Log in Start free

Vulnerability · Published May 2, 2025 · Assigned by Linux

CVE-2023-53094tty: serial: fsl_lpuart: fix race on RX DMA shutdown

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 5% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 95.5% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: tty: serial: fsl_lpuart: fix race on RX DMA shutdown From time to time DMA completion can come in the middle of DMA shutdown: <process ctx>: <IRQ>: lpuart32_shutdown() lpuart_dma_shutdown() del_timer_sync() lpuart_dma_rx_complete() lpuart_copy_rx_to_tty() mod_timer() lpuart_dma_rx_free() When the timer fires a bit later, sport->dma_rx_desc is NULL: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000004 pc : lpuart_copy_rx_to_tty+0xcc/0x5bc lr : lpuart_timer_func+0x1c/0x2c Call trace: lpuart_copy_rx_to_tty lpuart_timer_func call_timer_fn __run_timers.part.0 run_timer_softirq __do_softirq __irq_exit_rcu irq_exit handle_domain_irq gic_handle_irq call_on_irq_stack do_interrupt_handler ... To fix this fold del_timer_sync() into lpuart_dma_rx_free() after dmaengine_terminate_sync() to make sure timer will not be re-started in lpuart_copy_rx_to_tty() <= lpuart_dma_rx_complete().

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.25-1DEBIAN-CVE-2023-53094
Debian:13linux6.1.25-1DEBIAN-CVE-2023-53094
Debian:14linux6.1.25-1DEBIAN-CVE-2023-53094
Ubuntu:22.04:LTSlinux5.15.0-79.86UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-aws5.15.0-1042.47UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-azure5.15.0-1045.52UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1045.52.1UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-gcp5.15.0-1039.47UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-gke5.15.0-1039.44UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1025.30UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-ibm5.15.0-1035.38UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1037.42UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-kvm5.15.0-1039.44UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-79.88UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1030.30UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1016.16UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1002.2UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-oracle5.15.0-1040.46UBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-raspi5.15.0-1035.38UBUNTU-CVE-2023-53094
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-53094
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2023-53094
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1025.29UBUNTU-CVE-2023-53094

Affected products (as reported)

VendorProductVersions
Linux Linux 4a8588a1cf867333187d9ff071e6fbdab587d194 – before 19a98d56dfedafb25652bdb9cd48a4e73ceba7024a8588a1cf867333187d9ff071e6fbdab587d194 – before 90530e7214c8a04dcdde57502d93fa96af288c384a8588a1cf867333187d9ff071e6fbdab587d194 – before 954fc9931f0aabf272b5674cf468affdd88d3a364a8588a1cf867333187d9ff071e6fbdab587d194 – before 2a36b444cace9580380467fd1183bb5e85bcc80a4a8588a1cf867333187d9ff071e6fbdab587d194 – before 1be6f2b15f902c02e055ae0b419ca789200473c95716a781032693d0f812ed06528d98195e9df0280d5cb6e8b4b62d8efd1a470615894276341d6db93.18.9 – before 3.19
Linux Linux 4.0

References