All reports
Medium

kernel: configfs: fix a race in configfs_{,un}register_subsystem()

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2022-48931

Probability of exploitation in the next 30 days: 0.17%

FIRST EPSS · 2026-11-21

Description

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.

A flaw was found in the Linux kernel's configfs subsystem, which can result in a denial of service (DoS). A race condition occurs when multiple processes register or unregister configuration items concurrently without adequate locking. A local user could exploit this flaw through simultaneous operations, causing internal data structure corruption that triggers a kernel crash.