Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-48931

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

Medium4.7EPSS 0.17%
Published
Updated
Reserved
Assigned by
Linux

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.

Scores

CVSS scores of CVE-2022-48931, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.7.

Weakness

Affected products

  • Linux · Linux

    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < 40805099af11f68c5ca7dbcfacf455da8f99f622
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < d1654de19d42f513b6cfe955cc77e7f427e05a77
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < a37024f7757c25550accdebf49e497ad6ae239fe
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < b7e2b91fcb5c78c414e33dc8d50642e307ca0c5a
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < a7ab53d3c27dfe83bb594456b9f38a37796ec39b
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < e7a66dd2687758718eddd79b542a95cf3aa488cc
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < 3aadfd46858b1f64d4d6a0654b863e21aabff975
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < 84ec758fb2daa236026506868c8796b0500c047d
  • Linux · Linux

    • affected 2.6.16
    • unaffected < 2.6.16
    • unaffected 4.9.304 – ≤ 4.9.*
    • unaffected 4.14.269 – ≤ 4.14.*
    • unaffected 4.19.232 – ≤ 4.19.*
    • unaffected 5.4.182 – ≤ 5.4.*
    • unaffected 5.10.103 – ≤ 5.10.*
    • unaffected 5.15.26 – ≤ 5.15.*
    • unaffected 5.16.12 – ≤ 5.16.*
    • unaffected 5.17 – ≤ *

References (8)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-48931 badge
[![CVE-2022-48931](https://trackcve.app/badge/CVE-2022-48931.svg)](https://trackcve.app/cve/CVE-2022-48931)

Record last updated .