cve.bz

CVE-2026-98801 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: net: restrict SO_RESERVE_MEM to TCP sockets and cap max value Commit 2bb2f5fb21b0 ("net: add new socket option SO_RESERVE_MEM") and commit d00c8ee31729 ("net: fix possible NULL deref in sock_reserve_memory") only checked sk_has_account(sk), which is true for both TCP and UDP sockets. However, SO_RESERVE_MEM and sk_unused_reserved_mem() are currently only supported by TCP: - On UDP sockets, sk->sk_forward_alloc is protected by sk->sk_receive_queue.lock, whereas sock_reserve_memory() and sock_release_reserved_memory() only acquire lock_sock(sk). Concurrent UDP packet reception/release and setsockopt(SO_RESERVE_MEM) corrupt sk_forward_alloc and memcg accounting. - udp_rmem_release() reclaims excess sk_forward_alloc without accounting for sk_unused_reserved_mem(sk). Restrict sock_reserve_memory() to TCP sockets (sk_is_tcp(sk)) for now. Supporting SO_RESERVE_MEM for UDP (acquiring sk_receive_queue.lock and honoring sk_unused_reserved_mem() in udp_rmem_release()) can be done in a future net-next series if needed. In addition, reject val > SZ_1G with -EINVAL in sk_setsockopt(SO_RESERVE_MEM). Without an upper bound, values near INT_MAX cause sk_mem_pages(delta) and (pages << PAGE_SHIFT) to overflow 32-bit signed int, corrupting sk->sk_forward_alloc and sk->sk_reserved_mem. Using a page-aligned cap (SZ_1G) ensures that the page-rounded sk->sk_reserved_mem reported by getsockopt(SO_RESERVE_MEM) can always be passed back to setsockopt(SO_RESERVE_MEM).
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 6.12.113
  • Linux Linux: fixed in 6.18.56
  • Linux Linux: fixed in 7.2.10
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, Alpaquita: fixed package versions per release

Ask an AI about this CVE

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

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-98801](https://cve.bz/cve/badge/CVE-2026-98801.svg)](https://cve.bz/cve/CVE-2026-98801)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.16 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.113
Linux6.186.18.56
Linux7.27.2.10
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linuxno fix listedDEBIAN-CVE-2026-98801
Debian12linux-6.126.12.113-1~deb12u1DEBIAN-CVE-2026-98801
Debian13linux6.12.113-1DEBIAN-CVE-2026-98801
Debian14linux7.2.10-1DEBIAN-CVE-2026-98801
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-98801
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-98801
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-98801
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-98801 USN-9024-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-98801 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-98801 USN-9026-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-98801 USN-9024-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-149.149~22.04.1UBUNTU-CVE-2026-98801 USN-9066-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1069.70~22.04.1UBUNTU-CVE-2026-98801 USN-9024-1
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-149.149.1~22.04.1UBUNTU-CVE-2026-98801 USN-9024-1
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1067.71~22.04.1UBUNTU-CVE-2026-98801 USN-9025-1
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 31 moreno fix listedUBUNTU-CVE-2026-98801
43 more for Ubuntu in the JSON and on Ubuntu's page.
Azure Linux3kernelno fix listedAZL-109077
Alpaquita23linux-ltsno fix listedBELL-CVE-2026-98801
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-98801
Alpaquitastreamlinux-lts6.18.58-r0BELL-CVE-2026-98801

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

Red Hat's statement

SO_RESERVE_MEM can corrupt socket and memcg memory accounting through two related flaws. UDP receive and release paths protect sk_forward_alloc with sk_receive_queue.lock, while reservation updates use lock_sock, allowing concurrent operations to race and produce inconsistent accounting. Values near INT_MAX can also overflow sk_mem_pages(delta) and pages shifted by PAGE_SHIFT, corrupting sk_forward_alloc and sk_reserved_mem even without the UDP race. For the CVSS the PR:L value is used because a local process can create a socket and invoke setsockopt without requiring full administrative control. Remote UDP traffic may help exercise the race, but remote packets alone cannot invoke SO_RESERVE_MEM, so the issue is local rather than network reachable. The demonstrated impact is incorrect socket and memcg accounting with possible resource exhaustion or service disruption. A direct UAF, OOB access, arbitrary write, or reliable privilege escalation primitive is not established.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix 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-98801.

References

Check your stackJSON