Loading vulnerability…
CVE-2022-49995 is a use-after-free vulnerability in the Linux kernel writeback subsystem during disk-device removal. After bdi_unregister() stops writeback activity and waits for delayed work, wb_inode_writeback_end() can still schedule delayed bandwidth-estimation work. The resulting timer can access a freed bdi_writeback object. The upstream fix verifies that bdi_writeback is still alive before scheduling the work and makes wb->work_lock interrupt-safe because the affected function can execute in interrupt context.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel writeback subsystem use-after-free vulnerability that can occur after a device is removed.
A use-after-free vulnerability in the Linux kernel writeback subsystem after device removal.
Linux kernel vulnerability addressed by RHSA-2024:0575; no further technical detail is provided.
A Linux kernel writeback use-after-free vulnerability triggered after removal of a disk device. Delayed bandwidth-estimation work can be scheduled after bdi_unregister has completed and may access a freed bdi_writeback object. The fix checks whether bdi_writeback remains alive before scheduling the work and changes the relevant work lock to an IRQ-safe lock.
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.