{"id":"CVE-2022-50145","summary":"dmaengine: sf-pdma: Add multithread support for a DMA channel","details":"In the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: sf-pdma: Add multithread support for a DMA channel\n\nWhen we get a DMA channel and try to use it in multiple threads it\nwill cause oops and hanging the system.\n\n% echo 64 \u003e /sys/module/dmatest/parameters/threads_per_chan\n% echo 10000 \u003e /sys/module/dmatest/parameters/iterations\n% echo 1 \u003e /sys/module/dmatest/parameters/run\n[   89.480664] Unable to handle kernel NULL pointer dereference at virtual\n               address 00000000000000a0\n[   89.488725] Oops [#1]\n[   89.494708] CPU: 2 PID: 1008 Comm: dma0chan0-copy0 Not tainted\n               5.17.0-rc5\n[   89.509385] epc : vchan_find_desc+0x32/0x46\n[   89.513553]  ra : sf_pdma_tx_status+0xca/0xd6\n\nThis happens because of data race. Each thread rewrite channels's\ndescriptor as soon as device_prep_dma_memcpy() is called. It leads to the\nsituation when the driver thinks that it uses right descriptor that\nactually is freed or substituted for other one.\n\nWith current fixes a descriptor changes its value only when it has\nbeen used. A new descriptor is acquired from vc-\u003edesc_issued queue that\nis already filled with descriptors that are ready to be sent. Threads\nhave no direct access to DMA channel descriptor. Now it is just possible\nto queue a descriptor for further processing.","modified":"2026-04-03T13:14:40.759955605Z","published":"2025-06-18T11:03:06.312Z","related":["SUSE-SU-2025:02264-1","SUSE-SU-2025:02321-1","SUSE-SU-2025:02322-1","SUSE-SU-2025:02537-1"],"database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50145.json","cna_assigner":"Linux"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/4c7350b1dd8a192af844de32fc99b9e34c876fda"},{"type":"WEB","url":"https://git.kernel.org/stable/c/5ab2782c944e324008ef5d658f2494a9f0e3c5ac"},{"type":"WEB","url":"https://git.kernel.org/stable/c/a93b3f1e11971a91b6441b6d47488f4492cc113f"},{"type":"WEB","url":"https://git.kernel.org/stable/c/b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc"},{"type":"WEB","url":"https://git.kernel.org/stable/c/b9b4992f897be9b0b9e3a3b956cab6b75ccc3f11"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50145.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50145"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"6973886ad58e6b4988813331abb76ae0b364a9c2"},{"fixed":"b9b4992f897be9b0b9e3a3b956cab6b75ccc3f11"},{"fixed":"5ab2782c944e324008ef5d658f2494a9f0e3c5ac"},{"fixed":"4c7350b1dd8a192af844de32fc99b9e34c876fda"},{"fixed":"a93b3f1e11971a91b6441b6d47488f4492cc113f"},{"fixed":"b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50145.json"}}],"schema_version":"1.7.5"}