Skip to main content
VulnerabilityPublished Updated

CVE-2026-97597: Linux kernel · ipv6: flowlabel: cap duplicate leases per socket

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in 467467bf4209f9f8add0c648bae763f92a0224c3 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 467467bf4209f9f8add0c648bae763f92a0224c3, 0159f716d8adbe85951cdf008d0afe27d874eaa6, 8d6cd188508513503805c156165de38e4e4a8615 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 467467bf4209f9f8add0c648bae763f92a0224c3
Fixed in
  • 467467bf4209f9f8add0c648bae763f92a0224c3
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 0159f716d8adbe85951cdf008d0afe27d874eaa6
Fixed in
  • 0159f716d8adbe85951cdf008d0afe27d874eaa6
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 8d6cd188508513503805c156165de38e4e4a8615
Fixed in
  • 8d6cd188508513503805c156165de38e4e4a8615
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 6d917992c22b6029fc2dc1bd464b7f6709357161
Fixed in
  • 6d917992c22b6029fc2dc1bd464b7f6709357161
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 2f1a6dd5c80ceb902f50449efe899f29cd7918e3
Fixed in
  • 2f1a6dd5c80ceb902f50449efe899f29cd7918e3
LinuxLinuxAffected
  • =2.6.12
Fixed in–

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.

References

Community reviews

Loading reviews…