CVE-2025-38108
BaseFortify
Publication date: 2025-07-03
Last updated on: 2025-12-16
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.0 (inc) to 5.4.295 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.239 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.186 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.142 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.94 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.34 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.15.3 (exc) |
| linux | linux_kernel | 6.16 |
| debian | debian_linux | 11.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a race condition in the Linux kernel's RED (Random Early Detection) network scheduler. It occurs when the SFQ perturb timer fires at an incorrect time, causing concurrent operations on the queue discipline (qdisc) to interfere with each other. Specifically, one CPU locks and flushes the backlog while another CPU locks and rehashes the queue, leading to a race that can cause the parent's queue length to underflow. The issue is fixed by changing the function called to purge all packets before releasing the lock, preventing the race.
How can this vulnerability impact me? :
This vulnerability can lead to an underflow of a parent's queue length in the network scheduler, which may cause unexpected behavior in network traffic management. This could potentially disrupt network performance or stability on affected Linux systems.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the race condition in the RED qdisc (__red_change) has been fixed. The fix involves replacing qdisc_tree_flush_backlog() with qdisc_purge_queue() to prevent the race condition and potential queue length underflow. Applying the latest kernel patches or updates from your Linux distribution that address this issue is recommended.