[CVE-2026-63980][MODERATE REGULAR] net/handshake: Use spin_lock_bh for hn_lock [ Upstream

[CVE-2026-63980][MODERATE REGULAR] net/handshake: Use spin_lock_bh for hn_lock [ Upstream

[AL-KERNEL]

CVE: CVE-2026-63980
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net/handshake: Use spin_lock_bh for hn_lock [ Upstream
Commit: 06ab5978866fc2221b910347fd3e510ca8e7b1a4
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=06ab5978866fc2221b910347fd3e510ca8e7b1a4
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-63980
Analysis date: Sun, 19 Jul 2026 14:15:00 -0400
ActionableScore: 4
ActionableScore lower bound: 3
Actionable bucket: Borderline, manual review recommended / Actionable Moderate watchlist
Manual review required: YES

Summary:
A network-adjacent NVMe/TCP TLS teardown path can call `tls_handshake_cancel()` from BH context while `hn_lock` is held in process context, causing a spinlock deadlock and denial of service without evidence of memory corruption or privilege escalation.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-63980 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-63980

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE REGULAR
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-63980	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';CWE-667;*CWE-833;CWE-362;BEST CVSS score: '5.3';DESCR '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.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline, manual review recommended / Actionable Moderate watchlist (with actual score 4)	YES	LOCK DEADLOCK DANGER RACE HARDWARE  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	YES	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=4
ActionableScoreLower=3

## 1. ActionableScore

* Conservative score: 3
* Paranoid score: 4
* Final recommended bucket: **Borderline, manual review recommended / Actionable Moderate watchlist**

## 2. Signal breakdown

* Remote reachable / network-triggerable: +2
  The affected path is reachable through NVMe/TCP with TLS handshake support. This is not a general Internet-facing networking path, but a remote NVMe/TCP peer on the storage network can plausibly influence the socket state-change path.

* Reliable kernel crash / strong DoS: +1
  The described failure mode is a same-CPU softirq/process-context spinlock deadlock, which can stall the CPU or affected networking/storage path.

* Availability impact realistic: +1
  The deadlock can be persistent until watchdog intervention, recovery, or reboot. This is stronger than a transient warning.

* Hard or timing-dependent race: -1
  Triggering requires an interleaving where process context holds `hn_lock` while the BH/softirq cancellation path runs on the same CPU.

* No memory corruption: +0
  The patch changes locking from `spin_lock()` to `spin_lock_bh()`. It does not show UAF, OOB access, double free, refcount misuse, type confusion, or attacker-controlled memory reuse.

* No plausible privilege escalation primitive: +0
  The bug is a deadlock/DoS condition. There is no evidence of writable stale object access, callback corruption, arbitrary write, or object replacement.

* Paranoid elevation rationale: +1 practical scrutiny
  The higher score is justified only for triage sensitivity because the issue is network-adjacent and affects NVMe/TCP TLS teardown/cancel paths. It should not be treated as Important-class memory corruption.

## 3. Reachability analysis

A remote NVMe/TCP peer may be able to trigger the relevant socket state-change and cancellation path if NVMe/TCP target TLS handshake support is enabled and reachable. In typical deployments, NVMe/TCP targets are placed on isolated storage or data-center networks, not the public Internet. No local code execution on the victim is necessarily required in the network-peer model, so PR:N is reasonable for CVSS-style reachability, but the practical exposure is narrower than ordinary AV:N Internet-facing services.

Namespaces and containers do not appear central to the trigger. The affected code is in the kernel net handshake infrastructure used here by the NVMe/TCP target TLS upcall path. The feature is configuration-dependent and requires the relevant NVMe/TCP TLS target setup.

Call-site confidence: high, because the commit message explicitly identifies `nvmet_tcp_state_change()` in BH context reaching `tls_handshake_cancel()` and `handshake_req_cancel()`.

## 4. Severity interpretation

This behaves like an actionable DoS-oriented Moderate issue, not an Important-class memory corruption vulnerability. The theoretical impact is kernel or CPU lockup due to an invalid locking context. The realistic evidence supports availability impact only. There is no demonstrated confidentiality impact, integrity impact, UAF, arbitrary write, or privilege escalation path.

The conservative result is borderline Moderate. The paranoid score reaches Actionable Moderate watchlist level because the trigger is network-adjacent and the affected service is a storage protocol path where availability matters.

## 5. One-sentence report phrase

A network-adjacent NVMe/TCP TLS teardown path can call `tls_handshake_cancel()` from BH context while `hn_lock` is held in process context, causing a spinlock deadlock and denial of service without evidence of memory corruption or privilege escalation.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Manual review is recommended because the issue is network-adjacent and affects a storage protocol teardown path, but it does not currently justify Important severity because the demonstrated primitive is deadlock-based DoS only.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: net/handshake: Use spin_lock_bh for hn_lock [ Upstream
Commit: 06ab5978866fc2221b910347fd3e510ca8e7b1a4
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=06ab5978866fc2221b910347fd3e510ca8e7b1a4

Changed files:
  net/handshake/netlink.c
  net/handshake/request.c
  net/handshake/tlshd.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=06ab5978866fc2221b910347fd3e510ca8e7b1a4

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-63980 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-63980

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: Not available
  The Best / paranoid CVSS vector: AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.3

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 3
  Paranoid ActionableScore: 4

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): MODERATE REGULAR

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).