Kernel compromise via incorrect packet-pointer state pruning
Published May 1, 2026 · Updated May 1, 2026
Incorrect state pruning in the Linux Kernel BPF verifier allows local users to compromise the kernel through a crafted BPF program. The regsafe() comparison wrongly treats a prior BEYOND_PKT_END packet-pointer range as safe for a current finite range, preventing exploration of the valid current state. Low local privileges and permission to submit the relevant BPF program are required; the public record does not disclose the resulting post-verification primitive.
Summary
What happened
Incorrect state pruning in the Linux Kernel BPF verifier allows local users to compromise the kernel through a crafted BPF program. The regsafe() comparison wrongly treats a prior BEYOND_PKT_END packet-pointer range as safe for a current finite range, preventing exploration of the valid current state. Low local privileges and permission to submit the relevant BPF program are required; the public record does not disclose the resulting post-verification primitive.
The record
- CVE
- CVE-2026-43030
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 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=5.11
- Affected versionversion=6d94e741a8ff818e5518da8257f5ca0aaed1f269 <015a74476dc1ab6923d89f1ee009aaf43faa7185
- Affected versionversion=6d94e741a8ff818e5518da8257f5ca0aaed1f269 <37db6b9726d0bcf91cbdf9d63b558c50da49f968
- Affected versionversion=6d94e741a8ff818e5518da8257f5ca0aaed1f269 <7241da033fdc507b920e092dab1f97b945cb0370
- Affected versionversion=6d94e741a8ff818e5518da8257f5ca0aaed1f269 <8aebe18069394f4a79d2d82080a0f806da449996
- Affected versionversion=6d94e741a8ff818e5518da8257f5ca0aaed1f269 <a8502a79e832b861e99218cbd2d8f4312d62e225
- Affected versionversion=6d94e741a8ff818e5518da8257f5ca0aaed1f269 <b99d82706bd1511bb875e3de7154698fd9215c99
- Affected versionversion=6d94e741a8ff818e5518da8257f5ca0aaed1f269 <ca995b1462ec6db1e869100ba1fb7356bd3f22f0
- Affected versionversion=95b6ec733752b31bfd166c4609d2c1b5cdde9b47 <b52f6d0ef7b308f9d05bbddb78749852f28e8e40
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