Loading vulnerability…
CVE-2024-42301 is an array out-of-bounds write vulnerability in the Linux kernel parallel-port subsystem. The parport hardware-base-address handling path used sprintf to copy formatted data into a fixed-size destination buffer without bounds enforcement. An oversized formatted value can overwrite adjacent stack memory; observed behavior included stack-canary detection and a kernel panic in do_hardware_base_addr. The flaw was fixed by replacing unsafe sprintf operations with bounded snprintf operations.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A locally exploitable vulnerability requiring low privileges that can result in high confidentiality, integrity, and availability impact, according to the supplied CVSS v3 vector.
An array out-of-bounds risk in the Linux kernel parallel-port device subsystem.
Linux kernel parallel-port subsystem array out-of-bounds flaw.
Linux kernel parallel-port driver array out-of-bounds risk.
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.