CVE-2026-72491: net/9p: fix race condition on rdma->state in trans_rdma.c
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.72% (FIRST EPSS); higher than 54.3% of all records.
- 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 13bf9879b778b2f4b260b45bed18f31806120d1e, 151f8cf5b23d8a534d884432a82a6d54d5a61989, 3970a19a80de530b801b6256354d4a529a9a2d6c.
Low priority for now. Upgrade to Linux Linux 13bf9879b778b2f4b260b45bed18f31806120d1e, 151f8cf5b23d8a534d884432a82a6d54d5a61989, 3970a19a80de530b801b6256354d4a529a9a2d6c 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: net/9p: fix race condition on rdma->state in trans_rdma.c The rdma->state field is modified without holding req_lock in both recv_done() and p9_cm_event_handler(), while rdma_request() accesses the same field under the req_lock spinlock. This inconsistent locking creates a race condition: - recv_done() running in softirq completion context sets rdma->state = P9_RDMA_FLUSHING without acquiring req_lock - p9_cm_event_handler() modifies rdma->state at multiple points (ADDR_RESOLVED, ROUTE_RESOLVED, ESTABLISHED, CLOSED) without req_lock - rdma_request() uses spin_lock_irqsave(&rdma->req_lock, flags) to protect the read-modify-write of rdma->state The race can cause lost state transitions: recv_done() or the CM event handler could set state to FLUSHING/CLOSED while rdma_request() is concurrently checking or modifying state under the lock, leading to the FLUSHING transition being silently overwritten by CLOSING. This corrupts the connection state machine and can cause use-after-free on RDMA request objects during teardown. Fix by adding req_lock protection to all rdma->state modifications in recv_done() and p9_cm_event_handler(), matching the pattern already used in rdma_request(). Use spin_lock_irqsave/spin_unlock_irqrestore in the CM event handler since it can race with recv_done() which runs in softirq context. Tested with a kernel module that races two threads (simulating rdma_request and recv_done/CM handler) on rdma->state with proper locking: 5.5M+ FLUSHING writes over 27M iterations with 0 lost transitions.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.7% · 54th percentile
- CWE
- —
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
—
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
- 3479b3c35e82ed10aa0ca2ee9e78c4eded06ba62, c01ddaa54d7411e964ffd250c018d8469c5852f2, 9e69c673fe077b8dc491cd8406c9bdcb1f76dee2, e48e7e27e4dfd00c81e0381e7cee610cce021452, 4.20affected
- 473c7dd1d7b59ff8f88a5154737e3eac78a96e5b and later · before 4cee2b8766045059d5e0b8114837b4a8efe827acaffected · git
- 473c7dd1d7b59ff8f88a5154737e3eac78a96e5b and later · before 5424138848eb7d7d8a7196676e90a2cbf2142454affected · git
- 473c7dd1d7b59ff8f88a5154737e3eac78a96e5b and later · before 3970a19a80de530b801b6256354d4a529a9a2d6caffected · git
- 473c7dd1d7b59ff8f88a5154737e3eac78a96e5b and later · before 8aadc136d8e8d8fc95d7982d213cfe2234dfcf2baffected · git
- 473c7dd1d7b59ff8f88a5154737e3eac78a96e5b and later · before 151f8cf5b23d8a534d884432a82a6d54d5a61989affected · git
- 473c7dd1d7b59ff8f88a5154737e3eac78a96e5b and later · before 13bf9879b778b2f4b260b45bed18f31806120d1eaffected · git
- 473c7dd1d7b59ff8f88a5154737e3eac78a96e5b and later · before ebbcbe5c0db215feecc17def06178da443f4eea6affected · git
- 473c7dd1d7b59ff8f88a5154737e3eac78a96e5b and later · before 7d54894a1ee265a72d70f7cae1da6cc774cccc71affected · git
- 4.4.185 and later · before 4.5affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72487Aug 15, 2026 · PCI: Check ROM header and data structure addr before accessing30Monitor
- ← EarlierCVE-2026-72488Aug 15, 2026 · soundwire: fix bug in sdw_add_element_group_count found by syzkaller31Monitor
- Later →CVE-2026-72493Aug 15, 2026 · net: serialize netif_running() check in enqueue_to_backlog()39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 13bf9879b778b2f4b260b45bed18f31806120d1e | Vendor (CNA) |
| Linux Linux | 151f8cf5b23d8a534d884432a82a6d54d5a61989 | Vendor (CNA) |
| Linux Linux | 3970a19a80de530b801b6256354d4a529a9a2d6c | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 4cee2b8766045059d5e0b8114837b4a8efe827ac | Vendor (CNA) |
| Linux Linux | 5424138848eb7d7d8a7196676e90a2cbf2142454 | Vendor (CNA) |
| Linux Linux | 7d54894a1ee265a72d70f7cae1da6cc774cccc71 | Vendor (CNA) |
| Linux Linux | 8aadc136d8e8d8fc95d7982d213cfe2234dfcf2b | Vendor (CNA) |
| Linux Linux | ebbcbe5c0db215feecc17def06178da443f4eea6 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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 researchersFinders, 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).
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)
—
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/151f8cf5b23d8a534d884432a82a6d54d5a61989
- git.kernel.org/stable/c/3970a19a80de530b801b6256354d4a529a9a2d6c
- git.kernel.org/stable/c/4cee2b8766045059d5e0b8114837b4a8efe827ac
- git.kernel.org/stable/c/5424138848eb7d7d8a7196676e90a2cbf2142454
- git.kernel.org/stable/c/7d54894a1ee265a72d70f7cae1da6cc774cccc71
- git.kernel.org/stable/c/8aadc136d8e8d8fc95d7982d213cfe2234dfcf2b
- git.kernel.org/stable/c/ebbcbe5c0db215feecc17def06178da443f4eea6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.