-

CVE-2026-93100

fs/resctrl: Prevent use-after-free in rdtgroup_kn_put()

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. ]
Daten sind bereitgestellt durch das CVE Programm von einer CVE Numbering Authority (CNA) (Unstrukturiert).
HerstellerLinux
≫
Produkt Linux
Default Statusunaffected
Version b8511ccc75c033f6d54188ea4df7bf1e85778740
Version < ae69f936e8ffed553d899ba4c02f8a7461a89e54
Status affected
Version b8511ccc75c033f6d54188ea4df7bf1e85778740
Version < 4c593c62c1499665baebbb41b70e2c9b7e947b86
Status affected
Version b8511ccc75c033f6d54188ea4df7bf1e85778740
Version < f5bcf539484d2d604c2f2330e09487ea090b21c7
Status affected
Version d20edc0bca5577bab38acb5b190619c922ddebf8
Status affected
Version 1b006f8cbde9f3dabdfafe2ff7aa9f831ed5b625
Status affected
Version 40300f986e47dbc8f1d02e5080385f5cf9f85f70
Status affected
Version b5a4949897ebada8132d54c93208989482503103
Status affected
Version 4.14.170
Version < 4.15
Status affected
Version 4.19.102
Version < 4.20
Status affected
Version 5.4.18
Version < 5.5
Status affected
Version 5.5.2
Version < 5.6
Status affected
HerstellerLinux
≫
Produkt Linux
Default Statusaffected
Version 5.6
Status affected
Version 0
Version < 5.6
Status unaffected
Version <= 6.18.*
Version 6.18.52
Status unaffected
Version <= 7.2.*
Version 7.2.6
Status unaffected
Version <= *
Version 7.3-rc1
Status unaffected
VulnDex Vulnerability Enrichment
Diese Information steht angemeldeten Benutzern zur Verfügung. Login Login
Zu dieser CVE wurde keine Warnung gefunden.
EPSS Metriken
Typ Quelle Score Percentile
EPSS FIRST.org 0.17% 0.063
CVSS Metriken
Quelle Base Score Exploit Score Impact Score Vector String
Es wurden noch keine Informationen zu CWE veröffentlicht.
https://git.kernel.org/stable/c/ae69f936e8ffed553d899ba4c02f8a7461a89e54
https://git.kernel.org/stable/c/4c593c62c1499665baebbb41b70e2c9b7e947b86
https://git.kernel.org/stable/c/f5bcf539484d2d604c2f2330e09487ea090b21c7