CVE-2026-74655serial: qcom-geni: fix TX DMA buffer flush
- 8.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% 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: fix TX DMA buffer flush When transmit flushing a qcom-geni UART during an ongoing TX DMA, the UART gets stuck infinitely repeating corrupted TX DMA frames. The DMA-mode uart_ops does not provide a flush_buffer callback, so an in-flight transfer can complete after serial core has reset the transmit kfifo, underflowing its length and resubmitting page-sized transfers indefinitely. Add one that stops the transfer and clears tx_remaining and tx_queued. The stop path was also broken: it unmapped the buffer while the serial engine could still read it, and never reset the TX DMA state machine. Cancel the main sequencer command first, then reset the state machine and wait for it before unmapping. Drop the early return so a pending mapping is also cleaned up when the main command is inactive. The bug can be triggered from userspace with a large write immediately followed by TCOFLUSH. A following tcdrain will hang forever. The bug was reproduced and this fix was validated on Arduino Uno Q (QRB2210) using /dev/ttyHS1.
Timeline
ID reserved
By Linux
- 7 days later
· 7 days later
Published
- 5 days later
· 5 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected 2aaa43c7077833301c237684cd7bc9ae5e3dec95 – < 1606abb7ce8c0cfef98c7e556b83c14e5d73c1bf
- affected 2aaa43c7077833301c237684cd7bc9ae5e3dec95 – < 313ae287442e5e8d3f7b53b73f37d384bda072d0
- affected 2aaa43c7077833301c237684cd7bc9ae5e3dec95 – < 1c31e2377f4c1bb110ca7f6e597b2253a7440c37
- affected 2aaa43c7077833301c237684cd7bc9ae5e3dec95 – < b1801c0d40f62778b613334de5840aba10a564d5
- affected 2aaa43c7077833301c237684cd7bc9ae5e3dec95 – < e3c04834ae1ab5e9cfbe8ac54ec734aa4774249d
- affected 6.3
- unaffected < 6.3
- unaffected 6.6.154 – ≤ 6.6.*
- unaffected 6.12.104 – ≤ 6.12.*
- unaffected 6.18.45 – ≤ 6.18.*
- unaffected 7.1.9 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References5
- https://git.kernel.org/stable/c/1606abb7ce8c0cfef98c7e556b83c14e5d73c1bf (opens in a new tab)
- https://git.kernel.org/stable/c/313ae287442e5e8d3f7b53b73f37d384bda072d0 (opens in a new tab)
- https://git.kernel.org/stable/c/1c31e2377f4c1bb110ca7f6e597b2253a7440c37 (opens in a new tab)
- https://git.kernel.org/stable/c/b1801c0d40f62778b613334de5840aba10a564d5 (opens in a new tab)
- https://git.kernel.org/stable/c/e3c04834ae1ab5e9cfbe8ac54ec734aa4774249d (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-64592 (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-74655)Record last updated .