CVE-2026-72393
Linux kernel fbnic driver use-after-free in LSO causes kernel memory corruption.
Is CVE-2026-72393 being exploited?
Not confirmed. CVE-2026-72393 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.58% probability of exploitation in the next 30 days.
How severe is CVE-2026-72393?
CVE-2026-72393 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-72393?
Yes. A fix has been recorded for CVE-2026-72393. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72393 affect?
CVE-2026-72393 affects Linux kernel (fbnic module), Systems using Broadcom FBNIC adapters or drivers, Virtual guests using fbnic passthrough. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72393?
Apply vendor/kernel updates with fbnic fix or unload/disable fbnic if not required.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Use-after-free in fbnic during packet transmit; attacker can cause kernel crash or potentially achieve kernel RCE/privilege escalation via crafted traffic or local senders.
Immediate action required
- affected>= b0b0f52042acb324cd39fbefb2b1ae83af8f8ae1 and < 83df3e2594cd78aa40b1246a19879abb4891945b
- affected>= b0b0f52042acb324cd39fbefb2b1ae83af8f8ae1 and < 21f304c2aae46625e050c28d979f4b9d83faa85e
- affected>= b0b0f52042acb324cd39fbefb2b1ae83af8f8ae1 and < 62b68b774f06bf52e329f254f0199bc43d350ccf
- affected6.15
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.