CVE-2026-74256
Linux kernel BPF sockmap integer overflow enabling OOB memory corruption/kernel panic
Is CVE-2026-74256 being exploited?
Not confirmed. CVE-2026-74256 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-74256?
CVE-2026-74256 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-74256?
Yes. A fix has been recorded for CVE-2026-74256. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74256 affect?
CVE-2026-74256 affects Linux kernel (BPF sockmap - bpf_msg_pop_data). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74256?
Install vendor kernel update ASAP; restrict or disable untrusted BPF/sockmap usage.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Integer overflow in bpf_msg_pop_data enables out-of-bounds memory access causing kernel panic and potential local privilege escalation or code execution via BPF/sockmap.
Patch when possible
- affected>= 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and < 9ef44ed6fb0c1db01cfcc3de432a33e719713eb5
- affected>= 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and < d693c5ed67dabe1ccbf8dcea93075bdc9ffd4ca0
- affected>= 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and < ba5cc05dae8fce237d191c7ea96b1107a791e548
- affected>= 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and < c05a0ec1cdced622a1a0c7d85679fe02f31033ec
- affected>= 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and < 17eb9832a10db2f7a80cb429ca2bc5038445a943
- affected>= 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and < fe09dd288722f1c749b7506c0b3e7841a7d85027
- affected>= 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and < e09f7bd7273928b4089e6b71f8e992f2b356ca1b
- affected>= 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and < a48802fb2cd2d1e23651989f8ff4d15e9d5dad54
- affected5.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.