CVE-2022-50406 is a memory-corruption vulnerability in the Linux kernel iomap subsystem when recording errors during filesystem writeback. The observed failure involves a NULL-pointer dereference in errseq_set, reached through __filemap_set_wb_err and iomap_do_writepage. It was reproduced on an arm64 system using XFS on a device-mapper volume, with storage I/O errors occurring during writeback. The vulnerability can cause a kernel oops or crash. The precise underlying memory-lifetime defect and complete affected upstream version range are not established.
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.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A memory-corruption flaw in Linux kernel iomap error recording during writeback.
A Linux kernel iomap flaw that can cause memory corruption while recording errors during writeback.
Linux kernel iomap memory-corruption flaw when recording errors during writeback.
Linux kernel iomap memory-corruption flaw triggered while recording errors during writeback.
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.