{
  "cveId": "CVE-2022-50145",
  "url": "https://patchblox.com/security/cve/CVE-2022-50145",
  "summary": "CVE-2022-50145 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-50145, 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:  dmaengine: sf-pdma: Add multithread support for...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  dmaengine: sf-pdma: Add multithread support for a DMA channel  When we get a DMA channel and try to use it in multiple threads it will cause oops and hanging the system.  % echo 64 \u003E /sys/module/dmatest/parameters/threads_per_chan % echo 10000 \u003E /sys/module/dmatest/parameters/iterations % echo 1 \u003E /sys/module/dmatest/parameters/run [   89.480664] Unable to handle kernel NULL pointer dereference at virtual                address 00000000000000a0 [   89.488725] Oops [#1] [   89.494708] CPU: 2 PID: 1008 Comm: dma0chan0-copy0 Not tainted                5.17.0-rc5 [   89.509385] epc : vchan_find_desc\u002B0x32/0x46 [   89.513553]  ra : sf_pdma_tx_status\u002B0xca/0xd6  This happens because of data race. Each thread rewrite channels\u0027s descriptor as soon as device_prep_dma_memcpy() is called. It leads to the situation when the driver thinks that it uses right descriptor that actually is freed or substituted for other one.  With current fixes a descriptor changes its value only when it has been used. A new descriptor is acquired from vc-\u003Edesc_issued queue that is already filled with descriptors that are ready to be sent. Threads have no direct access to DMA channel descriptor. Now it is just possible to queue a descriptor for further processing.",
  "published": "2025-06-18T11:15:44Z",
  "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.00204,
  "epssPercentile": 0.10401,
  "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-50145",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50145",
      "released": "2025-06-18T11:15:44Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.0.2-1",
      "fix": "DEBIAN-CVE-2022-50145",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50145",
      "released": "2025-06-18T11:15:44Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.0.2-1",
      "fix": "DEBIAN-CVE-2022-50145",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50145",
      "released": "2025-06-18T11:15:44Z"
    }
  ],
  "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"
  }
}