{
  "cveId": "CVE-2022-50193",
  "url": "https://patchblox.com/security/cve/CVE-2022-50193",
  "summary": "CVE-2022-50193 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-50193, released June 18, 2025. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  erofs: wake up all waiters after z_erofs_lzma_he...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  erofs: wake up all waiters after z_erofs_lzma_head ready  When the user mounts the erofs second times, the decompression thread may hung. The problem happens due to a sequence of steps like the following:  1) Task A called z_erofs_load_lzma_config which obtain all of the node    from the z_erofs_lzma_head.  2) At this time, task B called the z_erofs_lzma_decompress and wanted to    get a node. But the z_erofs_lzma_head was empty, the Task B had to    sleep.  3) Task A release nodes and push nodes into the z_erofs_lzma_head. But    task B was still sleeping.  One example report when the hung happens: task:kworker/u3:1 state:D stack:14384 pid: 86 ppid: 2 flags:0x00004000 Workqueue: erofs_unzipd z_erofs_decompressqueue_work Call Trace:  \u003CTASK\u003E  __schedule\u002B0x281/0x760  schedule\u002B0x49/0xb0  z_erofs_lzma_decompress\u002B0x4bc/0x580  ? cpu_core_flags\u002B0x10/0x10  z_erofs_decompress_pcluster\u002B0x49b/0xba0  ? __update_load_avg_se\u002B0x2b0/0x330  ? __update_load_avg_se\u002B0x2b0/0x330  ? update_load_avg\u002B0x5f/0x690  ? update_load_avg\u002B0x5f/0x690  ? set_next_entity\u002B0xbd/0x110  ? _raw_spin_unlock\u002B0xd/0x20  z_erofs_decompress_queue.isra.0\u002B0x2e/0x50  z_erofs_decompressqueue_work\u002B0x30/0x60  process_one_work\u002B0x1d3/0x3a0  worker_thread\u002B0x45/0x3a0  ? process_one_work\u002B0x3a0/0x3a0  kthread\u002B0xe2/0x110  ? kthread_complete_and_exit\u002B0x20/0x20  ret_from_fork\u002B0x22/0x30  \u003C/TASK\u003E",
  "published": "2025-06-18T11:15:49Z",
  "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.00243,
  "epssPercentile": 0.15514,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.0.2-1",
      "fix": "DEBIAN-CVE-2022-50193",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50193",
      "released": "2025-06-18T11:15:49Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.0.2-1",
      "fix": "DEBIAN-CVE-2022-50193",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50193",
      "released": "2025-06-18T11:15:49Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.0.2-1",
      "fix": "DEBIAN-CVE-2022-50193",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50193",
      "released": "2025-06-18T11:15:49Z"
    }
  ],
  "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"
  }
}