CVE-2024-26919 is a resource-leak flaw in the Linux kernel USB ULPI subsystem. The per-device ULPI debugfs root is created using the ULPI device's parent name, while interface unregistration attempts to remove a directory using the ULPI device name. Because the names do not match, the debugfs directory is not removed. The stale directory can persist across device teardown and block subsequent deferred probe attempts.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel USB ULPI debugfs directory resource-leak vulnerability.
Linux kernel USB ULPI debugfs directory reference-leak flaw.
Linux kernel USB ULPI debugfs directory-leak vulnerability.
Linux kernel ULPI USB debugfs directory resource-leak vulnerability.
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.