IT

Tracker / CVE-2022-48931

CVE-2022-48931

Medium 4.7

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.

Affected products and versions

linux linux_kernel · 2.6.16 → 4.9.304
linux linux_kernel · 4.10 → 4.14.269
linux linux_kernel · 4.15 → 4.19.232
linux linux_kernel · 4.20 → 5.4.182
linux linux_kernel · 5.11 → 5.15.26
linux linux_kernel · 5.16 → 5.16.12
linux linux_kernel · 5.5 → 5.10.103

Analysis

This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.

References