CVE-2026-97939ipmr: account multicast table and route memory
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ipmr: account multicast table and route memory A netadmin in a user+net namespace can create many IPv4 and IPv6 multicast routing tables with MRT_TABLE and MRT6_TABLE. Each unseen id allocates an mr_table via the shared mr_table_alloc(), links it into the per-net list, and leaves it until netns teardown. Those objects were not charged to memcg, so the host unreclaimable slab grows with the table count. Account mr_table allocations with GFP_KERNEL_ACCOUNT and mark the IPv4/IPv6 MFC caches SLAB_ACCOUNT. This matches the established handling of IP addresses, routes and alternate interface names. Unresolved MFC entries are still allocated from softIRQ with GFP_ATOMIC and are not charged. They expire after 10 seconds and are bounded by the socket receive queue; see commit 0079ad8e8dc3 ("ipmr: remove hard code cache_resolve_queue_len limit").
Timeline
ID reserved
By Linux
Published
- 35 days later
· 35 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.22% · top 88% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected f0ad0860d01e47a3ffd220564c5c653b3afbe962 – < 3e808d8dfebd8f114a747bd90c8f7d2a6fd7474f
- affected f0ad0860d01e47a3ffd220564c5c653b3afbe962 – < 57c523e95ea2608a19e6bfcd664d641ddf7bc4b4
- affected f0ad0860d01e47a3ffd220564c5c653b3afbe962 – < 20424f267c9dbdfcade28b2b2306767a7dfb43d1
- affected f0ad0860d01e47a3ffd220564c5c653b3afbe962 – < 21e0749e8ef272ac7e3eefe0fa488a5983f4b038
- affected f0ad0860d01e47a3ffd220564c5c653b3afbe962 – < ec1c6140394ee87127479bc500a3158b125bf07a
- affected f0ad0860d01e47a3ffd220564c5c653b3afbe962 – < 0264b3ee09b118fec8a5471b4ca288f8ab84722f
- affected f0ad0860d01e47a3ffd220564c5c653b3afbe962 – < d0a2e2a4ee6bfe51e398bfb6921a7d0f4c26bc1c
- affected f0ad0860d01e47a3ffd220564c5c653b3afbe962 – < b7ee18725f2292ab554aa96a101ae42d45f008bd
- affected 2.6.35
- unaffected < 2.6.35
- unaffected 5.10.273 – ≤ 5.10.*
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/3e808d8dfebd8f114a747bd90c8f7d2a6fd7474f (opens in a new tab)
- https://git.kernel.org/stable/c/57c523e95ea2608a19e6bfcd664d641ddf7bc4b4 (opens in a new tab)
- https://git.kernel.org/stable/c/20424f267c9dbdfcade28b2b2306767a7dfb43d1 (opens in a new tab)
- https://git.kernel.org/stable/c/21e0749e8ef272ac7e3eefe0fa488a5983f4b038 (opens in a new tab)
- https://git.kernel.org/stable/c/ec1c6140394ee87127479bc500a3158b125bf07a (opens in a new tab)
- https://git.kernel.org/stable/c/0264b3ee09b118fec8a5471b4ca288f8ab84722f (opens in a new tab)
- https://git.kernel.org/stable/c/d0a2e2a4ee6bfe51e398bfb6921a7d0f4c26bc1c (opens in a new tab)
- https://git.kernel.org/stable/c/b7ee18725f2292ab554aa96a101ae42d45f008bd (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86793 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97939)Record last updated .