Kernel-memory disclosure via uninitialized file-handle padding
Published Apr 17, 2024 · Updated May 12, 2026
Information disclosure in affected Linux kernels and Siemens GNU/Linux subsystems allows attackers to receive uninitialized kernel-memory bytes. The do_sys_name_to_handle function allocates a file-handle buffer with kmalloc and copies 20 bytes to the caller without initializing bytes 18 and 19. Reachability requires access to the name_to_handle_at system call; the reported exposure is limited to two bytes, with no established code execution or data modification.
Summary
What happened
Information disclosure in affected Linux kernels and Siemens GNU/Linux subsystems allows attackers to receive uninitialized kernel-memory bytes. The do_sys_name_to_handle function allocates a file-handle buffer with kmalloc and copies 20 bytes to the caller without initializing bytes 18 and 19. Reachability requires access to the name_to_handle_at system call; the reported exposure is limited to two bytes, with no established code execution or data modification.
The record
- CVE
- CVE-2024-26901
- Published
- Apr 17, 2024
- Updated
- May 12, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-908
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 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=V3.1.0 <V3.1.5
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