cve.bz

CVE-2026-63978 linux linux kernel: Race Condition

9.8 criticalEPSS 0.5%Fix available

Critical (9.8) in linux linux kernel. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-63978 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63978?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63978?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-63978 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.4 and later

Fixed in

ProductRelease lineFixed in
Linux6.66.6.160
Linux6.126.12.93
Linux6.186.18.44
Linux7.07.0.12
Linuxlater releases7.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13linux6.12.94-1DEBIAN-CVE-2026-63978
Debian14linux7.0.12-1DEBIAN-CVE-2026-63978
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-63978
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-63978
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-63978
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 moreno fix listedUBUNTU-CVE-2026-63978
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 41 moreno fix listedUBUNTU-CVE-2026-63978
Ubuntu24.04:LTSlinux-azure-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-63978 USN-8728-2
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-63978
Ubuntu24.04:LTSlinux-gcp-7.0, linux-oracle-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-63978 USN-8728-1 USN-8728-3
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-28.28~24.04.1UBUNTU-CVE-2026-63978
Ubuntu24.04:LTSlinux-nvidia-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-63978 USN-8663-1
Ubuntu24.04:LTSlinux-nvidia-tegra6.8.0-1035.38UBUNTU-CVE-2026-63978 USN-8781-1
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-28.28.1~24.04.3UBUNTU-CVE-2026-63978
13 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:9::appstreamrv, perf, rtla and 29 more0:5.14.0-687.61.1.el9_8RHSA-2026:90365
Red Hatenterprise_linux:9::baseoskernel, kernel-64k, kernel-core and 45 more0:5.14.0-687.61.1.el9_8RHSA-2026:90365
Red Hatenterprise_linux:9::crblibperf, perf-debuginfo, kernel-debuginfo and 16 more0:5.14.0-687.61.1.el9_8RHSA-2026:90365
Red Hatenterprise_linux:9::nfvkernel-rt, kernel-rt-core, perf-debuginfo and 18 more0:5.14.0-687.61.1.el9_8RHSA-2026:90365
Red Hatenterprise_linux:9::realtimekernel-rt, kernel-rt-64k, kernel-rt-core and 35 more0:5.14.0-687.61.1.el9_8RHSA-2026:90365
Red Hatenterprise_linux:10.2rv, perf, rtla and 88 more0:6.12.0-211.69.1.el10_2RHSA-2026:91565
Red Hatshadow_migration_toolkit:10::el10kernel-modules-internal0:6.12.0-211.69.1.el10_2RHSA-2026:91565
AlmaLinux9rv, perf, rtla and 71 more5.14.0-687.61.1.el9_8ALSA-2026:90365
AlmaLinux10rv, perf, rtla and 72 more6.12.0-211.69.1.el10_2ALSA-2026:91565
Rocky Linux9kernel0:5.14.0-687.61.1.el9_8RLSA-2026:90365
Rocky Linux9kernel0:5.14.0-687.61.1.el9_8.cloud.1.0RXSA-2026:90365
Rocky Linux10kernel0:6.12.0-211.69.1.el10_2RLSA-2026:91565
Azure Linux3kernel6.6.161.1-1AZL-92820
Alpaquita25linux-lts6.12.95-r0BELL-CVE-2026-63978
Alpaquitastreamlinux-lts6.18.46-r0BELL-CVE-2026-63978

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpaquita.

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernel-0:6.12.0-211.69.1.el10_2Fixed 2026-10-28RHSA-2026:91565
Red Hat Enterprise Linux 9kernel-0:5.14.0-687.61.1.el9_8Fixed 2026-10-26RHSA-2026:90365
Shadow Migration Toolkit for Virtualization for RHEL 10kernel-0:6.12.0-211.69.1.el10_2Fixed 2026-10-28RHSA-2026:91565
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-63978.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. Analyzed by the NVD

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON