Widely used Linux kernel component; a critical race could crash NVMe/TCP targets and disrupt storage IO across many servers.
CVE-2026-46135
Linux nvmet-tcp race may cause teardown re-entry and kernel crash.
Is CVE-2026-46135 being exploited?
Not confirmed. CVE-2026-46135 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.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-46135?
CVE-2026-46135 is rated Critical. 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-46135?
Yes. A fix has been recorded for CVE-2026-46135. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-46135 affect?
CVE-2026-46135 affects Linux kernel nvmet-tcp (NVMe over TCP). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-46135?
Upgrade to patched kernel with nvmet-tcp fix
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Race in ICReq handling may cause queue teardown re-entry, risking kernel crash or instability in NVMe/TCP targets.
Patch when possible
- affected>= 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < b7dd4d27aa70bd98bb10572310e913668baf6a65
- affected>= 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < 9c63cf80895a70eb4fcfcaa725bb1ac9ae76f02b
- affected>= 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < 6f96dea4819d122737b217ea16660d255abbf8c6
- affected>= 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < 5f0b95ef68ab9afba75b20eebf436130f80c161a
- affected>= 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < 49891c8fe0cb43fbbe480da1cdccfbbaeb820cb3
- affected>= 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < 67e1aaf93b495c2f10bc8a5fbba575fbb7f449b6
- affected>= 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < dcfe4d1f7960e7d1c01642318f3aae1a604f8508
- affected>= 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < 5293a8882c549fab4a878bc76b0b6c951f980a61
- 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.