CVE-2026-63978: net/handshake: Drain pending requests at net namespace exit
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.49% (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 2bf24a7e190aae0ea47c78099938ae056c622e44, 8c35539db0ab0bfa1ea44efab00b053261a69469, 9ec20c9a5a04f2c3f1cf65d21f886d7aaa6189cd; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 2bf24a7e190aae0ea47c78099938ae056c622e44, 8c35539db0ab0bfa1ea44efab00b053261a69469, 9ec20c9a5a04f2c3f1cf65d21f886d7aaa6189cd; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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/handshake: Drain pending requests at net namespace exit The arguments to list_splice_init() in handshake_net_exit() are reversed. The call moves the local empty "requests" list onto hn->hn_requests, leaving the local list empty, so the subsequent drain loop runs zero iterations. Pending handshake requests that had not yet been accepted are not torn down when the net namespace is destroyed; each one keeps a reference on a socket file and on the handshake_req allocation. Pass the source and destination in the documented order (list_splice_init(list, head) moves list onto head) so the pending list is transferred to the local scratch list and drained through handshake_complete(). Fixing the splice direction exposes a list-corruption race. After the splice each req->hr_list still has non-empty link pointers, threading the stack-local scratch list rather than hn_requests. A concurrent handshake_req_cancel() -- for example, from sunrpc's TLS timeout on a kernel socket whose netns reference was not taken -- finds the request through the rhashtable, calls remove_pending(), and sees !list_empty(&req->hr_list). __remove_pending_locked() then list_del_init()s an entry off the scratch list while the drain iterates, corrupting it. The same call arriving after the drain loop has run list_del() on an entry hits LIST_POISON instead. Have remove_pending() check HANDSHAKE_F_NET_DRAINING under hn_lock and report not-found when drain is in progress. The drain has already taken ownership; handshake_complete()'s existing test_and_set on HANDSHAKE_F_REQ_COMPLETED still arbitrates between drain and cancel for who calls the consumer's hp_done. Use list_del_init() rather than list_del() in the drain so req->hr_list does not carry LIST_POISON after drain releases the entry. The DRAINING guard in remove_pending() makes cancel return false, but cancel still falls through to test_and_set_bit on HANDSHAKE_F_REQ_COMPLETED and drops the request's hr_file reference. Without another pin, if that is the last reference, sk_destruct frees the request while it is still linked on the drain loop's local list. Pin each request's hr_file under hn_lock before releasing the list, and drop that drain pin after the loop finishes with the request.
- Published
- Jul 19, 2026
- Updated
- Nov 12, 2026
- EPSS
- 0.4% · 42th percentile
- CWE
- CWE-362
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.4%
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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
- 3b3009ea8abb713b022d94fba95ec270cf6e7eae and later · before ee4b2ba9d30155f9945811cd3c0c1b06d45787a9affected · git
- 3b3009ea8abb713b022d94fba95ec270cf6e7eae and later · before 9ec20c9a5a04f2c3f1cf65d21f886d7aaa6189cdaffected · git
- 3b3009ea8abb713b022d94fba95ec270cf6e7eae and later · before 2bf24a7e190aae0ea47c78099938ae056c622e44affected · git
- 3b3009ea8abb713b022d94fba95ec270cf6e7eae and later · before 8c35539db0ab0bfa1ea44efab00b053261a69469affected · git
- 3b3009ea8abb713b022d94fba95ec270cf6e7eae and later · before ea5fe6a73ca57e5150b8a38b341aef2636eb72f0affected · git
- before 6.4not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.93 and later · up to and including 6.12.*not affected · semver
- 6.18.44 and later · up to and including 6.18.*not affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.4 and later · before 6.6.160
- linux linux kernel6.7 and later · before 6.12.93
- linux linux kernel6.13 and later · before 6.18.44
- linux linux kernel6.19 and later · before 7.0.12
- linux linux kernel7.1
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.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-63976Jul 19, 2026 · Bluetooth: l2cap: clear chan->ident on ECRED reconfiguration success35Monitor
- ← EarlierCVE-2026-63977Jul 19, 2026 · dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work31Monitor
- Later →CVE-2026-63979Jul 19, 2026 · net/handshake: hand off the pinned file reference to accept_doit39Monitor
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 | 2bf24a7e190aae0ea47c78099938ae056c622e44 | Vendor (CNA) |
| Linux Linux | 8c35539db0ab0bfa1ea44efab00b053261a69469 | Vendor (CNA) |
| Linux Linux | 9ec20c9a5a04f2c3f1cf65d21f886d7aaa6189cd | Vendor (CNA) |
| Linux Linux | ea5fe6a73ca57e5150b8a38b341aef2636eb72f0 | Vendor (CNA) |
| Linux Linux | ee4b2ba9d30155f9945811cd3c0c1b06d45787a9 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| almalinux:kernel | 5.14.0-687.61.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-687.61.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-687.61.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-687.61.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-687.61.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-687.61.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-687.61.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-687.61.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-687.61.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-687.61.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-687.61.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-687.61.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.12.94-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-687.61.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-687.61.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-687.61.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-687.61.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-687.61.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-687.61.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-687.61.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-687.61.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-687.61.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+4
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)
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.
Attack patterns (CAPEC)
ATT&CK techniques
—
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.