CVE-2026-72339
Linux qede NIC off-by-one bug causes kernel memory/DMA corruption
Is CVE-2026-72339 being exploited?
Not confirmed. CVE-2026-72339 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.74% probability of exploitation in the next 30 days.
How severe is CVE-2026-72339?
CVE-2026-72339 is rated Critical with a CVSS score of 9.8. 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-72339?
Yes. A fix has been recorded for CVE-2026-72339. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72339 affect?
CVE-2026-72339 affects Linux kernel (qede network driver), Servers with Broadcom QED / Emulex NICs, Cloud hosts running affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72339?
Deploy vendor/Kernel updates that include the qede fix and reboot affected hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Malicious network traffic can desynchronize BD ring causing DMA/SLUB corruption, leading to kernel panic or potential privilege escalation / remote code execution.
Immediate action required
- affected>= 8a8633978b842c88fbcfe00d4e5dde96048f630e and < ecc05d4b20220a09c9c69584fc46ca55248a374a
- affected>= 8a8633978b842c88fbcfe00d4e5dde96048f630e and < 07be8b8adf91b7ada4c3dacce064d572a6066421
- affected>= 8a8633978b842c88fbcfe00d4e5dde96048f630e and < 1624aa100c0b218181aa74e3696a389b509298cb
- affected>= 8a8633978b842c88fbcfe00d4e5dde96048f630e and < 0bf78df2d3ecb1f4964ff42a7327d25845955153
- affected>= 8a8633978b842c88fbcfe00d4e5dde96048f630e and < 814a5edac8c9fc04051808d5faaa93768e989281
- affected>= 8a8633978b842c88fbcfe00d4e5dde96048f630e and < b066420e57f3402a52c998678b4678252ac9bb63
- affected>= 8a8633978b842c88fbcfe00d4e5dde96048f630e and < 982d6d6bc059c5dff37a2201c2f08c14bcfcbd20
- affected>= 8a8633978b842c88fbcfe00d4e5dde96048f630e and < a0a558ca7e75b49e71f8c545c30e8c005e6e4e2f
- affected4.18
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.