CVE-2022-48931: configfs: fix a race in configfs_{,un}register_subsystem()
In the Linux kernel, the following vulnerability has been resolved:
configfs: fix a race in configfs_{,un}register_subsystem()
When configfs_register_subsystem() or configfs_unregister_subsystem()
is executing link_group() or unlink_group(),
it is possible that two processes add or delete list concurrently.
Some unfortunate interleavings of them can cause kernel panic.
One of cases is:
A --> B --> C --> D
A <-- B <-- C <-- D
delete list_head *B | delete list_head *C
--------------------------------|-----------------------------------
configfs_unregister_subsystem | configfs_unregister_subsystem
unlink_group | unlink_group
unlink_obj | unlink_obj
list_del_init | list_del_init
__list_del_entry | __list_del_entry
__list_del | __list_del
// next == C |
next->prev = prev |
| next->prev = prev
prev->next = next |
| // prev == B
| prev->next = next
Fix this by adding mutex when calling link_group() or unlink_group(),
but parent configfs_subsystem is NULL when config_item is root.
So I create a mutex configfs_subsystem_mutex.
Security readout for executives and security teams
Plain-English summary
CVE-2022-48931 is a Linux kernel configfs race that can crash the kernel during concurrent subsystem registration or unregistration. The business impact is availability: affected systems may panic if the vulnerable path is reachable. Sources do not provide CVSS, exploitation evidence, or a remote attack path.
Executive priority
Treat this as an availability-risk kernel update. It is not presented as remotely exploitable or actively exploited, but a kernel panic can still cause service interruption on exposed or critical Linux hosts.
Technical view
configfs_register_subsystem() and configfs_unregister_subsystem() could call link_group() or unlink_group() concurrently and corrupt list_head state during add/delete operations, leading to kernel panic. The fix adds configfs_subsystem_mutex around those calls because the parent subsystem may be NULL for root config items.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions with configfs code present and reachable. The source lists Linux kernel versions and stable commits but does not define affected distributions, appliances, container images, or required privileges.
Exploitation context
The provided sources describe a race condition and kernel panic scenario, not active exploitation. KEV status is false, and no cited source claims in-the-wild exploitation or a public exploit.
Researcher notes
The core issue is unsynchronized configfs list manipulation during concurrent subsystem registration or unregistration. Evidence supports denial of service via kernel panic only. Missing data includes CVSS, privilege requirements, distribution mappings, and exploitability details.
Mitigation direction
Update affected Linux kernels through vendor or distribution-supported packages.
Verify the kernel includes the relevant upstream stable fix for CVE-2022-48931.
Prioritize systems where kernel panic would interrupt critical services.
Check vendor advisories for distribution-specific fixed kernel versions.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and images.
Compare running kernels against vendor guidance and the listed upstream stable commits.
Review crash logs for kernel panics involving configfs registration or unregistration.
Confirm patched systems boot into the updated kernel after maintenance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-48931 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.