CVE-2025-21664dm thin: make get_first_thin use rcu-safe list first function
- 7.8HighCVSS base score
- 0.24%Exploitation in 30 daysEPSS · top 85% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 23 days later
· 23 days later
Published
- 21 months later
· 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected b10ebd34cccae1b431caf1be54919aede2be7cbe – < ec037fe8c0d0f6140e3d8a49c7b29cb5582160b8
- affected b10ebd34cccae1b431caf1be54919aede2be7cbe – < cd30a3960433ec2db94b3689752fa3c5df44d649
- affected b10ebd34cccae1b431caf1be54919aede2be7cbe – < 802666a40c71a23542c43a3f87e3a2d0f4e8fe45
- affected b10ebd34cccae1b431caf1be54919aede2be7cbe – < 12771050b6d059eea096993bf2001da9da9fddff
- affected b10ebd34cccae1b431caf1be54919aede2be7cbe – < 6b305e98de0d225ccebfb225730a9f560d28ecb0
- affected b10ebd34cccae1b431caf1be54919aede2be7cbe – < cbd0d5ecfa390ac29c5380200147d09c381b2ac6
- affected b10ebd34cccae1b431caf1be54919aede2be7cbe – < 80f130bfad1dab93b95683fc39b87235682b8f72
- affected 3.15
- unaffected < 3.15
- unaffected 5.4.290 – ≤ 5.4.*
- unaffected 5.10.234 – ≤ 5.10.*
- unaffected 5.15.177 – ≤ 5.15.*
- unaffected 6.1.125 – ≤ 6.1.*
- unaffected 6.6.72 – ≤ 6.6.*
- unaffected 6.12.10 – ≤ 6.12.*
- unaffected 6.13 – ≤ *
References
References10
- https://git.kernel.org/stable/c/ec037fe8c0d0f6140e3d8a49c7b29cb5582160b8 (opens in a new tab)
- https://git.kernel.org/stable/c/cd30a3960433ec2db94b3689752fa3c5df44d649 (opens in a new tab)
- https://git.kernel.org/stable/c/802666a40c71a23542c43a3f87e3a2d0f4e8fe45 (opens in a new tab)
- https://git.kernel.org/stable/c/12771050b6d059eea096993bf2001da9da9fddff (opens in a new tab)
- https://git.kernel.org/stable/c/6b305e98de0d225ccebfb225730a9f560d28ecb0 (opens in a new tab)
- https://git.kernel.org/stable/c/cbd0d5ecfa390ac29c5380200147d09c381b2ac6 (opens in a new tab)
- https://git.kernel.org/stable/c/80f130bfad1dab93b95683fc39b87235682b8f72 (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html (opens in a new tab)
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-2613 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-21664)Record last updated .