From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-68466: mtd: rawnand: lpc32xx_slc: fail DMA transfer on completion timeout
Date: Sat, 15 Aug 2026 15:01:08 +0900 [thread overview]
Message-ID: <2026081504-CVE-2026-68466-7ca5@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mtd: rawnand: lpc32xx_slc: fail DMA transfer on completion timeout
lpc32xx_xmit_dma() waits for the DMA completion callback but ignores
wait_for_completion_timeout(). A timed out DMA transfer is therefore
unmapped and reported as successful to the NAND read/write path.
Return -ETIMEDOUT when the completion wait expires. Terminate the DMA
channel before unmapping the scatterlist so the timed out transfer cannot
continue to access the buffer after the error is returned.
The Linux kernel CVE team has assigned CVE-2026-68466 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.7 with commit 2944a44da09e46b6db2fd2c3334f242b09e05c43 and fixed in 5.10.261 with commit 307e4f4c1d4e1575b3495ecc6e41aa2adc40f491
Issue introduced in 3.7 with commit 2944a44da09e46b6db2fd2c3334f242b09e05c43 and fixed in 5.15.212 with commit c367af37ce7238c96c6071337149099467160746
Issue introduced in 3.7 with commit 2944a44da09e46b6db2fd2c3334f242b09e05c43 and fixed in 6.1.178 with commit 623c4d8e740debb4af28981e3d4e209f9d0260a4
Issue introduced in 3.7 with commit 2944a44da09e46b6db2fd2c3334f242b09e05c43 and fixed in 6.6.145 with commit bd4a622786f92e1f183f7557ab89dd32891cef60
Issue introduced in 3.7 with commit 2944a44da09e46b6db2fd2c3334f242b09e05c43 and fixed in 6.12.97 with commit 8f5c3ee53a5dc1a0f7cfd780485f2c8b5d17f91d
Issue introduced in 3.7 with commit 2944a44da09e46b6db2fd2c3334f242b09e05c43 and fixed in 6.18.40 with commit cf7258f57d18026b8f77c0e80ff1805e9caf7250
Issue introduced in 3.7 with commit 2944a44da09e46b6db2fd2c3334f242b09e05c43 and fixed in 7.1.5 with commit cb2031f8b226efbd13735c07b075e5f14ec11f6d
Issue introduced in 3.7 with commit 2944a44da09e46b6db2fd2c3334f242b09e05c43 and fixed in 7.2-rc4 with commit 17a8ce84964f243c8f89dc7353ac7e8d3137bc74
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-68466
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/mtd/nand/raw/lpc32xx_slc.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/307e4f4c1d4e1575b3495ecc6e41aa2adc40f491
https://git.kernel.org/stable/c/c367af37ce7238c96c6071337149099467160746
https://git.kernel.org/stable/c/623c4d8e740debb4af28981e3d4e209f9d0260a4
https://git.kernel.org/stable/c/bd4a622786f92e1f183f7557ab89dd32891cef60
https://git.kernel.org/stable/c/8f5c3ee53a5dc1a0f7cfd780485f2c8b5d17f91d
https://git.kernel.org/stable/c/cf7258f57d18026b8f77c0e80ff1805e9caf7250
https://git.kernel.org/stable/c/cb2031f8b226efbd13735c07b075e5f14ec11f6d
https://git.kernel.org/stable/c/17a8ce84964f243c8f89dc7353ac7e8d3137bc74
reply other threads:[~2026-08-15 6:05 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=2026081504-CVE-2026-68466-7ca5@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.