Linux kernel BPF regsafe() packet pointer state validation flaw
CVE-2026-43030 is a vulnerability in the Linux kernel BPF verifier logic, fixed by the change described as "bpf: Fix regsafe() for pointers to packet." The flaw is in regsafe() handling of packet-pointer register state comparisons. Specifically, when the old register state has rold->reg->range == BEYOND_PKT_END and the current register state has rcur->reg->range == N, regsafe() may incorrectly return true. This can cause the verifier to treat distinct states as equivalent and skip exploration of a current state that actually has a valid packet range. The issue is therefore a logic error in BPF verifier state-safety analysis for pointers to packet.
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
8 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.