CVE-2025-21664 Details
Description
In the Linux kernel, the following vulnerability has been resolved: dm thin: make get_first_thin use rcu-safe list first function The documentation in rculist.h explains the absence of list_empty_rcu() and cautions programmers against relying on a list_empty() -> list_first() sequence in RCU safe code. This is because each of these functions performs its own READ_ONCE() of the list head. This can lead to a situation where the list_empty() sees a valid list entry, but the subsequent list_first() sees a different view of list head state after a modification. In the case of dm-thin, this author had a production box crash from a GP fault in the process_deferred_bios path. This function saw a valid list head in get_first_thin() but when it subsequently dereferenced that and turned it into a thin_c, it got the inside of the struct pool, since the list was now empty and referring to itself. The kernel on which this occurred printed both a warning about a refcount_t being saturated, and a UBSAN error for an out-of-bounds cpuid access in the queued spinlock, prior to the fault itself. When the resulting kdump was examined, it was possible to see another thread patiently waiting in thin_dtr's synchronize_rcu. The thin_dtr call managed to pull the thin_c out of the active thins list (and have it be the last entry in the active_thins list) at just the wrong moment which lead to this crash. Fortunately, the fix here is straight forward. Switch get_first_thin() function to use list_first_or_null_rcu() which performs just a single READ_ONCE() and returns NULL if the list is already empty. This was run against the devicemapper test suite's thin-provisioning suites for delete and suspend and no regressions were observed.
A vulnerability in the Linux kernel's device mapper thin provisioning module can lead to a general protection fault. This issue arises from the improper use of RCU (Read-Copy-Update) safe list functions, which can cause a thread to access an invalid list entry. The problem occurs when 'list_empty()' sees a valid entry, but 'list_first()' retrieves a different view of the list head after a modification, leading to a crash. The vulnerability has been addressed by changing the list handling to a safer method that reduces the risk of such errors.
The vulnerability has been fixed in the official Linux kernel repository. Users should upgrade to the latest version.
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.
CISA-ADP
Assessed Oct 15, 2026References 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 |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 3.15.1, < 5.4.290 >= 5.5, < 5.10.234 >= 5.11, < 5.15.177 >= 5.16, < 6.1.125 >= 6.2, < 6.6.72 >= 6.7, < 6.12.10 3.15 - 3.15 rc4 3.15 rc5 3.15 rc6 3.15 rc7 3.15 rc8 6.13 rc1 6.13 rc2 6.13 rc3 6.13 rc4 6.13 rc5 6.13 rc6 |
CPE
Remediation
| |
Change History
13 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 15, 2026 | CVE Modified | kernel.org |
| Oct 15, 2026 | CVE Modified | CISA-ADP |
| Oct 15, 2026 | CVE Modified | CVE |
| Oct 15, 2026 | CVE Modified | siemens-SADP |
| 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 |
| Sep 26, 2025 | Initial Analysis | [email protected] |
| Feb 2, 2025 | CVE Modified | kernel.org |
| Jan 23, 2025 | CVE Modified | kernel.org |
| Jan 21, 2025 | New CVE Received | kernel.org |