CVE-2026-93123

serial: qcom-geni: do not advance stale DMA completions

State
Published
Severity
Not scored
Published
Sep 17, 2026
Updated
Oct 19, 2026
Reserved
Sep 17, 2026

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

serial: qcom-geni: do not advance stale DMA completions

The qcom GENI serial DMA TX completion path advances the transmit fifo by the number of bytes recorded in port->tx_remaining.

If uart_flush_buffer() runs after the hardware has completed a DMA transfer but before the DMA completion interrupt has been handled, the serial core resets the transmit fifo while port->tx_remaining still describes the old DMA transfer.

A previous fix avoided advancing an empty fifo by checking that the fifo length is at least tx_remaining. That still does not distinguish the old DMA payload from new bytes written after the flush. If userspace writes new data before the stale DMA completion interrupt is handled, the fifo can again contain at least tx_remaining bytes and the stale completion can advance and discard those new bytes.

Mark an in-flight DMA transfer stale when the transmit fifo is flushed. The later completion still unprepares the original DMA mapping using the saved length, but it no longer advances the transmit fifo.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 2aaa43c7077833301c237684cd7bc9ae5e3dec95 to before 231c84fe7ec40e4a06c398c0591d5b8e823d68e1Affected
  • 2aaa43c7077833301c237684cd7bc9ae5e3dec95 to before c02d030747c46da33faf406dd772ef91100efa27Affected
  • 2aaa43c7077833301c237684cd7bc9ae5e3dec95 to before 59faa59c25a0a098fbc86275408d7c8405015702Affected
  • 2aaa43c7077833301c237684cd7bc9ae5e3dec95 to before 7ea38c49e7178960926657863299face6dc0e1b0Affected
LinuxLinux
  • 6.3Affected
  • before 6.3Not affected
  • 6.12.110 through 6.12.*Not affected
  • 6.18.52 through 6.18.*Not affected
  • 7.2.6 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.