CVE-2022-50103 (GCVE-0-2022-50103)
Vulnerability from cvelistv5
Published
2025-06-18 11:02
Modified
2025-06-18 11:02
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: sched, cpuset: Fix dl_cpu_busy() panic due to empty cs->cpus_allowed With cgroup v2, the cpuset's 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: [80468.182258] BUG: unable to handle page fault for address: ffffffff8b6648b0 : [80468.191019] RIP: 0010:dl_cpu_busy+0x30/0x2b0 : [80468.207946] Call Trace: [80468.208947] cpuset_can_attach+0xa0/0x140 [80468.209953] cgroup_migrate_execute+0x8c/0x490 [80468.210931] cgroup_update_dfl_csses+0x254/0x270 [80468.211898] cgroup_subtree_control_write+0x322/0x400 [80468.212854] kernfs_fop_write_iter+0x11c/0x1b0 [80468.213777] new_sync_write+0x11f/0x1b0 [80468.214689] vfs_write+0x1eb/0x280 [80468.215592] ksys_write+0x5f/0xe0 [80468.216463] do_syscall_64+0x5c/0x80 [80468.224287] entry_SYSCALL_64_after_hwframe+0x44/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()'s 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 >= nr_cpu_ids.
References
Impacted products
Vendor Product Version
Linux Linux Version: 7f51412a415d87ea8598d14722fb31e4f5701257
Version: 7f51412a415d87ea8598d14722fb31e4f5701257
Version: 7f51412a415d87ea8598d14722fb31e4f5701257
Version: 7f51412a415d87ea8598d14722fb31e4f5701257
Version: 7f51412a415d87ea8598d14722fb31e4f5701257
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "include/linux/sched.h",
            "kernel/cgroup/cpuset.c",
            "kernel/sched/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "336626564b58071b8980a4e6a31a8f5d92705d9b",
              "status": "affected",
              "version": "7f51412a415d87ea8598d14722fb31e4f5701257",
              "versionType": "git"
            },
            {
              "lessThan": "147f66d22f58712dce7ccdd6a1f6cb3ee8042df4",
              "status": "affected",
              "version": "7f51412a415d87ea8598d14722fb31e4f5701257",
              "versionType": "git"
            },
            {
              "lessThan": "357f3f0e522a6ce1ce4a571cb780d9861d53bec7",
              "status": "affected",
              "version": "7f51412a415d87ea8598d14722fb31e4f5701257",
              "versionType": "git"
            },
            {
              "lessThan": "f56607b44c9896e51678a7e8cdd3a5479f4b4548",
              "status": "affected",
              "version": "7f51412a415d87ea8598d14722fb31e4f5701257",
              "versionType": "git"
            },
            {
              "lessThan": "b6e8d40d43ae4dec00c8fea2593eeea3114b8f44",
              "status": "affected",
              "version": "7f51412a415d87ea8598d14722fb31e4f5701257",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "include/linux/sched.h",
            "kernel/cgroup/cpuset.c",
            "kernel/sched/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "3.19"
            },
            {
              "lessThan": "3.19",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.10.*",
              "status": "unaffected",
              "version": "5.10.137",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.61",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.18.*",
              "status": "unaffected",
              "version": "5.18.18",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.19.*",
              "status": "unaffected",
              "version": "5.19.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.0",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.10.137",
                  "versionStartIncluding": "3.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.61",
                  "versionStartIncluding": "3.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.18.18",
                  "versionStartIncluding": "3.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.19.2",
                  "versionStartIncluding": "3.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.0",
                  "versionStartIncluding": "3.19",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsched, cpuset: Fix dl_cpu_busy() panic due to empty cs-\u003ecpus_allowed\n\nWith cgroup v2, the cpuset\u0027s cpus_allowed mask can be empty indicating\nthat the cpuset will just use the effective CPUs of its parent. So\ncpuset_can_attach() can call task_can_attach() with an empty mask.\nThis can lead to cpumask_any_and() returns nr_cpu_ids causing the call\nto dl_bw_of() to crash due to percpu value access of an out of bound\nCPU value. For example:\n\n\t[80468.182258] BUG: unable to handle page fault for address: ffffffff8b6648b0\n\t  :\n\t[80468.191019] RIP: 0010:dl_cpu_busy+0x30/0x2b0\n\t  :\n\t[80468.207946] Call Trace:\n\t[80468.208947]  cpuset_can_attach+0xa0/0x140\n\t[80468.209953]  cgroup_migrate_execute+0x8c/0x490\n\t[80468.210931]  cgroup_update_dfl_csses+0x254/0x270\n\t[80468.211898]  cgroup_subtree_control_write+0x322/0x400\n\t[80468.212854]  kernfs_fop_write_iter+0x11c/0x1b0\n\t[80468.213777]  new_sync_write+0x11f/0x1b0\n\t[80468.214689]  vfs_write+0x1eb/0x280\n\t[80468.215592]  ksys_write+0x5f/0xe0\n\t[80468.216463]  do_syscall_64+0x5c/0x80\n\t[80468.224287]  entry_SYSCALL_64_after_hwframe+0x44/0xae\n\nFix that by using effective_cpus instead. For cgroup v1, effective_cpus\nis the same as cpus_allowed. For v2, effective_cpus is the real cpumask\nto be used by tasks within the cpuset anyway.\n\nAlso update task_can_attach()\u0027s 2nd argument name to cs_effective_cpus to\nreflect the change. In addition, a check is added to task_can_attach()\nto guard against the possibility that cpumask_any_and() may return a\nvalue \u003e= nr_cpu_ids."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-06-18T11:02:38.840Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/336626564b58071b8980a4e6a31a8f5d92705d9b"
        },
        {
          "url": "https://git.kernel.org/stable/c/147f66d22f58712dce7ccdd6a1f6cb3ee8042df4"
        },
        {
          "url": "https://git.kernel.org/stable/c/357f3f0e522a6ce1ce4a571cb780d9861d53bec7"
        },
        {
          "url": "https://git.kernel.org/stable/c/f56607b44c9896e51678a7e8cdd3a5479f4b4548"
        },
        {
          "url": "https://git.kernel.org/stable/c/b6e8d40d43ae4dec00c8fea2593eeea3114b8f44"
        }
      ],
      "title": "sched, cpuset: Fix dl_cpu_busy() panic due to empty cs-\u003ecpus_allowed",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2022-50103",
    "datePublished": "2025-06-18T11:02:38.840Z",
    "dateReserved": "2025-06-18T10:57:27.413Z",
    "dateUpdated": "2025-06-18T11:02:38.840Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2022-50103\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-06-18T11:15:39.670\",\"lastModified\":\"2025-06-18T13:47:40.833\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nsched, cpuset: Fix dl_cpu_busy() panic due to empty cs-\u003ecpus_allowed\\n\\nWith cgroup v2, the cpuset\u0027s cpus_allowed mask can be empty indicating\\nthat the cpuset will just use the effective CPUs of its parent. So\\ncpuset_can_attach() can call task_can_attach() with an empty mask.\\nThis can lead to cpumask_any_and() returns nr_cpu_ids causing the call\\nto dl_bw_of() to crash due to percpu value access of an out of bound\\nCPU value. For example:\\n\\n\\t[80468.182258] BUG: unable to handle page fault for address: ffffffff8b6648b0\\n\\t  :\\n\\t[80468.191019] RIP: 0010:dl_cpu_busy+0x30/0x2b0\\n\\t  :\\n\\t[80468.207946] Call Trace:\\n\\t[80468.208947]  cpuset_can_attach+0xa0/0x140\\n\\t[80468.209953]  cgroup_migrate_execute+0x8c/0x490\\n\\t[80468.210931]  cgroup_update_dfl_csses+0x254/0x270\\n\\t[80468.211898]  cgroup_subtree_control_write+0x322/0x400\\n\\t[80468.212854]  kernfs_fop_write_iter+0x11c/0x1b0\\n\\t[80468.213777]  new_sync_write+0x11f/0x1b0\\n\\t[80468.214689]  vfs_write+0x1eb/0x280\\n\\t[80468.215592]  ksys_write+0x5f/0xe0\\n\\t[80468.216463]  do_syscall_64+0x5c/0x80\\n\\t[80468.224287]  entry_SYSCALL_64_after_hwframe+0x44/0xae\\n\\nFix that by using effective_cpus instead. For cgroup v1, effective_cpus\\nis the same as cpus_allowed. For v2, effective_cpus is the real cpumask\\nto be used by tasks within the cpuset anyway.\\n\\nAlso update task_can_attach()\u0027s 2nd argument name to cs_effective_cpus to\\nreflect the change. In addition, a check is added to task_can_attach()\\nto guard against the possibility that cpumask_any_and() may return a\\nvalue \u003e= nr_cpu_ids.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: sched, cpuset: Se solucion\u00f3 el p\u00e1nico de dl_cpu_busy() debido a un valor de cs-\u0026gt;cpus_allowed vac\u00edo. Con cgroup v2, la m\u00e1scara cpus_allowed de cpuset puede estar vac\u00eda, lo que indica que solo usar\u00e1 las CPU efectivas de su padre. Por lo tanto, cpuset_can_attach() puede llamar a task_can_attach() con una m\u00e1scara vac\u00eda. Esto puede provocar que cpumask_any_and() devuelva nr_cpu_ids, lo que provoca el bloqueo de la llamada a dl_bw_of() debido al acceso a un valor de CPU fuera de los l\u00edmites. Por ejemplo: [80468.182258] ERROR: no se puede manejar el error de p\u00e1gina para la direcci\u00f3n: ffffffff8b6648b0 : [80468.191019] RIP: 0010:dl_cpu_busy+0x30/0x2b0 : [80468.207946] Rastreo de llamadas: [80468.208947] cpuset_can_attach+0xa0/0x140 [80468.209953] cgroup_migrate_execute+0x8c/0x490 [80468.210931] cgroup_update_dfl_csses+0x254/0x270 [80468.211898] Solucione esto utilizando effective_cpus en su lugar. Para cgroup v1, effective_cpus es igual que cpus_allowed. Para v2, effective_cpus es la m\u00e1scara de CPU real que usar\u00e1n las tareas dentro del conjunto de CPU. Actualice tambi\u00e9n el segundo argumento de task_can_attach() a cs_effective_cpus para reflejar el cambio. Adem\u00e1s, se ha a\u00f1adido una comprobaci\u00f3n a task_can_attach() para evitar que cpumask_any_and() devuelva un valor mayor que nr_cpu_ids.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/147f66d22f58712dce7ccdd6a1f6cb3ee8042df4\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/336626564b58071b8980a4e6a31a8f5d92705d9b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/357f3f0e522a6ce1ce4a571cb780d9861d53bec7\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/b6e8d40d43ae4dec00c8fea2593eeea3114b8f44\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/f56607b44c9896e51678a7e8cdd3a5479f4b4548\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.