{
  "cveId": "CVE-2022-48931",
  "url": "https://patchblox.com/security/cve/CVE-2022-48931",
  "summary": "CVE-2022-48931 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-48931, released August 22, 2024. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  configfs: fix a race in configfs_{,un}register_s...",
  "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 --\u003E B --\u003E C --\u003E D A \u003C-- B \u003C-- C \u003C-- 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-\u003Eprev = prev   |                                 |               next-\u003Eprev = prev             prev-\u003Enext = next   |                                 |                 // prev == B                                 |                 prev-\u003Enext = 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.",
  "published": "2024-08-22T04:15:16Z",
  "severity": "medium",
  "cvss": 4.7,
  "cvssVector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00165,
  "epssPercentile": 0.05746,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "5.16.12-1",
      "fix": "DEBIAN-CVE-2022-48931",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-48931",
      "released": "2024-08-22T04:15:16Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "5.16.12-1",
      "fix": "DEBIAN-CVE-2022-48931",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-48931",
      "released": "2024-08-22T04:15:16Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "5.16.12-1",
      "fix": "DEBIAN-CVE-2022-48931",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-48931",
      "released": "2024-08-22T04:15:16Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T06:59:42Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}