Kernel crash via scalar-register NULL dereference
Published Jun 24, 2026 · Updated Jun 24, 2026
NULL pointer dereference in the BPF verifier in Linux Kernel allows local users to crash the kernel through a crafted BPF program. map_kptr_match_type calls btf_is_kernel on reg->btf before rejecting a scalar register, whose BTF pointer is NULL, when it is stored in a kptr slot. Exploitation requires local low-privileged access and the ability to submit the crafted program to the BPF verifier; the resulting dereference can crash the running kernel without a reported data-read or data-write path.
Summary
What happened
NULL pointer dereference in the BPF verifier in Linux Kernel allows local users to crash the kernel through a crafted BPF program. map_kptr_match_type calls btf_is_kernel on reg->btf before rejecting a scalar register, whose BTF pointer is NULL, when it is stored in a kptr slot. Exploitation requires local low-privileged access and the ability to submit the crafted program to the BPF verifier; the resulting dereference can crash the running kernel without a reported data-read or data-write path.
The record
- CVE
- CVE-2026-53032
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 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=4782968e0d631b0d8944dcfd4bf8fb49be087101
- Affected versionversion=6.4.16 <6.5
- Affected versionversion=6.5.3 <6.6
- Affected versionversion=6.6
- Affected versionversion=ab6c637ad0276e42f8acabcbc64932a6d346dab3 <0a36c1f72888bca0237295a4da19cd91821a90be
- Affected versionversion=ab6c637ad0276e42f8acabcbc64932a6d346dab3 <4d0a375887ab4d49e4da1ff10f9606cab8f7c3ad
- Affected versionversion=ab6c637ad0276e42f8acabcbc64932a6d346dab3 <520454e839710c327808c2fcc98e28cee77355fc
- Affected versionversion=ab6c637ad0276e42f8acabcbc64932a6d346dab3 <6982653ce5f119982aa58f1af58e7bfbebf39252
- Affected versionversion=ab6c637ad0276e42f8acabcbc64932a6d346dab3 <da1d615ce49a47986a8864e2371a26e97861085c
- Affected versionversion=af3d2e0f3a54e67806959d161e613457772babc5
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