Kernel crash via unterminated qedf debugfs input
Published Jun 19, 2024 · Updated May 12, 2026
Out-of-bounds read in the Linux kernel qedf SCSI driver from 4.11 allows local users to crash the kernel through a debugfs write. The qedf_dbg_debug_cmd_write function copies a count-sized user buffer without a terminating NUL, then kstrtouint reads beyond that allocation while parsing it. Access to the qedf debugfs command interface and local privileges are required, and the bounded consequence is a kernel crash.
Summary
What happened
Out-of-bounds read in the Linux kernel qedf SCSI driver from 4.11 allows local users to crash the kernel through a debugfs write. The qedf_dbg_debug_cmd_write function copies a count-sized user buffer without a terminating NUL, then kstrtouint reads beyond that allocation while parsing it. Access to the qedf debugfs command interface and local privileges are required, and the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2024-38559
- Published
- Jun 19, 2024
- Updated
- May 12, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-476, CWE-20, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 19, 2024CVE publishedPublication date reported by the CVE source.
- May 12, 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=0 <*
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