Loading vulnerability…
A resource leak vulnerability existed in the Linux kernel's MMC/SDIO subsystem. Specifically, in error paths of sdio_add_func() and sdio_init_func(), resources such as device references and device tree nodes were not properly released if initialization failed. This was due to sdio_remove_func() not being able to clean up when the sdio function was not present, leading to unbalanced get/put operations and memory leaks. The patch ensures that of_node_put() and put_device() are always called, and that get/put operations are balanced by moving get_device() to sdio_alloc_func() and put_device() to sdio_release_func().
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.