CVE-2022-50145
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2022
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
dmaengine: sf-pdma: Add multithread support for a DMA channel
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 6973886ad58e6b4988813331abb76ae0b364a9c2 | affected | git | b9b4992f897be9b0b9e3a3b956cab6b75ccc3f11 | Unavailable | None listed |
| 6973886ad58e6b4988813331abb76ae0b364a9c2 | affected | git | 5ab2782c944e324008ef5d658f2494a9f0e3c5ac | Unavailable | None listed |
| 6973886ad58e6b4988813331abb76ae0b364a9c2 | affected | git | 4c7350b1dd8a192af844de32fc99b9e34c876fda | Unavailable | None listed |
| 6973886ad58e6b4988813331abb76ae0b364a9c2 | affected | git | a93b3f1e11971a91b6441b6d47488f4492cc113f | Unavailable | None listed |
| 6973886ad58e6b4988813331abb76ae0b364a9c2 | affected | git | b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 5.5 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 5.5 | Unavailable | None listed |
| 5.10.137 | unaffected | semver | Unavailable | 5.10.* | None listed |
| 5.15.61 | unaffected | semver | Unavailable | 5.15.* | None listed |
| 5.18.18 | unaffected | semver | Unavailable | 5.18.* | None listed |
| 5.19.2 | unaffected | semver | Unavailable | 5.19.* | None listed |
| 6.0 | unaffected | original_commit_for_fix | Unavailable | * | None listed |