CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HHigh (7.5) in linux linux. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExplain CVE-2026-97524 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97524?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97524?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-97524 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | from 5.10.228 before 5.10.271 |
| Linux | from 5.15.169 before 5.15.222 |
| Linux | from 6.1.113 before 6.1.189 |
| Linux | from 6.6.57 before 6.6.158 |
| Linux | from 6.11.4 before 6.12 |
| Linux | 6.12 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 5.10 | 5.10.271 |
| Linux | 5.15 | 5.15.222 |
| Linux | 6.1 | 6.1.189 |
| 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 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | 6.1.190-1 | DEBIAN-CVE-2026-97524 |
| Debian | 12 | linux-6.12 | 6.12.111-1~deb12u1 | DEBIAN-CVE-2026-97524 |
| Debian | 13 | linux | 6.12.111-1 | DEBIAN-CVE-2026-97524 |
| Debian | 14 | linux | 7.2.7-1 | DEBIAN-CVE-2026-97524 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-97524 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-97524 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-97524 |
| Ubuntu | 22.04:LTS | linux | 5.15.0-202.212 | UBUNTU-CVE-2026-97524 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-aws | 5.15.0-1119.126 | UBUNTU-CVE-2026-97524 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-97524 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure | 5.15.0-1125.134 | UBUNTU-CVE-2026-97524 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-97524 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde | 5.15.0-1124.133 | UBUNTU-CVE-2026-97524 USN-8962-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-97524 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp | 5.15.0-1120.130 | UBUNTU-CVE-2026-97524 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-97524 USN-9024-1 |
| 77 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-104583 |
| Alpaquita | 23 | linux-lts | 6.1.189-r0 | BELL-CVE-2026-97524 |
| Alpaquita | 25 | linux-lts | 6.12.111-r0 | BELL-CVE-2026-97524 |
| Alpaquita | stream | linux-lts | 6.18.53-r0 | BELL-CVE-2026-97524 |
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 rates this Moderate.
An MPTCP subflow reset can recursively reenter the receive path through a state change and attempt to acquire the data lock again under rare error conditions. A malformed or corrupted DSS mapping from a remote MPTCP peer can also cause reset processing to purge the receive queue while the current skb is still being processed, creating a plausible use after free or double free condition. For the CVSS the PR:N because the remote peer does not need local access or elevated privileges beyond the ability to establish or interact with an affected MPTCP connection. The issue is network reachable where MPTCP is enabled and exposed to untrusted peers. Impact is at least denial of service through a lockup or kernel crash. In the paranoid case confidentiality and integrity impact are rated High because the skb lifetime error is a plausible memory corruption candidate and should be reviewed manually.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Affected | |
| 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 | Affected | |
| 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 | Affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | 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-97524.