Kernel sanitizer warning via overflowing partition bounds check
Published Jul 12, 2024 · Updated May 23, 2026
Integer overflow in Linux kernel block partition ioctls allows local users to trigger a sanitizer warning via crafted bounds. The blkpg_do_ioctl check adds the untrusted partition start and length before testing whether the sum is negative, so the check itself overflows. Local access to a block-device ioctl is required; public sources document the warning but no resulting data exposure, modification, or service interruption.
Summary
What happened
Integer overflow in Linux kernel block partition ioctls allows local users to trigger a sanitizer warning via crafted bounds. The blkpg_do_ioctl check adds the untrusted partition start and length before testing whether the sum is negative, so the check itself overflows. Local access to a block-device ioctl is required; public sources document the warning but no resulting data exposure, modification, or service interruption.
The record
- CVE
- CVE-2024-41000
- Published
- Jul 12, 2024
- Updated
- May 23, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-190
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 12, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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