CVE-2022-49122 is a potential Spectre variant 1 gadget in the Linux kernel device-mapper ioctl path. A user-controlled cmd value is used as an array index. Speculative execution may transiently perform an unsafe array access despite architectural bounds validation, allowing a side channel to expose kernel-memory contents. The upstream fix applies array_index_nospec to constrain the index before the array access.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A potential Spectre v1 gadget in the Linux kernel device-mapper ioctl handling.
A potential Spectre v1 gadget in the Linux kernel device-mapper ioctl path.
A potential Spectre v1 gadget in the Linux kernel device-mapper ioctl path, addressed in the Red Hat Enterprise Linux 8.2 AUS kernel update.
A medium-severity Linux kernel device-mapper ioctl Spectre v1 speculative-execution information-disclosure vulnerability. A user-controlled command value can be used as an array index, potentially allowing kernel-memory contents to leak to userspace speculatively. The resolution uses array_index_nospec.
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.