Loading vulnerability…
CVE-2022-49985 is an out-of-bounds read vulnerability in Linux kernel eBPF array-range validation for poke descriptors. The affected logic represents the valid map-index interval with tnum_range(0, map->max_entries - 1) and tests the register offset using tnum_in(). Because a tracked-number range can overapproximate the intended concrete interval, an out-of-range constant index can be accepted. During BPF JIT compilation, this can lead to an out-of-bounds slab read in bpf_int_jit_compile. The correction performs the upper-bound check against the concrete reg->var_off.value when the register is a known constant scalar.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel eBPF flaw involving use of tnum_range during array range checking for poke descriptors. Red Hat addressed it in a Moderate-severity kernel update.
A Linux kernel BPF array-range checking flaw involving use of tnum_range for poke descriptors. Red Hat addressed it in its kernel-rt security update.
Linux kernel BPF array range-checking flaw.
A Linux kernel BPF flaw affecting array range checking for poke descriptors due to use of tnum_range.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.