From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74655: serial: qcom-geni: fix TX DMA buffer flush
Date: Sat, 22 Aug 2026 17:32:19 +0200 [thread overview]
Message-ID: <2026082226-CVE-2026-74655-093d@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-74655 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.3 with commit 2aaa43c7077833301c237684cd7bc9ae5e3dec95 and fixed in 6.12.104 with commit 313ae287442e5e8d3f7b53b73f37d384bda072d0
Issue introduced in 6.3 with commit 2aaa43c7077833301c237684cd7bc9ae5e3dec95 and fixed in 6.18.45 with commit 1c31e2377f4c1bb110ca7f6e597b2253a7440c37
Issue introduced in 6.3 with commit 2aaa43c7077833301c237684cd7bc9ae5e3dec95 and fixed in 7.1.9 with commit b1801c0d40f62778b613334de5840aba10a564d5
Issue introduced in 6.3 with commit 2aaa43c7077833301c237684cd7bc9ae5e3dec95 and fixed in 7.2 with commit e3c04834ae1ab5e9cfbe8ac54ec734aa4774249d
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-74655
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/tty/serial/qcom_geni_serial.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/313ae287442e5e8d3f7b53b73f37d384bda072d0
https://git.kernel.org/stable/c/1c31e2377f4c1bb110ca7f6e597b2253a7440c37
https://git.kernel.org/stable/c/b1801c0d40f62778b613334de5840aba10a564d5
https://git.kernel.org/stable/c/e3c04834ae1ab5e9cfbe8ac54ec734aa4774249d
reply other threads:[~2026-08-22 15:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026082226-CVE-2026-74655-093d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.