CVE-2026-63979: net/handshake: hand off the pinned file reference to accept_doit
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 2f28dbb30b88eafab8d49aaec94710b4e12dea8e, 68eba6519cbd6359fb554a9720f3a3b6b2eba23f, b869e3e4ce1996df23b3efdbbe9a64c4ab81d745.
Low priority for now. Upgrade to Linux Linux 2f28dbb30b88eafab8d49aaec94710b4e12dea8e, 68eba6519cbd6359fb554a9720f3a3b6b2eba23f, b869e3e4ce1996df23b3efdbbe9a64c4ab81d745 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: hand off the pinned file reference to accept_doit handshake_req_next() removes the request from the per-net pending list and drops hn_lock before handshake_nl_accept_doit() reads req->hr_sk->sk_socket and dereferences sock->file (once in FD_PREPARE() and again in get_file()). In that window a consumer running tls_handshake_cancel() followed by sockfd_put() (svc_sock_free) or __fput_sync() (xs_reset_transport) releases sock->file. sock_release() then runs sock_orphan(), zeroing sk_socket, and frees the struct socket. The accept-side code either reads NULL through sk_socket or chases freed memory. The submit-side sock_hold() does not prevent this. sk_refcnt protects struct sock, but struct socket and sock->file are independently refcounted via the file descriptor the consumer owns. Pinning sk leaves sock and sock->file unprotected. Retarget the accept-side dereferences at req->hr_file, which was pinned at submit time, instead of req->hr_sk->sk_socket->file. Pinning on its own is not sufficient: a consumer that cancels between handshake_req_next() returning and accept_doit reaching FD_PREPARE() takes the !remove_pending() branch in handshake_req_cancel() and drops hr_file before the accept side takes its own reference. Hand off an additional file reference inside handshake_req_next(), under hn_lock, so the accept side operates on a reference that no concurrent handshake_req_cancel() can revoke. FD_PREPARE() consumes that handed-off reference, either by transferring it to the new fd in fd_publish() or by dropping it in the cleanup destructor on error; the explicit get_file() that previously balanced FD_PREPARE() is therefore redundant and goes away. Update handshake_req_cancel_test2 and _test3 to simulate the FD_PREPARE() consumption with an fput() so the kunit file-count assertions stay balanced.
- Published
- Jul 19, 2026
- Updated
- Nov 12, 2026
- EPSS
- 0.6% · 51th percentile
- CWE
- CWE-416
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.
| 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 b869e3e4ce1996df23b3efdbbe9a64c4ab81d745affected · git
- 3b3009ea8abb713b022d94fba95ec270cf6e7eae and later · before 2f28dbb30b88eafab8d49aaec94710b4e12dea8eaffected · git
- 3b3009ea8abb713b022d94fba95ec270cf6e7eae and later · before 68eba6519cbd6359fb554a9720f3a3b6b2eba23faffected · git
- 3b3009ea8abb713b022d94fba95ec270cf6e7eae and later · before c06876d4fac38f35820946ee3b1be7d7da799cd4affected · git
- 3b3009ea8abb713b022d94fba95ec270cf6e7eae and later · before f4251190e58b209999c1ba9e6d2976136a1be055affected · git
- before 6.4not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.114 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.114
- 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-63977Jul 19, 2026 · dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work31Monitor
- ← EarlierCVE-2026-63978Jul 19, 2026 · net/handshake: Drain pending requests at net namespace exit39Monitor
- Later →CVE-2026-63980Jul 19, 2026 · net/handshake: Use spin_lock_bh for hn_lock30Monitor
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 | 2f28dbb30b88eafab8d49aaec94710b4e12dea8e | Vendor (CNA) |
| Linux Linux | 68eba6519cbd6359fb554a9720f3a3b6b2eba23f | Vendor (CNA) |
| Linux Linux | b869e3e4ce1996df23b3efdbbe9a64c4ab81d745 | Vendor (CNA) |
| Linux Linux | c06876d4fac38f35820946ee3b1be7d7da799cd4 | Vendor (CNA) |
| Linux Linux | f4251190e58b209999c1ba9e6d2976136a1be055 | Vendor (CNA) |
| 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.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.0.12-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.115-2~deb12u1 · Debian:12 | 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) |
| red hat:kernel-debuginfo | 0:5.14.0-687.61.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+3
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-416 · Use After FreeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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.