Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-46135: nvmet-tcp: fix race between ICReq handling and queue teardown

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 49891c8fe0cb43fbbe480da1cdccfbbaeb820cb3, 5293a8882c549fab4a878bc76b0b6c951f980a61, 5f0b95ef68ab9afba75b20eebf436130f80c161a.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 49891c8fe0cb43fbbe480da1cdccfbbaeb820cb3, 5293a8882c549fab4a878bc76b0b6c951f980a61, 5f0b95ef68ab9afba75b20eebf436130f80c161a or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix race between ICReq handling and queue teardown nvmet_tcp_handle_icreq() updates queue->state after sending an Initialization Connection Response (ICResp), but it does so without serializing against target-side queue teardown. If an NVMe/TCP host sends an Initialization Connection Request (ICReq) and immediately closes the connection, target-side teardown may start in softirq context before io_work drains the already buffered ICReq. In that case, nvmet_tcp_schedule_release_queue() sets queue->state to NVMET_TCP_Q_DISCONNECTING and drops the queue reference under state_lock. If io_work later processes that ICReq, nvmet_tcp_handle_icreq() can still overwrite the state back to NVMET_TCP_Q_LIVE. That defeats the DISCONNECTING-state guard in nvmet_tcp_schedule_release_queue() and allows a later socket state change to re-enter teardown and issue a second kref_put() on an already released queue. The ICResp send failure path has the same problem. If teardown has already moved the queue to DISCONNECTING, a send error can still overwrite the state with NVMET_TCP_Q_FAILED, again reopening the window for a second teardown path to drop the queue reference. Fix this by serializing both post-send state transitions with state_lock and bailing out if teardown has already started. Use -ESHUTDOWN as an internal sentinel for that bail-out path rather than propagating it as a transport error like -ECONNRESET. Keep nvmet_tcp_socket_error() setting rcv_state to NVMET_TCP_RECV_ERR before honoring that sentinel so receive-side parsing stays quiesced until the existing release path completes.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
May 28, 2026
Updated
Oct 19, 2026
EPSS
0.3% · 34th percentile

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-46135

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.0 and later · before 6.12.88
  • linux linux kernel6.13 and later · before 6.18.30
  • linux linux kernel6.19 and later · before 7.0.7
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.0affected
    • 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before b7dd4d27aa70bd98bb10572310e913668baf6a65affected · git
    • 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before 9c63cf80895a70eb4fcfcaa725bb1ac9ae76f02baffected · git
    • 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before 6f96dea4819d122737b217ea16660d255abbf8c6affected · git
    • 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before 5f0b95ef68ab9afba75b20eebf436130f80c161aaffected · git
    • 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before 49891c8fe0cb43fbbe480da1cdccfbbaeb820cb3affected · git
    • 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before 67e1aaf93b495c2f10bc8a5fbba575fbb7f449b6affected · git
    • 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before dcfe4d1f7960e7d1c01642318f3aae1a604f8508affected · git
    • 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before 5293a8882c549fab4a878bc76b0b6c951f980a61affected · git
    • before 5.0not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-46132May 28, 2026 · net: rtnetlink: zero ifla_vf_broadcast to avoid stack infoleak in rtnl_fill_vfinfo
    22Monitor
  • ← EarlierCVE-2026-46133May 28, 2026 · RDMA/rxe: Reject unknown opcodes before ICRC processing
    30Monitor
  • Later →CVE-2026-46136May 28, 2026 · wifi: mt76: mt7921: fix a potential clc buffer length underflow
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux49891c8fe0cb43fbbe480da1cdccfbbaeb820cb3Vendor (CNA)
Linux Linux5293a8882c549fab4a878bc76b0b6c951f980a61Vendor (CNA)
Linux Linux5f0b95ef68ab9afba75b20eebf436130f80c161aVendor (CNA)
Linux Linux67e1aaf93b495c2f10bc8a5fbba575fbb7f449b6Vendor (CNA)
Linux Linux6f96dea4819d122737b217ea16660d255abbf8c6Vendor (CNA)
Linux Linux9c63cf80895a70eb4fcfcaa725bb1ac9ae76f02bVendor (CNA)
Linux Linuxb7dd4d27aa70bd98bb10572310e913668baf6a65Vendor (CNA)
Linux Linuxdcfe4d1f7960e7d1c01642318f3aae1a604f8508Vendor (CNA)
almalinux:bpftool4.18.0-553.136.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.136.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.136.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.136.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.136.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.136.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.136.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.136.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.136.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.136.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.136.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.136.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-553.136.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.136.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.136.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.136.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.136.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.136.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.136.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-553.136.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-553.136.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+24

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records