CVE-2025-68815
BaseFortify
Publication date: 2026-01-13
Last updated on: 2026-01-19
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.18.0-rc7-00105-g7e9f13163c13-dirty |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's ETS (Earliest TxTime Scheduler) code. When a user changes a DRR (Deficit Round Robin) class to a strict class using the ets qdisc change command, the code fails to remove the DRR class from the active list. As a result, if the class is changed back from strict to DRR, it gets added twice to the active list. This double addition can cause kernel warnings and potential instability, as demonstrated by a kernel splat (crash) triggered by specific tc commands.
How can this vulnerability impact me? :
This vulnerability can lead to kernel instability or crashes when manipulating traffic control classes in the Linux kernel network scheduler. Specifically, it can cause a kernel splat (crash) due to double addition of a class to the active list, which may disrupt network traffic management and potentially affect system reliability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing kernel logs for specific error messages triggered by the vulnerability. You can reproduce the issue using the following commands to check if the system is vulnerable: 1. tc qdisc add dev lo root handle 1: ets bands 2 strict 1 2. tc qdisc add dev lo parent 1:2 handle 20: tbf rate 8bit burst 100b latency 1s 3. tc filter add dev lo parent 1: basic classid 1:2 4. ping -c1 -W0.01 -s 56 127.0.0.1 5. tc qdisc change dev lo root handle 1: ets bands 2 strict 2 6. tc qdisc change dev lo root handle 1: ets bands 2 strict 1 7. ping -c1 -W0.01 -s 56 127.0.0.1 After running these commands, check the kernel logs (e.g., using dmesg) for messages like "list_add double add" or warnings from list_debug.c indicating a double addition to the active list, which confirms the presence of the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation is to update the Linux kernel to a version that includes the fix for this vulnerability. The fix ensures that when changing an ets class to strict, it is properly removed from the active list to prevent double additions. Until the kernel is updated, avoid performing ets qdisc change commands that transform drr classes into strict ones and back, as this triggers the vulnerability.