cve.bz

CVE-2026-63980 linux linux kernel: Race Condition

7.5 highEPSS 0.3%Fix available

High (7.5) in linux linux kernel. EPSS 0.3% 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: Use spin_lock_bh for hn_lock nvmet_tcp_state_change(), a socket callback that runs in BH context, can reach handshake_req_cancel() via nvmet_tcp_schedule_release_queue() and tls_handshake_cancel(). handshake_req_cancel() acquires hn->hn_lock with plain spin_lock(). If a process-context thread on the same CPU holds hn->hn_lock when a softirq invokes the cancel path, the lock attempt deadlocks. This is the only caller that invokes tls_handshake_cancel() from BH context; every other consumer calls it from process context. Deferring the cancel to process context in the NVMe target is not straightforward: nvmet_tcp_schedule_release_queue() must call tls_handshake_cancel() atomically with its state transition to DISCONNECTING. If the cancel were deferred, the handshake completion callback could fire in the window before the cancel runs, observe the unexpected state, and return without dropping its kref on the queue. Reworking that interlock is considerably more invasive than hardening the handshake lock. Convert all hn->hn_lock acquisitions from spin_lock/spin_unlock to spin_lock_bh/spin_unlock_bh so the lock is never taken with softirqs enabled.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 28th 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: partial, 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-63980 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63980?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63980?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-63980 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.7 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.93
Linux6.186.18.35
Linux7.07.0.12
Linuxlater releases7.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13linux6.12.94-1DEBIAN-CVE-2026-63980
Debian14linux7.0.12-1DEBIAN-CVE-2026-63980
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-63980
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-63980
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-63980
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1066.69~22.04.1UBUNTU-CVE-2026-63980 USN-8903-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1068.75~22.04.1UBUNTU-CVE-2026-63980 USN-8904-1
Ubuntu22.04:LTSlinux-gcp-6.8, linux-azure-6.86.8.0-1070.78~22.04.1UBUNTU-CVE-2026-63980 USN-8904-1 USN-8905-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-149.149~22.04.1UBUNTU-CVE-2026-63980 USN-9066-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1066.67~22.04.1UBUNTU-CVE-2026-63980 USN-8906-1
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-146.146.1~22.04.1UBUNTU-CVE-2026-63980 USN-8903-2
Ubuntu22.04:LTSlinux-nvidia-6.86.8.0-1064.67~22.04.1UBUNTU-CVE-2026-63980 USN-8903-2
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1067.71~22.04.1UBUNTU-CVE-2026-63980 USN-9025-1
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2026-63980
40 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.81.1SUSE-SU-2026:4254-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_201-150700.1.3.1SUSE-SU-2026:4120-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_211-150700.15.3.1SUSE-SU-2026:4254-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-64kb, kernel-source, kernel-default and 1 more6.4.0-150700.53.81.1SUSE-SU-2026:4254-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-default-base6.4.0-150700.53.81.1.150700.17.45.1SUSE-SU-2026:4254-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-docs, kernel-syms, kernel-source and 1 more6.4.0-150700.53.81.1SUSE-SU-2026:4254-1
SUSELinux Enterprise Module for Public Cloud 15 SP7kernel-azure6.4.0-150700.53.81.1SUSE-SU-2026:4254-1
SUSELinux Micro 6.0kernel-default-base6.4.0-52.1.21.36SUSE-SU-2026:23481-1
SUSELinux Micro 6.0kernel-rt, kernel-source-rt6.4.0-52.1SUSE-SU-2026:23477-1
SUSELinux Micro 6.0kernel-source, kernel-default, kernel-kvmsmall6.4.0-52.1SUSE-SU-2026:23481-1
SUSELinux Micro 6.1kernel-default-base6.4.0-52.1.21.34SUSE-SU-2026:23529-1
SUSELinux Micro 6.1kernel-rt, kernel-source-rt6.4.0-52.1SUSE-SU-2026:23528-1
2 more for SUSE in the JSON and on SUSE's page.
Alpaquita25linux-lts6.12.95-r0BELL-CVE-2026-63980
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-63980

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A deadlock can occur in the net handshake layer because hn_lock was taken with plain spin_lock while tls_handshake_cancel can be reached from BH context through nvmet_tcp_state_change. If a process context thread on the same CPU already holds hn_lock with softirqs enabled, the softirq cancel path can spin on the same lock and stall the CPU or the affected networking path. For the CVSS the PR:N is used because a remote peer may only need reachability to the exposed NVMe/TCP TLS target path, not local code execution on the victim. The attack vector is treated as AV:A rather than AV:N because NVMe/TCP targets are normally deployed on local or trusted storage networks. Impact is denial of service due to deadlock or soft lockup. No UAF, OOB access, information disclosure, or privilege escalation primitive is indicated by the patch context.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
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 9kernelFix deferred
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-63980.

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