CVE-2026-97560 linux linux
linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
- EPSS
- 0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
- Published
- Modified
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Fix and patched versions
- Linux Linux: fixed in 6.6.158
- Linux Linux: fixed in 6.12.111
- Linux Linux: fixed in 6.18.53
- Linux Linux: fixed in 7.2.7
- Linux Linux: fixed in 7.3
- Debian, Ubuntu, openSUSE, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-97560 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97560?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97560?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-97560 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.
| Product | Affected |
|---|---|
| Linux | from 6.6.64 before 6.6.158 |
| Linux | from 6.12.2 before 6.12.111 |
| Linux | from 6.11.11 before 6.12 |
| Linux | 6.13 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.6 | 6.6.158 |
| Linux | 6.12 | 6.12.111 |
| Linux | 6.18 | 6.18.53 |
| Linux | 7.2 | 7.2.7 |
| Linux | later releases | 7.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux-6.12 | 6.12.111-1~deb12u1 | DEBIAN-CVE-2026-97560 |
| Debian | 13 | linux | 6.12.111-1 | DEBIAN-CVE-2026-97560 |
| Debian | 14 | linux | 7.2.7-1 | DEBIAN-CVE-2026-97560 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-97560 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-97560 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-97560 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-97560 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-97560 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-97560 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-97560 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-hwe-6.8 | 6.8.0-149.149~22.04.1 | UBUNTU-CVE-2026-97560 USN-9066-1 |
| Ubuntu | 22.04:LTS | linux-ibm-6.8 | 6.8.0-1069.70~22.04.1 | UBUNTU-CVE-2026-97560 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-149.149.1~22.04.1 | UBUNTU-CVE-2026-97560 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-oracle-6.8 | 6.8.0-1067.71~22.04.1 | UBUNTU-CVE-2026-97560 USN-9025-1 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 31 more | no fix listed | UBUNTU-CVE-2026-97560 |
| 43 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| openSUSE | Tumbleweed | kernel-source | 7.2.9-1.1 | openSUSE-SU-2026:12074-1 |
| Azure Linux | 3 | kernel | no fix listed | AZL-104187 |
| Alpaquita | stream | linux-lts | 6.18.53-r0 | BELL-CVE-2026-97560 |
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; 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 · openSUSE · Alpaquita.
Red Hat
Red Hat rates this Moderate.
A moderate impact flaw was found in the Linux kernel SMB client (fs/smb/client/reparse.c) in smb2_parse_native_symlink(). When parsing a share-root relative native symlink, the code copies from smb_target+1 to skip the leading separator but uses strlen(smb_target)+1 as the length, reading one byte past the allocated buffer. A malicious or compromised SMB server can supply a crafted symlink target (reparse point); when a local user or workload then accesses such a symlink on a mounted SMB share (for example via a stat or path lookup), the out-of-bounds read is triggered, which can crash the kernel and cause a denial of service. Only a single byte past the string terminator is read, and the Red Hat assessment found no evidence of information disclosure, so the impact is limited to availability (Red Hat CVSS 3.1: 5.5, MODERATE, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), despite the CVE description mentioning possible exposure of sensitive kernel memory. The vulnerable code was introduced into Red Hat kernels through a backport of the 'cifs: Fix parsing native symlinks relative to the export' change and is present only in newer streams; Red Hat Enterprise Linux 6, 7, and 8, the RHEL 9.2 and 9.4 update streams and their kernel-rt builds, and OpenShift Container Platform 4.12 through 4.18 are not affected because the vulnerable code is not present there. For the affected streams (Red Hat Enterprise Linux 9 versions 9.6 and later, Red Hat Enterprise Linux 10, Red Hat In-Vehicle OS 2, and OpenShift Container Platform 4.19 and later), the fix is deferred: this one-byte out-of-bounds read has a practical consequence of a local denial of service rather than memory corruption or privilege escalation, so it does not warrant an immediate out-of-cycle update and the fix will be delivered in a future scheduled kernel update. The residual risk is a kernel crash on systems where a user accesses a crafted native symlink on an SMB share served by a malicious server.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Fix deferred | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Fix deferred |
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-97560.
References
- https://git.kernel.org/stable/c/22a9d0a9ba0c89be57558c1aa80dc60a571dd89c
- https://git.kernel.org/stable/c/2a302fdbaf7dd00d285303c94af8f48321c22993
- https://git.kernel.org/stable/c/cb26524ef4ac28fcfa554c0656e8dc412c38a8ff
- https://git.kernel.org/stable/c/d1f173d28e964ba2c3c4ebe7491d594dc8c77a40
- https://git.kernel.org/stable/c/ff411fcbfc55eec1d66ea82483d254319dc8e973