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-38108net_sched: red: fix a race in __red_change()

Description

In the Linux kernel, the following vulnerability has been resolved: net_sched: red: fix a race in __red_change() Gerrard Tai reported a race condition in RED, whenever SFQ perturb timer fires at the wrong time. The race is as follows: CPU 0 CPU 1 [1]: lock root [2]: qdisc_tree_flush_backlog() [3]: unlock root | | [5]: lock root | [6]: rehash | [7]: qdisc_tree_reduce_backlog() | [4]: qdisc_put() This can be abused to underflow a parent's qlen. Calling qdisc_purge_queue() instead of qdisc_tree_flush_backlog() should fix the race, because all packets will be purged from the qdisc before releasing the lock.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 16 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-38108, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 0c8d13ac96070000da33f394f45e9c19638483c5 – < 2790c4ec481be45a80948d059cd7c9a06bc37493
    • affected 0c8d13ac96070000da33f394f45e9c19638483c5 – < a1bf6a4e9264a685b0e642994031f9c5aad72414
    • affected 0c8d13ac96070000da33f394f45e9c19638483c5 – < 110a47efcf23438ff8d31dbd9c854fae2a48bf98
    • affected 0c8d13ac96070000da33f394f45e9c19638483c5 – < f569984417a4e12c67366e69bdcb752970de921d
    • affected 0c8d13ac96070000da33f394f45e9c19638483c5 – < 2a71924ca4af59ffc00f0444732b6cd54b153d0e
    • affected 0c8d13ac96070000da33f394f45e9c19638483c5 – < 4b755305b2b0618e857fdadb499365b5f2e478d1
    • affected 0c8d13ac96070000da33f394f45e9c19638483c5 – < 444ad445df5496a785705019268a8a84b84484bb
    • affected 0c8d13ac96070000da33f394f45e9c19638483c5 – < 85a3e0ede38450ea3053b8c45d28cf55208409b8
  • Linux · Linux

    • affected 5.0
    • unaffected < 5.0
    • unaffected 5.4.295 – ≤ 5.4.*
    • unaffected 5.10.239 – ≤ 5.10.*
    • unaffected 5.15.186 – ≤ 5.15.*
    • unaffected 6.1.142 – ≤ 6.1.*
    • unaffected 6.6.94 – ≤ 6.6.*
    • unaffected 6.12.34 – ≤ 6.12.*
    • unaffected 6.15.3 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .