Kernel memory corruption via BPF stack-size overflow
Published May 19, 2024 · Updated Aug 5, 2026
Integer overflow in the Linux BPF verifier allows local users to corrupt kernel memory by loading a crafted BPF program. check_stack_range_initialized() accepts a signed access size that can wrap negative, then walks outside the verifier's stack-state array. The path requires local access and CAP_BPF or delegated BPF-token capability; successful abuse enables kernel reads and writes, while failure can panic the system.
Summary
What happened
Integer overflow in the Linux BPF verifier allows local users to corrupt kernel memory by loading a crafted BPF program. check_stack_range_initialized() accepts a signed access size that can wrap negative, then walks outside the verifier's stack-state array. The path requires local access and CAP_BPF or delegated BPF-token capability; successful abuse enables kernel reads and writes, while failure can panic the system.
The record
- CVE
- CVE-2024-35905
- Published
- May 19, 2024
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-129, CWE-190, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 19, 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=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