Loading vulnerability…
CVE-2024-50074 is a potential array out-of-bounds access vulnerability in the Linux kernel parallel-port subsystem. An earlier change replaced unbounded sprintf() calls with snprintf(), but subsequently used snprintf() return values for length calculations. Because snprintf() returns the number of characters that would have been produced rather than the number actually stored in a bounded buffer, a truncated result could cause a later calculation to exceed the buffer limit. The corrected implementation uses scnprintf(), which returns the number of characters actually written.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel parallel-port subsystem array out-of-bounds access flaw.
A Linux kernel parport array out-of-bounds access issue caused by incorrect length handling after replacing sprintf() with snprintf(). Because snprintf() returns the would-have-been output length, the calculated length could still exceed the destination limit. The fix uses scnprintf(), which returns the actual number of characters written.
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.