{
  "cveId": "CVE-2022-50103",
  "url": "https://patchblox.com/security/cve/CVE-2022-50103",
  "summary": "CVE-2022-50103 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-50103, released June 18, 2025. It is not reported as exploited. Patch Radar priority: High.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  sched, cpuset: Fix dl_cpu_busy() panic due to em...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  sched, cpuset: Fix dl_cpu_busy() panic due to empty cs-\u003Ecpus_allowed  With cgroup v2, the cpuset\u0027s cpus_allowed mask can be empty indicating that the cpuset will just use the effective CPUs of its parent. So cpuset_can_attach() can call task_can_attach() with an empty mask. This can lead to cpumask_any_and() returns nr_cpu_ids causing the call to dl_bw_of() to crash due to percpu value access of an out of bound CPU value. For example:  \t[80468.182258] BUG: unable to handle page fault for address: ffffffff8b6648b0 \t  : \t[80468.191019] RIP: 0010:dl_cpu_busy\u002B0x30/0x2b0 \t  : \t[80468.207946] Call Trace: \t[80468.208947]  cpuset_can_attach\u002B0xa0/0x140 \t[80468.209953]  cgroup_migrate_execute\u002B0x8c/0x490 \t[80468.210931]  cgroup_update_dfl_csses\u002B0x254/0x270 \t[80468.211898]  cgroup_subtree_control_write\u002B0x322/0x400 \t[80468.212854]  kernfs_fop_write_iter\u002B0x11c/0x1b0 \t[80468.213777]  new_sync_write\u002B0x11f/0x1b0 \t[80468.214689]  vfs_write\u002B0x1eb/0x280 \t[80468.215592]  ksys_write\u002B0x5f/0xe0 \t[80468.216463]  do_syscall_64\u002B0x5c/0x80 \t[80468.224287]  entry_SYSCALL_64_after_hwframe\u002B0x44/0xae  Fix that by using effective_cpus instead. For cgroup v1, effective_cpus is the same as cpus_allowed. For v2, effective_cpus is the real cpumask to be used by tasks within the cpuset anyway.  Also update task_can_attach()\u0027s 2nd argument name to cs_effective_cpus to reflect the change. In addition, a check is added to task_can_attach() to guard against the possibility that cpumask_any_and() may return a value \u003E= nr_cpu_ids.",
  "published": "2025-06-18T11:15:39Z",
  "severity": "high",
  "cvss": 7.1,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
  "epss": 0.00198,
  "epssPercentile": 0.09664,
  "priority": "High",
  "priorityTier": 3,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.0.2-1",
      "fix": "DEBIAN-CVE-2022-50103",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50103",
      "released": "2025-06-18T11:15:39Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.0.2-1",
      "fix": "DEBIAN-CVE-2022-50103",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50103",
      "released": "2025-06-18T11:15:39Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.0.2-1",
      "fix": "DEBIAN-CVE-2022-50103",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50103",
      "released": "2025-06-18T11:15:39Z"
    }
  ],
  "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"
  }
}