CVE-2022-50145
dmaengine: sf-pdma: Add multithread support for a DMA channel
- Published
- Updated
- Reserved
- Assigned by
- Linux
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 > /sys/module/dmatest/parameters/threads_per_chan % echo 10000 > /sys/module/dmatest/parameters/iterations % echo 1 > /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+0x32/0x46 [ 89.513553] ra : sf_pdma_tx_status+0xca/0xd6 This happens because of data race. Each thread rewrite channels's 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->desc_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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.20% · top 90% of all CVEs (6 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Weakness
Affected products
- affected 6973886ad58e6b4988813331abb76ae0b364a9c2 – < b9b4992f897be9b0b9e3a3b956cab6b75ccc3f11
- affected 6973886ad58e6b4988813331abb76ae0b364a9c2 – < 5ab2782c944e324008ef5d658f2494a9f0e3c5ac
- affected 6973886ad58e6b4988813331abb76ae0b364a9c2 – < 4c7350b1dd8a192af844de32fc99b9e34c876fda
- affected 6973886ad58e6b4988813331abb76ae0b364a9c2 – < a93b3f1e11971a91b6441b6d47488f4492cc113f
- affected 6973886ad58e6b4988813331abb76ae0b364a9c2 – < b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc
- affected 5.5
- unaffected < 5.5
- unaffected 5.10.137 – ≤ 5.10.*
- unaffected 5.15.61 – ≤ 5.15.*
- unaffected 5.18.18 – ≤ 5.18.*
- unaffected 5.19.2 – ≤ 5.19.*
- unaffected 6.0 – ≤ *
References (5)
- https://git.kernel.org/stable/c/b9b4992f897be9b0b9e3a3b956cab6b75ccc3f11 (opens in a new tab)
- https://git.kernel.org/stable/c/5ab2782c944e324008ef5d658f2494a9f0e3c5ac (opens in a new tab)
- https://git.kernel.org/stable/c/4c7350b1dd8a192af844de32fc99b9e34c876fda (opens in a new tab)
- https://git.kernel.org/stable/c/a93b3f1e11971a91b6441b6d47488f4492cc113f (opens in a new tab)
- https://git.kernel.org/stable/c/b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-50145)Record last updated .