Answer in brief
CVE-2022-50145 records a High severity (CVSS 7.8) vulnerability in dmaengine: sf-pdma: Add multithread support for a DMA channel. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6973886ad58e6b4988813331abb76ae0b364a9c2 <b9b4992f897be9b0b9e3a3b956cab6b75ccc3f11 || >=6973886ad58e6b4988813331abb76ae0b364a9c2 <5ab2782c944e324008ef5d658f2494a9f0e3c5ac || >=6973886ad58e6b4988813331abb76ae0b364a9c2 <4c7350b1dd8a192af844de32fc99b9e34c876fda || >=6973886ad58e6b4988813331abb76ae0b364a9c2 <a93b3f1e11971a91b6441b6d47488f4492cc113f || >=6973886ad58e6b4988813331abb76ae0b364a9c2 <b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc | b9b4992f897be9b0b9e3a3b956cab6b75ccc3f11, 5ab2782c944e324008ef5d658f2494a9f0e3c5ac, 4c7350b1dd8a192af844de32fc99b9e34c876fda, a93b3f1e11971a91b6441b6d47488f4492cc113f, b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc |
| Linux/Linuxgeneric | 5.5 | Not reported |
Published upstream
Jun 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-50145 records a High severity (CVSS 7.8) vulnerability in dmaengine: sf-pdma: Add multithread support for a DMA channel. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6973886ad58e6b4988813331abb76ae0b364a9c2 <b9b4992f897be9b0b9e3a3b956cab6b75ccc3f11 || >=6973886ad58e6b4988813331abb76ae0b364a9c2 <5ab2782c944e324008ef5d658f2494a9f0e3c5ac || >=6973886ad58e6b4988813331abb76ae0b364a9c2 <4c7350b1dd8a192af844de32fc99b9e34c876fda || >=6973886ad58e6b4988813331abb76ae0b364a9c2 <a93b3f1e11971a91b6441b6d47488f4492cc113f || >=6973886ad58e6b4988813331abb76ae0b364a9c2 <b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc | b9b4992f897be9b0b9e3a3b956cab6b75ccc3f11, 5ab2782c944e324008ef5d658f2494a9f0e3c5ac, 4c7350b1dd8a192af844de32fc99b9e34c876fda, a93b3f1e11971a91b6441b6d47488f4492cc113f, b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc |
| Linux/Linuxgeneric | 5.5 | Not reported |
Published upstream
Jun 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.