{
  "cveId": "CVE-2022-48731",
  "url": "https://patchblox.com/security/cve/CVE-2022-48731",
  "summary": "CVE-2022-48731 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-48731, released June 20, 2024. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  mm/kmemleak: avoid scanning potential huge holes...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  mm/kmemleak: avoid scanning potential huge holes  When using devm_request_free_mem_region() and devm_memremap_pages() to add ZONE_DEVICE memory, if requested free mem region\u0027s end pfn were huge(e.g., 0x400000000), the node_end_pfn() will be also huge (see move_pfn_range_to_zone()).  Thus it creates a huge hole between node_start_pfn() and node_end_pfn().  We found on some AMD APUs, amdkfd requested such a free mem region and created a huge hole.  In such a case, following code snippet was just doing busy test_bit() looping on the huge hole.    for (pfn = start_pfn; pfn \u003C end_pfn; pfn\u002B\u002B) { \tstruct page *page = pfn_to_online_page(pfn); \t\tif (!page) \t\t\tcontinue; \t...   }  So we got a soft lockup:    watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [bash:1221]   CPU: 6 PID: 1221 Comm: bash Not tainted 5.15.0-custom #1   RIP: 0010:pfn_to_online_page\u002B0x5/0xd0   Call Trace:     ? kmemleak_scan\u002B0x16a/0x440     kmemleak_write\u002B0x306/0x3a0     ? common_file_perm\u002B0x72/0x170     full_proxy_write\u002B0x5c/0x90     vfs_write\u002B0xb9/0x260     ksys_write\u002B0x67/0xe0     __x64_sys_write\u002B0x1a/0x20     do_syscall_64\u002B0x3b/0xc0     entry_SYSCALL_64_after_hwframe\u002B0x44/0xae  I did some tests with the patch.  (1) amdgpu module unloaded  before the patch:    real    0m0.976s   user    0m0.000s   sys     0m0.968s  after the patch:    real    0m0.981s   user    0m0.000s   sys     0m0.973s  (2) amdgpu module loaded  before the patch:    real    0m35.365s   user    0m0.000s   sys     0m35.354s  after the patch:    real    0m1.049s   user    0m0.000s   sys     0m1.042s",
  "published": "2024-06-20T12:15:11Z",
  "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.00168,
  "epssPercentile": 0.0619,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "5.16.10-1",
      "fix": "DEBIAN-CVE-2022-48731",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-48731",
      "released": "2024-06-20T12:15:11Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "5.16.10-1",
      "fix": "DEBIAN-CVE-2022-48731",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-48731",
      "released": "2024-06-20T12:15:11Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "5.16.10-1",
      "fix": "DEBIAN-CVE-2022-48731",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-48731",
      "released": "2024-06-20T12:15:11Z"
    }
  ],
  "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"
  }
}