CVE-2022-50375
BaseFortify
Publication date: 2025-09-18
Last updated on: 2025-12-11
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.9 (inc) to 5.4.220 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.150 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.75 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 5.19.17 (exc) |
| linux | linux_kernel | From 6.0 (inc) to 6.0.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's serial driver for fsl_lpuart. When the lpuart_dma_shutdown function tears down the DMA (Direct Memory Access), certain flags indicating DMA usage (lpuart_dma_tx_use and lpuart_dma_rx_use) are not reset to false. As a result, another function, lpuart_flush_buffer, may still attempt to access DMA APIs after the DMA has been shut down, which can cause the kernel to abort or panic. This issue can happen, for example, when trying to kill the btattach process, leading to a kernel panic and system instability.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to panic and crash when certain serial device operations are performed, such as terminating the btattach process. Kernel panics lead to system instability, unexpected reboots, and potential loss of data or service availability. This can disrupt normal operation of devices relying on the affected serial driver, impacting system reliability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing kernel panic messages related to dma API access after dma shutdown, especially when using the btattach command on affected devices. For example, running the command `btattach -B /dev/ttyLP2 -S 115200` may trigger the issue and produce kernel error logs indicating synchronous external aborts and stack traces involving fsl_edma3_disable_request and lpuart_flush_buffer. Monitoring dmesg or kernel logs for such errors can help detect the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves applying the patch that disables dma rx/tx use flags in lpuart_dma_shutdown to prevent dma APIs from being accessed after dma is torn down. Until the patch is applied, avoid killing btattach processes or using affected serial devices in a way that triggers dma shutdown to prevent kernel panics. Rebooting the system after encountering the issue is also necessary as indicated by the kernel logs.