{
  "cveId": "CVE-2024-47736",
  "url": "https://patchblox.com/security/cve/CVE-2024-47736",
  "summary": "CVE-2024-47736 is fixed in linux on 1 platform, first by DEBIAN-CVE-2024-47736, released October 21, 2024. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "erofs: handle overlapped pclusters out of crafted images properly",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  erofs: handle overlapped pclusters out of crafted images properly  syzbot reported a task hang issue due to a deadlock case where it is waiting for the folio lock of a cached folio that will be used for cache I/Os.  After looking into the crafted fuzzed image, I found it\u0027s formed with several overlapped big pclusters as below:   Ext:   logical offset   |  length :     physical offset    |  length    0:        0..   16384 |   16384 :     151552..    167936 |   16384    1:    16384..   32768 |   16384 :     155648..    172032 |   16384    2:    32768..   49152 |   16384 :  537223168.. 537239552 |   16384 ...  Here, extent 0/1 are physically overlapped although it\u0027s entirely _impossible_ for normal filesystem images generated by mkfs.  First, managed folios containing compressed data will be marked as up-to-date and then unlocked immediately (unlike in-place folios) when compressed I/Os are complete.  If physical blocks are not submitted in the incremental order, there should be separate BIOs to avoid dependency issues.  However, the current code mis-arranges z_erofs_fill_bio_vec() and BIO submission which causes unexpected BIO waits.  Second, managed folios will be connected to their own pclusters for efficient inter-queries.  However, this is somewhat hard to implement easily if overlapped big pclusters exist.  Again, these only appear in fuzzed images so let\u0027s simply fall back to temporary short-lived pages for correctness.  Additionally, it justifies that referenced managed folios cannot be truncated for now and reverts part of commit 2080ca1ed3e4 (\u0022erofs: tidy up \u0060struct z_erofs_bvec\u0060\u0022) for simplicity although it shouldn\u0027t be any difference.",
  "published": "2024-10-21T13:15:03Z",
  "severity": "Moderate",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "cwe": "Improper Locking",
  "epss": 0.00182,
  "epssPercentile": 0.07827,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "vendorAdvisory": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-47736",
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.170-1",
      "fix": "DEBIAN-CVE-2024-47736",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2024-47736",
      "released": "2024-10-21T13:15:03Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.11.2-1",
      "fix": "DEBIAN-CVE-2024-47736",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2024-47736",
      "released": "2024-10-21T13:15:03Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.11.2-1",
      "fix": "DEBIAN-CVE-2024-47736",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2024-47736",
      "released": "2024-10-21T13:15:03Z"
    }
  ],
  "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"
  }
}