CVE-2026-93100fs/resctrl: Prevent use-after-free in rdtgroup_kn_put()
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% 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: fs/resctrl: Prevent use-after-free in rdtgroup_kn_put() A struct rdtgroup is reference counted via rdtgroup::waitcount. Callers that need the structure to remain valid across a sleep (while waiting on acquiring rdtgroup_mutex) take a reference with rdtgroup_kn_get() and release it with rdtgroup_kn_put(). The release path is intended to serve as the fallback freer: if the count drops to zero and the group has already been marked RDT_DELETED, rdtgroup_kn_put() frees the structure. The bulk teardown paths free_all_child_rdtgrp() and rmdir_all_sub() resulting from a resctrl directory remove or resctrl fs unmount act as the primary freer: they hold rdtgroup_mutex and free each rdtgroup whose waitcount is zero, otherwise they set RDT_DELETED and leave the freeing to the last waiter. These two freers race. rdtgroup_kn_put() commits waitcount == 0 with atomic_dec_and_test() outside rdtgroup_mutex, then reads rdtgroup::flags. Between those two operations a concurrent caller of free_all_child_rdtgrp() or rmdir_all_sub() (which holds the mutex) can observe waitcount == 0 via atomic_read(), call rdtgroup_remove(), and kfree() the structure. The subsequent read of rdtgroup::flags in rdtgroup_kn_put() is then a use-after-free, and the structure may even be freed twice if the freed memory happens to satisfy the RDT_DELETED flag check. Replace the bare atomic_dec_and_test() with atomic_dec_and_mutex_lock() so that the decrement-to-zero takes rdtgroup_mutex before the count becomes globally visible. The inspection of rdtgroup::flags then runs under the same mutex held by the bulk freers, making the two paths mutually exclusive. The common case where the count does not reach zero remains lock-free. Defer kernfs_unbreak_active_protection() until after the mutex is dropped since kernfs active protections functionally wrap rdtgroup_mutex. Remove resource group, which in turn drops its kernfs reference, after kernfs protection is restored. [ bp: Split the commit messsages into smaller, easier-parseable paragraphs. ]
Timeline
ID reserved
By Linux
Published
- 43 days later
· 43 days 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
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected b8511ccc75c033f6d54188ea4df7bf1e85778740 – < 906b3044dbf7c38cc411f7cf457c811363161e3b
- affected b8511ccc75c033f6d54188ea4df7bf1e85778740 – < 971b40e3ca1279ca4917889e0195d33b66d071a4
- affected b8511ccc75c033f6d54188ea4df7bf1e85778740 – < 828ff461c136b95d13b8d712c0a7a06a640e313a
- affected b8511ccc75c033f6d54188ea4df7bf1e85778740 – < ae69f936e8ffed553d899ba4c02f8a7461a89e54
- affected b8511ccc75c033f6d54188ea4df7bf1e85778740 – < 4c593c62c1499665baebbb41b70e2c9b7e947b86
- affected b8511ccc75c033f6d54188ea4df7bf1e85778740 – < f5bcf539484d2d604c2f2330e09487ea090b21c7
- affected d20edc0bca5577bab38acb5b190619c922ddebf8
- affected 1b006f8cbde9f3dabdfafe2ff7aa9f831ed5b625
- affected 40300f986e47dbc8f1d02e5080385f5cf9f85f70
- affected b5a4949897ebada8132d54c93208989482503103
- affected 4.14.170 – < 4.15
- affected 4.19.102 – < 4.20
- affected 5.4.18 – < 5.5
- affected 5.5.2 – < 5.6
- affected 5.6
- unaffected < 5.6
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/906b3044dbf7c38cc411f7cf457c811363161e3b (opens in a new tab)
- https://git.kernel.org/stable/c/971b40e3ca1279ca4917889e0195d33b66d071a4 (opens in a new tab)
- https://git.kernel.org/stable/c/828ff461c136b95d13b8d712c0a7a06a640e313a (opens in a new tab)
- https://git.kernel.org/stable/c/ae69f936e8ffed553d899ba4c02f8a7461a89e54 (opens in a new tab)
- https://git.kernel.org/stable/c/4c593c62c1499665baebbb41b70e2c9b7e947b86 (opens in a new tab)
- https://git.kernel.org/stable/c/f5bcf539484d2d604c2f2330e09487ea090b21c7 (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-2026-82208 (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-2026-93100)Record last updated .