In the Linux kernel, the following vulnerability has been resolved:
sched: sch_cake: add bounds checks to host bulk flow fairness counts
Even though we fixed a logic error in the commit cited below, syzbot
still managed to trigger an underflow of the per-host bulk flow
counters, leading to an out of bounds memory access.
To avoid any such logic errors causing out of bounds memory accesses,
this commit factors out all accesses to the per-host bulk flow counters
to a series of helpers that perform bounds-checking before any
increments and decrements. This also has the benefit of improving
readability by moving the conditional checks for the flow mode into
these helpers, instead of having them spread out throughout the
code (which was the cause of the original logic error).
As part of this change, the flow quantum calculation is consolidated
into a helper function, which means that the dithering applied to the
ost load scaling is now applied both in the DRR rotation and when a
sparse flow's quantum is first initiated. The only user-visible effect
of this is that the maximum packet size that can be sent while a flow
stays sparse will now vary with +/- one byte in some cases. This should
not make a noticeable difference in practice, and thus it's not worth
complicating the code to preserve the old behaviour.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-safety flaw in the CAKE network scheduler. A low-privileged local attacker may be able to turn a counter underflow into out-of-bounds kernel memory access, potentially exposing sensitive data or crashing the host. The sources do not establish remote exploitation or exploitation in the wild.
Executive priority
Treat this as a high-priority kernel update on Linux systems with untrusted local users or confirmed CAKE use. It is not supported as an internet-wide emergency because the attack vector is local and active exploitation is not evidenced. Other applicable systems should receive the vendor kernel update during the next controlled maintenance window.
Technical view
A logic error can underflow per-host bulk-flow counters in sched/sch_cake, causing out-of-bounds memory access. The fix centralizes counter operations in bounds-checking helpers. CVSS 3.1 is 7.3 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H), indicating local exploitation with high confidentiality and availability impact.
Likely exposure
Exposure is limited to Linux systems carrying the affected sch_cake code. Exploitation is rated local and low-complexity, requires low privileges, and needs no user interaction. Risk is greatest on multi-user or tenant systems where untrusted users can reach relevant networking functionality. The bundle does not establish whether CAKE is enabled by default on any distribution.
Exploitation context
Syzbot triggered the faulty state during kernel testing, demonstrating reachability under test conditions. The CVE is not listed in KEV, and the supplied sources do not report active exploitation or public weaponization. Practical reliability, required CAKE configuration, and distribution-specific reachability remain unestablished.
Researcher notes
The fix adds bounds checks to all per-host bulk-flow counter increments and decrements, preventing counter logic errors from directly becoming out-of-bounds accesses. The bundle's normalized version lists are ambiguous and mix commit hashes with releases. Validate applicability against the CVE record, stable commits, and vendor advisories before declaring a system affected.
Mitigation direction
Apply the distribution or vendor kernel update incorporating the applicable referenced stable fix.
Follow applicable vendor advisories for product-specific packages, fixed builds, and release timing.
Restrict untrusted local access until remediation is complete.
Validation and detection
Inventory running kernel builds and identify systems where CAKE traffic scheduling is present or used.
Map each build to its distribution or vendor advisory; do not rely on upstream version numbers alone.
Verify the installed kernel includes the applicable stable fix and rebooted into the updated kernel.
Monitor relevant hosts for kernel memory faults, crashes, or scheduler-related warnings.
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-2025-21647 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
2ADP providers
12Source 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.