CVE-2025-21647 Details
Description
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.
A vulnerability in the Linux kernel's sch_cake scheduler has been addressed, which involved an underflow in the per-host bulk flow counters. This underflow led to an out-of-bounds memory access. The issue arose from a logic error that was not properly managed, allowing syzbot to exploit it. The vulnerability has been resolved by introducing bounds checks to the bulk flow fairness counts. All accesses to the per-host bulk flow counters have been refactored into a series of helper functions that perform necessary bounds-checking before any modifications. This change not only corrects the logic error but also enhances code readability by consolidating conditional checks into the helper functions, rather than having them dispersed throughout the code. As a result, the flow quantum calculation has been streamlined, although the maximum packet size that can be sent while a flow remains sparse will now vary by plus or minus one byte in some instances, a change that is not expected to have a significant practical impact.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-125 | Out-of-bounds Read | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.4.284, < 5.4.291 >= 5.10.226, < 5.10.235 >= 5.15.167, < 5.15.179 >= 6.1.110, < 6.1.125 >= 6.6.51, < 6.6.72 >= 6.10.10, < 6.11 >= 6.11.1, < 6.12.10 6.11 - 6.11 rc7 6.13 rc1 6.13 rc2 6.13 rc3 6.13 rc4 6.13 rc5 6.13 rc6 |
CPE
Remediation
| |
Change History
9 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | siemens-SADP |
| May 12, 2026 | CVE Modified | siemens-SADP |
| Nov 3, 2025 | CVE Modified | CVE |
| Nov 3, 2025 | CVE Modified | CVE |
| Sep 26, 2025 | Initial Analysis | [email protected] |
| Mar 13, 2025 | CVE Modified | kernel.org |
| Jan 19, 2025 | New CVE Received | kernel.org |