{
  "cveId": "CVE-2022-48797",
  "url": "https://patchblox.com/security/cve/CVE-2022-48797",
  "summary": "CVE-2022-48797 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-48797, released July 16, 2024. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  mm: don\u0027t try to NUMA-migrate COW pages that hav...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  mm: don\u0027t try to NUMA-migrate COW pages that have other uses  Oded Gabbay reports that enabling NUMA balancing causes corruption with his Gaudi accelerator test load:   \u0022All the details are in the bug, but the bottom line is that somehow,   this patch causes corruption when the numa balancing feature is   enabled AND we don\u0027t use process affinity AND we use GUP to pin pages   so our accelerator can DMA to/from system memory.    Either disabling numa balancing, using process affinity to bind to   specific numa-node or reverting this patch causes the bug to   disappear\u0022  and Oded bisected the issue to commit 09854ba94c6a (\u0022mm: do_wp_page() simplification\u0022).  Now, the NUMA balancing shouldn\u0027t actually be changing the writability of a page, and as such shouldn\u0027t matter for COW.  But it appears it does.  Suspicious.  However, regardless of that, the condition for enabling NUMA faults in change_pte_range() is nonsensical.  It uses \u0022page_mapcount(page)\u0022 to decide if a COW page should be NUMA-protected or not, and that makes absolutely no sense.  The number of mappings a page has is irrelevant: not only does GUP get a reference to a page as in Oded\u0027s case, but the other mappings migth be paged out and the only reference to them would be in the page count.  Since we should never try to NUMA-balance a page that we can\u0027t move anyway due to other references, just fix the code to use \u0027page_count()\u0027. Oded confirms that that fixes his issue.  Now, this does imply that something in NUMA balancing ends up changing page protections (other than the obvious one of making the page inaccessible to get the NUMA faulting information).  Otherwise the COW simplification wouldn\u0027t matter - since doing the GUP on the page would make sure it\u0027s writable.  The cause of that permission change would be good to figure out too, since it clearly results in spurious COW events - but fixing the nonsensical test that just happened to work before is obviously the CorrectThing(tm) to do regardless.",
  "published": "2024-07-16T12:15:04Z",
  "severity": "medium",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00241,
  "epssPercentile": 0.15374,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "5.16.11-1",
      "fix": "DEBIAN-CVE-2022-48797",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-48797",
      "released": "2024-07-16T12:15:04Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "5.16.11-1",
      "fix": "DEBIAN-CVE-2022-48797",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-48797",
      "released": "2024-07-16T12:15:04Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "5.16.11-1",
      "fix": "DEBIAN-CVE-2022-48797",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-48797",
      "released": "2024-07-16T12:15:04Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T00:53:09Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}