Linux kernel BPF nullable PTR_TO_BUF NULL dereference
A vulnerability in the Linux kernel BPF verifier allowed direct memory access checks on nullable PTR_TO_BUF pointers without enforcing a prior NULL check. The flaw is in check_mem_access(), which matches PTR_TO_BUF via base_type(); this strips the PTR_MAYBE_NULL qualifier and incorrectly permits direct dereference of pointers that may be NULL. In the map iterator context, ctx->key and ctx->value are typed as PTR_TO_BUF | PTR_MAYBE_NULL, and during stop callbacks these pointers can legitimately be NULL. As a result, direct access to these fields could trigger a kernel NULL pointer dereference. The fix adds a type_may_be_null() guard to the PTR_TO_BUF handling path, aligning it with the existing PTR_TO_BTF_ID validation pattern.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.