Local denial of service via libbpf NULL dereference
Published Oct 19, 2022 · Updated Nov 3, 2025
Linux Kernel libbpf before 6.2 allows local users to cause a service interrupt via a NULL pointer dereference in find_prog_by_sec_insn. When an object has no program sections, obj->programs remains unallocated and the search accesses prog->sec_idx through a NULL entry. Local users able to invoke the affected BPF/libbpf processing can crash the process or kernel context; confidentiality and integrity impact are not reported.
Summary
What happened
Linux Kernel libbpf before 6.2 allows local users to cause a service interrupt via a NULL pointer dereference in find_prog_by_sec_insn. When an object has no program sections, obj->programs remains unallocated and the search accesses prog->sec_idx through a NULL entry. Local users able to invoke the affected BPF/libbpf processing can crash the process or kernel context; confidentiality and integrity impact are not reported.
The record
- CVE
- CVE-2022-3606
- Published
- Oct 19, 2022
- Updated
- Nov 3, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-404, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 19, 2022CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record 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=n/a
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