CVE-2023-52730 is a resource-management flaw in the Linux kernel MMC/SDIO subsystem. If SDIO function setup fails in sdio_add_func() or sdio_init_func(), the subsequent sdio_remove_func() cleanup path can omit release of device-tree-node and device references because the SDIO function has not been marked present. The upstream correction makes function presence govern only whether device_del() is needed, while always releasing applicable node and device references. It also moves device-reference acquisition to sdio_alloc_func() and release to sdio_release_func() to balance reference counting.
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.
Linux kernel MMC/SDIO resource-leak vulnerability affecting error-handling paths.
A Linux kernel MMC/SDIO issue involving possible resource leaks in certain error-handling paths. The cited automatic assessment characterizes its impact as low.
A Linux kernel MMC/SDIO error-path resource leak vulnerability. Failed SDIO function initialization or addition can leave device and device-tree references unreleased, causing memory/resource leaks and a potential availability impact.
A Linux kernel MMC/SDIO resource-leak vulnerability in error-handling paths. Failed SDIO function initialization or addition can leave device and device-tree references unreleased; the fix ensures cleanup routines are called and balances get_device()/put_device() reference handling.
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.