Local kernel compromise via parport procfs overflow
Published Aug 17, 2024 · Updated Aug 5, 2026
Stack buffer overflow in the Linux parport procfs interface allows local users to compromise the kernel through file reads. The do_hardware_base_addr and do_autoprobe handlers use unbounded formatting to copy address or Device ID data into fixed-size stack buffers. Any local account that can read the affected read-only procfs entries can trigger kernel-stack corruption, resulting in a system crash or kernel control-flow compromise.
Summary
What happened
Stack buffer overflow in the Linux parport procfs interface allows local users to compromise the kernel through file reads. The do_hardware_base_addr and do_autoprobe handlers use unbounded formatting to copy address or Device ID data into fixed-size stack buffers. Any local account that can read the affected read-only procfs entries can trigger kernel-stack corruption, resulting in a system crash or kernel control-flow compromise.
The record
- CVE
- CVE-2024-42301
- Published
- Aug 17, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 17, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <166a0bddcc27de41fe13f861c8348e8e53e988c8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <47b3dce100778001cd76f7e9188944b5cb27a76d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7789a1d6792af410aa9b39a1eb237ed24fa2170a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7f4da759092a1a6ce35fb085182d02de8cc4cc84
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a44f88f7576bc1916d8d6293f5c62fbe7cbe03e0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ab11dac93d2d568d151b1918d7b84c2d02bacbd5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b579ea3516c371ecf59d073772bc45dfd28c8a0e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c719b393374d3763e64900ee19aaed767d5a08d6
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo