Full vulnerability report · 2026

CVE-2026-63980High confidence

net/handshake: Use spin_lock_bh for hn_lock

Linux · Linux

7.5HighCVSS 3.1

Recommended action

Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product

Operational reassessment

Published severity in operational context

Open reassessment dashboard →

Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

No CISA KEV confirmation is currently recorded.
The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
EPSS is 0.63% for the current model date.

Compensating controls

Validate the affected product branch and deploy the verified fixed release.
Restrict the affected network interface to trusted sources where business-safe.
Monitor vendor guidance and exploitation sources for a material change.

Verification

Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Canonical Ubuntu Security: 20 affected package states with no published fix

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states

Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution release	Source package	Vendor state	Fixed version	Evidence
Debian trixietrixie · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.12.94-1`	Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · source	`linux`	Not affectedDebian marks this release not affected (fixed-version marker 0).	`Not published in this feed`	Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`7.0.12-1`	Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`7.0.12-1`	Debian Security Tracker ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 7 Oct 2026

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current

CVE-2026-63980 · CSAF 2.0 · revision 12 · interimSUSE Product Security TeamCVE-2026-63980

91 known affected

The vendor explicitly identifies these products as affected by this CVE.

kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7

Summary: 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.
Remediation: To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

Recommended actionPatch only the product branches with a verified fix

Fix availability varies by product

What, why and how

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.

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Network
Privileges required: None: unauthenticated exploitation is possible
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration.: CWE not yet assigned
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

NetworkUnauthenticated

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-45753Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗

Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-63971 Référence CVE CVE-2026-63972 https://www.cve.org/CVERecord?id=CVE-2026-63972 Référence CVE CVE-2026-63973 https://www.cve.org/CVERecord?id=CVE-2026-63973 Référence CVE CVE-2026-63974 https://www.cve.org/CVERecord?id=CVE-2026-63974 Référence CVE CVE-2026-63975 https://www.cve.org/CVERecord?id=CVE-2026-63975 Référence CVE CVE-2026-63976 https://www.cve.org/CVERecord?id=CVE-2026-63976 Référence CVE CVE-2026-63977 https://www.cve.org/CVERecord?id=CVE-2026-63977 Référence CVE CVE-2026-63978 https://www.cve.org/CVERecord?id=CVE-2026-63978 Référence CVE CVE-2026-63979 https://www.cve.org/CVERecord?id=CVE-2026-63979 Référence CVE CVE-2026-63980 https://www.cve.org/CVERecord?id=CVE-2026-63980 Référence CVE CVE-2026-63981 https://www.cve.org/CVERecord?id=CVE-2026-63981 Référence CVE CVE-2026-63982 https://www.cve.org/CVERecord?id=CVE-2026-63982 Référence CVE CVE-2026-63983 https://www.cve.org/CVERecord?id=CVE-2026-63983 Référence CVE CVE-2026-63984 https://www.cve.org/CVERecord?id=CVE-2026-63984 Référence CVE CVE-2026-63985 https://www.cve.org/CVERecord?id=CVE-2026-63985 Référence CVE CVE-2026-63986 https://www.cve.org/CVERecord?id=CVE-2026-63986 Référence CVE CVE-2026-63987 https://www.cve.org/CVERecord?id=CVE-2026-63987 Référence CVE CVE-2026-63988 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1202Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-63925 Référence CVE CVE-2026-63926 https://www.cve.org/CVERecord?id=CVE-2026-63926 Référence CVE CVE-2026-63928 https://www.cve.org/CVERecord?id=CVE-2026-63928 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63969 https://www.cve.org/CVERecord?id=CVE-2026-63969 Référence CVE CVE-2026-63970 https://www.cve.org/CVERecord?id=CVE-2026-63970 Référence CVE CVE-2026-63972 https://www.cve.org/CVERecord?id=CVE-2026-63972 Référence CVE CVE-2026-63973 https://www.cve.org/CVERecord?id=CVE-2026-63973 Référence CVE CVE-2026-63980 https://www.cve.org/CVERecord?id=CVE-2026-63980 Référence CVE CVE-2026-63985 https://www.cve.org/CVERecord?id=CVE-2026-63985 Référence CVE CVE-2026-63990 https://www.cve.org/CVERecord?id=CVE-2026-63990 Référence CVE CVE-2026-63992 https://www.cve.org/CVERecord?id=CVE-2026-63992 Référence CVE CVE-2026-63995 https://www.cve.org/CVERecord?id=CVE-2026-63995 Référence CVE CVE-2026-63996 https://www.cve.org/CVERecord?id=CVE-2026-63996 Référence CVE CVE-2026-63997 https://www.cve.org/CVERecord?id=CVE-2026-63997 Référence CVE CVE-2026-63998 https://www.cve.org/CVERecord?id=CVE-2026-63998 Référence CVE CVE-2026-63999 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63952 https://www.cve.org/CVERecord?id=CVE-2026-63952 Référence CVE CVE-2026-63974 https://www.cve.org/CVERecord?id=CVE-2026-63974 Référence CVE CVE-2026-63975 https://www.cve.org/CVERecord?id=CVE-2026-63975 Référence CVE CVE-2026-63976 https://www.cve.org/CVERecord?id=CVE-2026-63976 Référence CVE CVE-2026-63978 https://www.cve.org/CVERecord?id=CVE-2026-63978 Référence CVE CVE-2026-63979 https://www.cve.org/CVERecord?id=CVE-2026-63979 Référence CVE CVE-2026-63980 https://www.cve.org/CVERecord?id=CVE-2026-63980 Référence CVE CVE-2026-63984 https://www.cve.org/CVERecord?id=CVE-2026-63984 Référence CVE CVE-2026-63992 https://www.cve.org/CVERecord?id=CVE-2026-63992 Référence CVE CVE-2026-63993 https://www.cve.org/CVERecord?id=CVE-2026-63993 Référence CVE CVE-2026-63994 https://www.cve.org/CVERecord?id=CVE-2026-63994 Référence CVE CVE-2026-64000 https://www.cve.org/CVERecord?id=CVE-2026-64000 Référence CVE CVE-2026-64007 https://www.cve.org/CVERecord?id=CVE-2026-64007 Référence CVE CVE-2026-64010 https://www.cve.org/CVERecord?id=CVE-2026-64010 Référence CVE CVE-2026-64011 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1164Multiples vulnérabilités dans le noyau Linux de SUSE

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Fix availability varies by product
Affected: kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-default as component of SUSE Linux Enterprise Module for Legacy 15 SP7
kernel-source as component of SUSE Linux Enterprise Module for Legacy 15 SP7
reiserfs-kmp-default as component of SUSE Linux Enterprise Module for Legacy 15 SP7
kernel-default as component of SUSE Linux Enterprise Module for Public Cloud 15 SP7
kernel-source as component of SUSE Linux Enterprise Module for Public Cloud 15 SP7
cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
gfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-default-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-macros as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-source as component of SUSE Linux Enterprise Server 15 SP6-LTSS
ocfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
reiserfs-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
and 61 more
Fixed: Linux: < 6.7, 6.12.93 ≤ 6.12.*, 6.18.35 ≤ 6.18.*, 7.0.12 ≤ 7.0.*, 7.1 ≤ *
Action: Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround: No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

Evidence and provenance

Published 19 Jul 2026 · Last source change 5 Aug 2026, 12:37 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2

CVSS sourceCNA

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2026-45753

Product sourceVendor CSAF · SUSE Product Security Team

Remediation sourceVendor CSAF · SUSE Product Security Team

CWE sourceUnavailable

NVD statusNVD awaiting enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2026-07-19CVE published

2026-08-05Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-45753↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

net/handshake: Use spin_lock_bh for hn_lock

Published severity in operational context

Evidence used

Compensating controls

Verification

Remediation availability differs by product scope

Release-specific package status

Authoritative vendor CSAF and VEX advisories

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2026-45753

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication