Kernel crash via nullable BPF pointer dereference
Published May 8, 2026 · Updated May 8, 2026
NULL pointer dereference in the Linux kernel's BPF verifier allows local users to crash the kernel through a crafted map iterator program. The check_mem_access() path applies base_type() to nullable PTR_TO_BUF map-iterator key and value pointers, stripping PTR_MAYBE_NULL and approving direct access without a null check. Low-privileged local access capable of loading the relevant BPF program is required; a stop callback supplies NULL and triggers the kernel crash.
Summary
What happened
NULL pointer dereference in the Linux kernel's BPF verifier allows local users to crash the kernel through a crafted map iterator program. The check_mem_access() path applies base_type() to nullable PTR_TO_BUF map-iterator key and value pointers, stripping PTR_MAYBE_NULL and approving direct access without a null check. Low-privileged local access capable of loading the relevant BPF program is required; a stop callback supplies NULL and triggers the kernel crash.
The record
- CVE
- CVE-2026-43333
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 8, 2026CVE publishedPublication date reported by the CVE source.
- May 8, 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=20b2aff4bc15bda809f994761d5719827d66c0b4 <21a10c06ffae24cb01fd174a7ab7736001d2ea56
- Affected versionversion=20b2aff4bc15bda809f994761d5719827d66c0b4 <4f6c99dc0420f1a3d671c1b8ab8a7ac84d9cba09
- Affected versionversion=20b2aff4bc15bda809f994761d5719827d66c0b4 <63276547debc4d8a73eefb2c5273b2a905c961b0
- Affected versionversion=20b2aff4bc15bda809f994761d5719827d66c0b4 <70abd9d118da2f56beb4ec22e3a29becae373535
- Affected versionversion=20b2aff4bc15bda809f994761d5719827d66c0b4 <8755066f7bd0f4ac46a29d1708c7b20894539252
- Affected versionversion=20b2aff4bc15bda809f994761d5719827d66c0b4 <b0db1accbc7395657c2b79db59fa9fae0d6656f3
- Affected versionversion=5.17
- Affected versionversion=b453361384c2db1c703dacb806d5fd36aec4ceca <10bc4a4dcded509c5d5c67d497900c3922c604cd
- Affected versionversion=e982070f8970bb62e69ed7c9cafff886ed200349
What conditions does exploitation require?
What is affected?
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