{
  "cveId": "CVE-2024-53054",
  "url": "https://patchblox.com/security/cve/CVE-2024-53054",
  "summary": "CVE-2024-53054 is fixed in linux on 1 platform, first by CVE-2024-53054, released November 19, 2024. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:\n\ncgroup/bpf: use a dedicated workqueue for cgroup...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\ncgroup/bpf: use a dedicated workqueue for cgroup bpf destruction\n\nA hung_task problem shown below was found:\n\nINFO: task kworker/0:0:8 blocked for more than 327 seconds.\n\u0022echo 0 \u003E /proc/sys/kernel/hung_task_timeout_secs\u0022 disables this message.\nWorkqueue: events cgroup_bpf_release\nCall Trace:\n \u003CTASK\u003E\n __schedule\u002B0x5a2/0x2050\n ? find_held_lock\u002B0x33/0x100\n ? wq_worker_sleeping\u002B0x9e/0xe0\n schedule\u002B0x9f/0x180\n schedule_preempt_disabled\u002B0x25/0x50\n __mutex_lock\u002B0x512/0x740\n ? cgroup_bpf_release\u002B0x1e/0x4d0\n ? cgroup_bpf_release\u002B0xcf/0x4d0\n ? process_scheduled_works\u002B0x161/0x8a0\n ? cgroup_bpf_release\u002B0x1e/0x4d0\n ? mutex_lock_nested\u002B0x2b/0x40\n ? __pfx_delay_tsc\u002B0x10/0x10\n mutex_lock_nested\u002B0x2b/0x40\n cgroup_bpf_release\u002B0xcf/0x4d0\n ? process_scheduled_works\u002B0x161/0x8a0\n ? trace_event_raw_event_workqueue_execute_start\u002B0x64/0xd0\n ? process_scheduled_works\u002B0x161/0x8a0\n process_scheduled_works\u002B0x23a/0x8a0\n worker_thread\u002B0x231/0x5b0\n ? __pfx_worker_thread\u002B0x10/0x10\n kthread\u002B0x14d/0x1c0\n ? __pfx_kthread\u002B0x10/0x10\n ret_from_fork\u002B0x59/0x70\n ? __pfx_kthread\u002B0x10/0x10\n ret_from_fork_asm\u002B0x1b/0x30\n \u003C/TASK\u003E\n\nThis issue can be reproduced by the following pressuse test:\n1. A large number of cpuset cgroups are deleted.\n2. Set cpu on and off repeatly.\n3. Set watchdog_thresh repeatly.\nThe scripts can be obtained at LINK mentioned above the signature.\n\nThe reason for this issue is cgroup_mutex and cpu_hotplug_lock are\nacquired in different tasks, which may lead to deadlock.\nIt can lead to a deadlock through the following steps:\n1. A large number of cpusets are deleted asynchronously, which puts a\n   large number of cgroup_bpf_release works into system_wq. The max_active\n   of system_wq is WQ_DFL_ACTIVE(256). Consequently, all active works are\n   cgroup_bpf_release works, and many cgroup_bpf_release works will be put\n   into inactive queue. As illustrated in the diagram, there are 256 (in\n   the acvtive queue) \u002B n (in the inactive queue) works.\n2. Setting watchdog_thresh will hold cpu_hotplug_lock.read and put\n   smp_call_on_cpu work into system_wq. However step 1 has already filled\n   system_wq, \u0027sscs.work\u0027 is put into inactive queue. \u0027sscs.work\u0027 has\n   to wait until the works that were put into the inacvtive queue earlier\n   have executed (n cgroup_bpf_release), so it will be blocked for a while.\n3. Cpu offline requires cpu_hotplug_lock.write, which is blocked by step 2.\n4. Cpusets that were deleted at step 1 put cgroup_release works into\n   cgroup_destroy_wq. They are competing to get cgroup_mutex all the time.\n   When cgroup_metux is acqured by work at css_killed_work_fn, it will\n   call cpuset_css_offline, which needs to acqure cpu_hotplug_lock.read.\n   However, cpuset_css_offline will be blocked for step 3.\n5. At this moment, there are 256 works in active queue that are\n   cgroup_bpf_release, they are attempting to acquire cgroup_mutex, and as\n   a result, all of them are blocked. Consequently, sscs.work can not be\n   executed. Ultimately, this situation leads to four processes being\n   blocked, forming a deadlock.\n\nsystem_wq(step1)\t\tWatchDog(step2)\t\t\tcpu offline(step3)\tcgroup_destroy_wq(step4)\n...\n2000\u002B cgroups deleted asyn\n256 actives \u002B n inactives\n\t\t\t\t__lockup_detector_reconfigure\n\t\t\t\tP(cpu_hotplug_lock.read)\n\t\t\t\tput sscs.work into system_wq\n256 \u002B n \u002B 1(sscs.work)\nsscs.work wait to be executed\n\t\t\t\twarting sscs.work finish\n\t\t\t\t\t\t\t\tpercpu_down_write\n\t\t\t\t\t\t\t\tP(cpu_hotplug_lock.write)\n\t\t\t\t\t\t\t\t...blocking...\n\t\t\t\t\t\t\t\t\t\t\tcss_killed_work_fn\n\t\t\t\t\t\t\t\t\t\t\tP(cgroup_mutex)\n\t\t\t\t\t\t\t\t\t\t\tcpuset_css_offline\n\t\t\t\t\t\t\t\t\t\t\tP(cpu_hotplug_lock.read)\n\t\t\t\t\t\t\t\t\t\t\t...blocking...\n256 cgroup_bpf_release\nmutex_lock(\u0026cgroup_mutex);\n..blocking...\n\nTo fix the problem, place cgroup_bpf_release works on a dedicated\nworkqueue which can break the loop and solve the problem. System wqs are\nfor misc things which shouldn\u0027t create a large number of concurrent work\nitems. If something is going to generate \u003E\n---truncated---",
  "published": "2024-11-19T18:15:25Z",
  "severity": "",
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.119-1",
      "fix": "CVE-2024-53054",
      "url": "https://patchblox.com/security/fix/linux/cve-2024-53054",
      "released": "2024-11-19T18:15:25Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.11.7-1",
      "fix": "CVE-2024-53054",
      "url": "https://patchblox.com/security/fix/linux/cve-2024-53054",
      "released": "2024-11-19T18:15:25Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-10T01:44:33Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}