In the Linux kernel, the following vulnerability has been resolved:
net: ipv6: flowlabel: defer exclusive option free until RCU teardown
`ip6fl_seq_show()` walks the global flowlabel hash under the seq-file
RCU read-side lock and prints `fl->opt->opt_nflen` when an option block
is present.
Exclusive flowlabels currently free `fl->opt` as soon as `fl->users`
drops to zero in `fl_release()`. However, the surrounding
`struct ip6_flowlabel` remains visible in the global hash table until
later garbage collection removes it and `fl_free_rcu()` finally tears it
down.
A concurrent `/proc/net/ip6_flowlabel` reader can therefore race that
early `kfree()` and dereference freed option state, triggering a crash
in `ip6fl_seq_show()`.
Fix this by keeping `fl->opt` alive until `fl_free_rcu()`. That matches
the lifetime already required for the enclosing flowlabel while readers
can still reach it under RCU.
Security readout for executives and security teams
Plain-English summary
A Linux kernel memory-lifetime error can let a low-privileged local user trigger a race involving IPv6 flow labels and a procfs reader. The documented outcome is a kernel crash, potentially disrupting the host. Although the CVSS assessment lists broader impact, the supplied technical description does not establish data theft, modification, or privilege escalation.
Executive priority
Treat this as a high-priority local denial-of-service risk, especially on multi-user, hosting, container, or appliance environments. Schedule kernel updates through normal emergency-patching controls. Immediate isolation is not supported by the supplied evidence unless crashes or suspicious local activity are observed.
Technical view
An exclusive IPv6 flow label can free its option block when its user count reaches zero, while the enclosing flow-label object remains visible under RCU. A concurrent /proc/net/ip6_flowlabel reader may dereference that freed block in ip6fl_seq_show(), causing a use-after-free and crash. The fix defers freeing the options until RCU teardown.
Likely exposure
Exposure is limited to affected Linux kernel builds where a low-privileged local actor can exercise IPv6 flow-label behavior. The supplied version data is ambiguous, so determine status through distribution advisories, package changelogs, or the listed stable-kernel fixes. The sources do not demonstrate remote reachability.
Exploitation context
The CVSS 3.1 score is 7.8 with local access, low complexity, low privileges, and no user interaction. The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. The documented demonstrated effect is a kernel crash.
Researcher notes
The central issue is mismatched lifetimes between fl->opt and struct ip6_flowlabel under RCU visibility. Researchers should distinguish the documented use-after-free crash from the CVSS vector's theoretical confidentiality and integrity impacts. The supplied material does not prove controlled memory corruption, privilege escalation, remote attackability, or exploitation in the wild.
Mitigation direction
Update to a vendor-supported kernel containing the applicable stable fix or downstream backport.
Consult Linux distribution and appliance-vendor advisories for package-specific fixed versions.
Prioritize shared systems where untrusted or low-privileged users can execute local workloads.
Apply normal access controls while patching; the sources name no configuration-based workaround.
Validation and detection
Inventory running kernel and distribution package versions across Linux hosts and appliances.
Compare each package against vendor advisories and the listed upstream stable fixes.
Verify the relevant fix commit or documented downstream backport is present.
Review kernel crash records for faults involving ip6fl_seq_show or IPv6 flow-label handling.
After updating, confirm hosts booted into the remediated kernel rather than an older installed build.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-31680 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
11Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.