CVE-2026-93123serial: qcom-geni: do not advance stale DMA completions
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 32 days later
· 32 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 2aaa43c7077833301c237684cd7bc9ae5e3dec95 – < 231c84fe7ec40e4a06c398c0591d5b8e823d68e1
- affected 2aaa43c7077833301c237684cd7bc9ae5e3dec95 – < c02d030747c46da33faf406dd772ef91100efa27
- affected 2aaa43c7077833301c237684cd7bc9ae5e3dec95 – < 59faa59c25a0a098fbc86275408d7c8405015702
- affected 2aaa43c7077833301c237684cd7bc9ae5e3dec95 – < 7ea38c49e7178960926657863299face6dc0e1b0
- affected 6.3
- unaffected < 6.3
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/231c84fe7ec40e4a06c398c0591d5b8e823d68e1 (opens in a new tab)
- https://git.kernel.org/stable/c/c02d030747c46da33faf406dd772ef91100efa27 (opens in a new tab)
- https://git.kernel.org/stable/c/59faa59c25a0a098fbc86275408d7c8405015702 (opens in a new tab)
- https://git.kernel.org/stable/c/7ea38c49e7178960926657863299face6dc0e1b0 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-82231 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93123)Record last updated .