{
  "cveId": "CVE-2022-48892",
  "url": "https://patchblox.com/security/cve/CVE-2022-48892",
  "summary": "CVE-2022-48892 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-48892, released August 21, 2024. It is not reported as exploited. Patch Radar priority: High.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  sched/core: Fix use-after-free bug in dup_user_c...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  sched/core: Fix use-after-free bug in dup_user_cpus_ptr()  Since commit 07ec77a1d4e8 (\u0022sched: Allow task CPU affinity to be restricted on asymmetric systems\u0022), the setting and clearing of user_cpus_ptr are done under pi_lock for arm64 architecture. However, dup_user_cpus_ptr() accesses user_cpus_ptr without any lock protection. Since sched_setaffinity() can be invoked from another process, the process being modified may be undergoing fork() at the same time.  When racing with the clearing of user_cpus_ptr in __set_cpus_allowed_ptr_locked(), it can lead to user-after-free and possibly double-free in arm64 kernel.  Commit 8f9ea86fdf99 (\u0022sched: Always preserve the user requested cpumask\u0022) fixes this problem as user_cpus_ptr, once set, will never be cleared in a task\u0027s lifetime. However, this bug was re-introduced in commit 851a723e45d1 (\u0022sched: Always clear user_cpus_ptr in do_set_cpus_allowed()\u0022) which allows the clearing of user_cpus_ptr in do_set_cpus_allowed(). This time, it will affect all arches.  Fix this bug by always clearing the user_cpus_ptr of the newly cloned/forked task before the copying process starts and check the user_cpus_ptr state of the source task under pi_lock.  Note to stable, this patch won\u0027t be applicable to stable releases. Just copy the new dup_user_cpus_ptr() function over.",
  "published": "2024-08-21T07:15:05Z",
  "severity": "high",
  "cvss": 7.8,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss": 0.00249,
  "epssPercentile": 0.16314,
  "priority": "High",
  "priorityTier": 3,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.7-1",
      "fix": "DEBIAN-CVE-2022-48892",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-48892",
      "released": "2024-08-21T07:15:05Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.1.7-1",
      "fix": "DEBIAN-CVE-2022-48892",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-48892",
      "released": "2024-08-21T07:15:05Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.1.7-1",
      "fix": "DEBIAN-CVE-2022-48892",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-48892",
      "released": "2024-08-21T07:15:05Z"
    }
  ],
  "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"
  }
}