cve.bz

CVE-2026-97985 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. 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: af_unix: Update last skb marker in manage_oob(). Fahad Alharbi reported that blocking recv(MSG_PEEK) could hog CPU due to OOB skb. In the following cases, manage_oob() skips OOB skb(s) and returns NULL for the last recv(MSG_PEEK): socketpair(AF_UNIX, SOCK_STREAM, 0, sk); 1) skb -> OOB skb -> NULL send(sk[0], "ab", 2, MSG_OOB); recv(sk[1], buf, 0, MSG_PEEK); 2) skb -> consumed OOB skb -> NULL send(sk[0], "ab", 2, MSG_OOB); recv(sk[1], buf, 1, MSG_OOB); recv(sk[1], buf, 0, MSG_PEEK); 3) consumed OOB skb -> OOB skb -> NULL send(sk[0], "a", 1, MSG_OOB); recv(sk[1], buf, 0, MSG_OOB); send(sk[0], "b", 1, MSG_OOB); recv(sk[1], buf, 1, MSG_PEEK); Then, @copied is 0 in unix_stream_read_generic() (zero-length buffer, or non-OOB skb is not yet consumed), and unix_stream_data_wait() is called. However, it returns immediately because @last is not updated in unix_stream_read_generic(), and the thread busy-waits for a new skb. Let's update @last in manage_oob(). For MSG_PEEK, @last is updated with the skipped OOB, and for the non-peek case, @last matches the returned value (when !copied) because OOB is unlinked. Note that manage_oob() is inlined and no stack canary is added.
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; 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 6.6.160
  • 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 promptExplain CVE-2026-97985 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97985?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97985?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-97985 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.

ProductAffected
Linuxfrom 6.6.29 before 6.6.160
Linuxfrom 5.15.157 before 5.16
Linuxfrom 6.1.88 before 6.2
Linuxfrom 6.8.8 before 6.9
Linux6.9 and later

Fixed in

ProductRelease lineFixed in
Linux6.66.6.160
Linux6.126.12.111
Linux6.186.18.53
Linux7.27.2.7
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linuxno fix listedDEBIAN-CVE-2026-97985
Debian12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-97985
Debian13linux6.12.111-1DEBIAN-CVE-2026-97985
Debian14linux7.2.7-1DEBIAN-CVE-2026-97985
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-97985
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-97985
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-97985
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 48 moreno fix listedUBUNTU-CVE-2026-97985
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-97985 USN-9024-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-97985 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-97985 USN-9026-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-97985 USN-9024-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-149.149~22.04.1UBUNTU-CVE-2026-97985 USN-9066-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1069.70~22.04.1UBUNTU-CVE-2026-97985 USN-9024-1
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-149.149.1~22.04.1UBUNTU-CVE-2026-97985 USN-9024-1
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1067.71~22.04.1UBUNTU-CVE-2026-97985 USN-9025-1
47 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.2.9-1.1openSUSE-SU-2026:12074-1
Azure Linux3kernelno fix listedAZL-104352
Alpaquita23linux-ltsno fix listedBELL-CVE-2026-97985
Alpaquita25linux-lts6.12.111-r0BELL-CVE-2026-97985
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-97985

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

Red Hat's statement

Red Hat rates this Linux kernel flaw, which affects the AF_UNIX (Unix domain socket) implementation in Red Hat Enterprise Linux 10 and Red Hat In-Vehicle OS 2, as LOW severity. A local unprivileged user can create an AF_UNIX stream socketpair, send out-of-band (OOB) data, and issue blocking recv() calls (including with MSG_PEEK). In certain sequences, manage_oob() skips the OOB skb without updating the internal last-skb marker, so unix_stream_data_wait() returns immediately instead of sleeping; the receiving thread then busy-waits in a tight loop and consumes excessive CPU, causing a local denial of service. The issue is limited to CPU consumption on the local host: AF_UNIX sockets provide local inter-process communication and are not network reachable, and there is no memory corruption, information disclosure, or privilege escalation. Although the CVSS:3.1 base score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) corresponds to Moderate, Red Hat assesses the overall severity as LOW given the limited, availability-only local impact. The fix is deferred for the affected RHEL 10 and Red Hat In-Vehicle OS streams because of this low severity; the residual risk is that a local user could degrade system performance or availability by repeatedly triggering the busy-wait. RHEL 7 through RHEL 9 kernels (including kernel-rt) and the OpenShift Container Platform RHCOS images are not affected because the vulnerable code is not present, and RHEL 6 is out of support scope.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not 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-97985.

References

Check your stackJSON