CVE-2026-72221: sunrpc: wait for in-flight TLS handshake callback when cancel loses race
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.63% (FIRST EPSS); higher than 51% 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 0d8ceb39884148dc7a2fdf71e1cac5961ed1d2b9, 65b23bec1fca6e9ebdc3e6041ebf8c6ab074141b, a4f878e8ecd729ccf2e50993444e217583adeace.
Low priority for now. Upgrade to Linux Linux 0d8ceb39884148dc7a2fdf71e1cac5961ed1d2b9, 65b23bec1fca6e9ebdc3e6041ebf8c6ab074141b, a4f878e8ecd729ccf2e50993444e217583adeace 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: sunrpc: wait for in-flight TLS handshake callback when cancel loses race When wait_for_completion_interruptible_timeout() in svc_tcp_handshake() returns 0 (timeout) or -ERESTARTSYS (signal) and tls_handshake_cancel() then returns false, handshake_complete() has won the cancellation race: it has set HANDSHAKE_F_REQ_COMPLETED and is about to invoke svc_tcp_handshake_done(), but the callback's side effects on xpt_flags and on svsk->sk_handshake_done have not yet committed. The current code reads xpt_flags immediately to decide whether the session succeeded. Two races result. If the callback has executed set_bit(XPT_TLS_SESSION) but not yet clear_bit(XPT_HANDSHAKE), svc_tcp_handshake() sees a session, enqueues the transport, and returns. svc_xprt_received() then clears XPT_BUSY, a worker thread picks the transport up, the dispatcher in svc_handle_xprt() observes XPT_HANDSHAKE still set, and xpo_handshake is invoked a second time. That svc_tcp_handshake() calls init_completion(&svsk->sk_handshake_done) while the original callback concurrently calls complete_all() on it, corrupting the embedded swait_queue. If the callback has set HANDSHAKE_F_REQ_COMPLETED but not yet entered svc_tcp_handshake_done(), svc_tcp_handshake() reads XPT_TLS_SESSION as clear and tears the connection down even though the handshake is about to succeed. Wait for the callback to commit before inspecting xpt_flags. The completion is guaranteed to fire because handshake_complete() invokes svc_tcp_handshake_done() unconditionally once it has set HANDSHAKE_F_REQ_COMPLETED.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.6% · 51th percentile
- CWE
- —
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
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.
Is your version affected? Check itNoroxi 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
- 6.4affected
- b3cbf98e2fdf3cb147a95161560cd25987284330 and later · before 0d8ceb39884148dc7a2fdf71e1cac5961ed1d2b9affected · git
- b3cbf98e2fdf3cb147a95161560cd25987284330 and later · before e0f4691d42a54d359d8b64509fd9ab938d4f2a33affected · git
- b3cbf98e2fdf3cb147a95161560cd25987284330 and later · before 65b23bec1fca6e9ebdc3e6041ebf8c6ab074141baffected · git
- b3cbf98e2fdf3cb147a95161560cd25987284330 and later · before a4f878e8ecd729ccf2e50993444e217583adeaceaffected · git
- b3cbf98e2fdf3cb147a95161560cd25987284330 and later · before d00e32f84ca1a77cb67a3fbf59f58dada95f5a21affected · git
- before 6.4not affected · semver
- 6.6.145 and later · up to and including 6.6.*not affected · semver
- 6.12.97 and later · up to and including 6.12.*not affected · semver
- 6.18.40 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.74.1.el10_2 | 6.12.0-211.74.1.el10_2 |
+96
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-72218Aug 15, 2026 · lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure0Monitor
- ← EarlierCVE-2026-72219Aug 15, 2026 · lockd: Plug nlm_file leak when nlm_do_fopen() fails0Monitor
- Later →CVE-2026-72222Aug 15, 2026 · sunrpc: pin svc_xprt across the asynchronous TLS handshake callback39Monitor
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 | 0d8ceb39884148dc7a2fdf71e1cac5961ed1d2b9 | Vendor (CNA) |
| Linux Linux | 65b23bec1fca6e9ebdc3e6041ebf8c6ab074141b | Vendor (CNA) |
| Linux Linux | a4f878e8ecd729ccf2e50993444e217583adeace | Vendor (CNA) |
| Linux Linux | d00e32f84ca1a77cb67a3fbf59f58dada95f5a21 | Vendor (CNA) |
| Linux Linux | e0f4691d42a54d359d8b64509fd9ab938d4f2a33 | Vendor (CNA) |
| almalinux:kernel | 6.12.0-211.74.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.74.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.74.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.74.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.74.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.74.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.74.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.74.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.74.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.74.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.74.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.74.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.12.100-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.74.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.74.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-211.74.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-211.74.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-211.74.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-211.74.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-211.74.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-211.74.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-211.74.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:6.12.0-211.74.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:6.12.0-211.74.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-modules-internal | 0:6.12.0-211.74.1.el10_2 · Red Hat:shadow_migration_toolkit:10::el10 | Package registry (OSV) |
+12
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).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.