Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-21647sched: sch_cake: add bounds checks to host bulk flow fairness counts

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.

Timeline

  1. ID reserved

    By Linux

  2. · 21 days later

    Published

  3. · 21 months 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

CVSS scores of CVE-2025-21647, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
NVDNVD · Modified3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.3.

Affected products

  • Linux · Linux

    • affected 4a4eeefa514db570be025ab46d779af180e2c9bb – < 44fe1efb4961c1a5ccab16bb579dfc6b308ad58b
    • affected 7725152b54d295b7da5e34c2f419539b30d017bd – < b1a1743aaa4906c41c426eda97e2e2586f79246d
    • affected cde71a5677971f4f1b69b25e854891dbe78066a4 – < bb0245fa72b783cb23a9949c5048781341e91423
    • affected 549e407569e08459d16122341d332cb508024094 – < a777e06dfc72bed73c05dcb437d7c27ad5f90f3f
    • affected d4a9039a7b3d8005b90c7b1a55a306444f0e5447 – < 27202e2e8721c3b23831563c36ed5ac7818641ba
    • affected 546ea84d07e3e324644025e2aae2d12ea4c5896e – < 91bb18950b88f955838ec0c1d97f74d135756dc7
    • affected 546ea84d07e3e324644025e2aae2d12ea4c5896e – < 737d4d91d35b5f7fa5bb442651472277318b0bfd
    • affected d7c01c0714c04431b5e18cf17a9ea68a553d1c3c
    • affected 5.4.284 – < 5.4.291
    • affected 5.10.226 – < 5.10.235
    • affected 5.15.167 – < 5.15.179
    • affected 6.1.110 – < 6.1.125
    • affected 6.6.51 – < 6.6.72
    • affected 6.10.10 – < 6.11
  • Linux · Linux

    • affected 6.11
    • unaffected < 6.11
    • unaffected 5.4.291 – ≤ 5.4.*
    • unaffected 5.10.235 – ≤ 5.10.*
    • unaffected 5.15.179 – ≤ 5.15.*
    • unaffected 6.1.125 – ≤ 6.1.*
    • unaffected 6.6.72 – ≤ 6.6.*
    • unaffected 6.12.10 – ≤ 6.12.*
    • unaffected 6.13 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-21647 badge
[![CVE-2025-21647](https://cveledger.app/badge/CVE-2025-21647.svg)](https://cveledger.app/cve/CVE-2025-21647)

Record last updated .