- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 87% 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: ipv6: flowlabel: cap duplicate leases per socket ipv6_flowlabel_get() allocates an ipv6_fl_socklist entry for every successful GET. The recheck path for a compatible existing flowlabel links another lease without applying any lease admission check. Repeated GET requests for one shareable label can therefore grow a socket's lease list without bound. Reject a new unprivileged lease once the socket already holds FL_MAX_PER_SOCK leases. Check this on the shared recheck path so reuse of a globally interned label, including the fl_intern() collision path, is covered as well. New-label admission remains under the existing mem_check() policy. Use capable(CAP_NET_ADMIN) rather than ns_capable(), matching mem_check(). An unprivileged user must not bypass the cap by creating a user namespace and a netns where they have CAP_NET_ADMIN, which would still consume host memory. Check the capability only when the socket reaches the limit, so successful unprivileged GET requests below the cap do not generate a capability audit. Do the admission check before updating linger and expires so a rejected GET does not refresh the shared label, matching the existing socket-list allocation failure path.
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
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 87% of all CVEs (11 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 42abef116bb2265eeccae55a0dc91a9f1546f74c
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 0159f716d8adbe85951cdf008d0afe27d874eaa6
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 6d917992c22b6029fc2dc1bd464b7f6709357161
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2f1a6dd5c80ceb902f50449efe899f29cd7918e3
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 467467bf4209f9f8add0c648bae763f92a0224c3
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8d6cd188508513503805c156165de38e4e4a8615
- affected 2.6.12
- unaffected < 2.6.12
- 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
References6
- https://git.kernel.org/stable/c/42abef116bb2265eeccae55a0dc91a9f1546f74c (opens in a new tab)
- https://git.kernel.org/stable/c/0159f716d8adbe85951cdf008d0afe27d874eaa6 (opens in a new tab)
- https://git.kernel.org/stable/c/6d917992c22b6029fc2dc1bd464b7f6709357161 (opens in a new tab)
- https://git.kernel.org/stable/c/2f1a6dd5c80ceb902f50449efe899f29cd7918e3 (opens in a new tab)
- https://git.kernel.org/stable/c/467467bf4209f9f8add0c648bae763f92a0224c3 (opens in a new tab)
- https://git.kernel.org/stable/c/8d6cd188508513503805c156165de38e4e4a8615 (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-86728 (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-97597)Record last updated .