All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80737: serial: amba-pl011: synchronize DMA teardown
Date: Thu,  3 Sep 2026 10:22:06 +0200	[thread overview]
Message-ID: <2026090359-CVE-2026-80737-823d@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

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

serial: amba-pl011: synchronize DMA teardown

dmaengine_terminate_all() does not wait for a running callback, so the TX
callback can still touch the TX buffer after it is freed. The RX poll
timer reads the RX buffers without the port lock.

Switch to dmaengine_terminate_sync() and delete the RX timer before
freeing the buffers.

The Linux kernel CVE team has assigned CVE-2026-80737 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 2.6.39 with commit ead76f329f777c7301e0a5456a0a1c7a081570bd and fixed in 5.10.267 with commit a38fae9d212e2d3ed5e9ec0ef773f8c0a27fb76e
	Issue introduced in 2.6.39 with commit ead76f329f777c7301e0a5456a0a1c7a081570bd and fixed in 5.15.218 with commit 44bd0ecc3444882d08ecfbc2b2418d2f463d3186
	Issue introduced in 2.6.39 with commit ead76f329f777c7301e0a5456a0a1c7a081570bd and fixed in 6.1.185 with commit f70c9d4fba46463a5b1c7b3ee9ee3b40c90dac03
	Issue introduced in 2.6.39 with commit ead76f329f777c7301e0a5456a0a1c7a081570bd and fixed in 6.6.154 with commit c8c8e895f65fbf71ea6224e27cf8dab91b776e0d
	Issue introduced in 2.6.39 with commit ead76f329f777c7301e0a5456a0a1c7a081570bd and fixed in 6.12.106 with commit 9f6989e477f03a4721d34bb4b09b17accd40283e
	Issue introduced in 2.6.39 with commit ead76f329f777c7301e0a5456a0a1c7a081570bd and fixed in 6.18.45 with commit 5974cb66681eac367107b05924744d7e3b49d41c
	Issue introduced in 2.6.39 with commit ead76f329f777c7301e0a5456a0a1c7a081570bd and fixed in 7.1.9 with commit fdfb46c387241b4eddd36d746793764413285913
	Issue introduced in 2.6.39 with commit ead76f329f777c7301e0a5456a0a1c7a081570bd and fixed in 7.2 with commit 440915499231e9db1c361aa45bb702e8fd3b4a32

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-80737
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/amba-pl011.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/a38fae9d212e2d3ed5e9ec0ef773f8c0a27fb76e
	https://git.kernel.org/stable/c/44bd0ecc3444882d08ecfbc2b2418d2f463d3186
	https://git.kernel.org/stable/c/f70c9d4fba46463a5b1c7b3ee9ee3b40c90dac03
	https://git.kernel.org/stable/c/c8c8e895f65fbf71ea6224e27cf8dab91b776e0d
	https://git.kernel.org/stable/c/9f6989e477f03a4721d34bb4b09b17accd40283e
	https://git.kernel.org/stable/c/5974cb66681eac367107b05924744d7e3b49d41c
	https://git.kernel.org/stable/c/fdfb46c387241b4eddd36d746793764413285913
	https://git.kernel.org/stable/c/440915499231e9db1c361aa45bb702e8fd3b4a32

                 reply	other threads:[~2026-09-03  8:22 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=2026090359-CVE-2026-80737-823d@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.