cve.bz

CVE-2026-99056 linux linux

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: strparser: make sure __strp_recv isn't running before tearing down the parser The comment above strp_done() claims that if strp is stopped, strp_recv will no longer be called. That's only true if the caller has a mechanism (eg locking) to guarantee that strp_recv() calls that started before strp_stop() have completed by the time we call strp_done(). This adds a dummy lock_sock/release_sock pair to guarantee that any in-flight strp_recv() (which runs under either bh_lock_sock or lock_sock, depending if it's called from ->sk_data_ready or strp_work) has completed. Only espintcp can be affected by this race condition, but this patch makes sure no future user of strp can have the bug. This could crash on strp->sk ("general mode" of strp), but this mode has been here for 9 years and has never been used. It'll be gone soon, no point worrying about it. Switch the stopped/paused/etc bits to u8's to avoid races between strp_stop() and strp_pause/unpause(). A reproducer has been published and turns the possible UAF into an exploit [1].

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 6th 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 5.10.273
  • Linux Linux: fixed in 5.15.224
  • Linux Linux: fixed in 6.1.191
  • Linux Linux: fixed in 6.6.160
  • Linux Linux: fixed in 6.12.113
  • Linux Linux: fixed in 6.18.57
  • Linux Linux: fixed in 7.2.11
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-99056 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99056?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99056?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-99056 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.

Badge for a README or a site

CVE-2026-99056

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-99056](https://cve.bz/cve/badge/CVE-2026-99056.svg)](https://cve.bz/cve/CVE-2026-99056)

HTML:

<a href="https://cve.bz/cve/CVE-2026-99056"><img src="https://cve.bz/cve/badge/CVE-2026-99056.svg" alt="CVE-2026-99056"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.6 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.273
Linux5.155.15.224
Linux6.16.1.191
Linux6.66.6.160
Linux6.126.12.113
Linux6.186.18.57
Linux7.27.2.11
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.192-1DEBIAN-CVE-2026-99056
Debian13linux6.12.113-1DEBIAN-CVE-2026-99056
Debian14linux7.2.11-1DEBIAN-CVE-2026-99056
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-99056
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-99056
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-99056
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 48 moreno fix listedUBUNTU-CVE-2026-99056
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-99056 USN-9024-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-99056 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-99056 USN-9026-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-99056 USN-9024-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-149.149~22.04.1UBUNTU-CVE-2026-99056 USN-9066-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1069.70~22.04.1UBUNTU-CVE-2026-99056 USN-9024-1
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-149.149.1~22.04.1UBUNTU-CVE-2026-99056 USN-9024-1
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1067.71~22.04.1UBUNTU-CVE-2026-99056 USN-9025-1
51 more for Ubuntu in the JSON and on Ubuntu's page.
Azure Linux3kernel6.6.161.1-1AZL-110939
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-99056
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-99056
Alpaquitastreamlinux-lts6.18.58-r0BELL-CVE-2026-99056

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 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 · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important severity flaw because an authenticated local user can leverage a use-after-free condition in the kernel to achieve complete privilege escalation or cause a system crash, without requiring physical access or administrative privileges. Although the underlying race condition specifically affects teardown handling in the stream parser when processing ESP encapsulated over TCP (espintcp) sockets, the resulting memory corruption directly compromises host kernel integrity. Typical Red Hat Enterprise Linux deployments hosting multi-tenant workloads or unprivileged users with local socket access are primarily exposed to this risk.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-11-02) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to synchronize stream parser teardown with in-flight receive processing and convert parser state flags to independent members to prevent use-after-free conditions: upgrade to the fixed Kernel/Kernel Rt/Kernel Ivos Qualcomm/Openshift/Ose Rhel Coreos/Kpatch builds, which adds a lock_sock and release_sock pair in strp_done to wait for active receive processing to finish and converts parser state bitfield flags into u8 members, closing all 2 injection vectors (concurrent socket stream parser teardown during in-flight receive processing, unsynchronized bitfield state updates between parser stop and pause operations). Until patched, this is only a concern on Linux multi-tenant systems or hosts granting unprivileged local users access to create and tear down stream parser sockets such as espintcp — Non-Linux platforms are unaffected — so Restrict unprivileged local user access and constrain process capabilities to prevent unauthorized local users from creating or manipulating espintcp stream parser sockets. As a compensating measure, Enable runtime memory error detection with KASAN or HWASan to detect use-after-free memory errors at runtime using allocation quarantines and redzones, Enable SLAB freelist hardening to randomize freelist allocation order and validate freelist pointer integrity against exploitation, Enforce SELinux in enforcing mode to constrain unprivileged processes and limit post-exploitation actions, Enable KASLR to randomize kernel code locations and impede ROP chain construction, Enable SMEP to prevent the kernel from executing userspace shellcode if control flow is redirected, and Enable SMAP to prevent kernel dereferences of userspace memory structures used to forge freed socket or parser objects. These controls limit blast radius and contain exploitation, but they do not fix the underlying stream parser use-after-free race condition — apply the upstream patch to fully remediate.

Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelAffected
Red Hat Enterprise Linux 8kernel-rtAffected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtAffected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Affected

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-99056.

References

Check your stackJSON