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-72147: dmaengine: dw-edma-pcie: Reject devices without driver data
Date: Sat, 15 Aug 2026 15:03:46 +0900	[thread overview]
Message-ID: <2026081533-CVE-2026-72147-7d3c@gregkh> (raw)

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

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

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

dmaengine: dw-edma-pcie: Reject devices without driver data

dw_edma_pcie_probe() treats the PCI device ID driver_data as the
template for the controller layout and copies it unconditionally. A
device bound dynamically via sysfs can match the driver without that
data, which leads to a NULL pointer dereference.

Reject such matches before enabling the device.

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


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

	Issue introduced in 5.3 with commit 41aaff2a2ac01c5f5415f9de9cd7015ac2b8d569 and fixed in 6.6.148 with commit 2733b5dcb5a4ba4446f7bac954b97e4501dcaa64
	Issue introduced in 5.3 with commit 41aaff2a2ac01c5f5415f9de9cd7015ac2b8d569 and fixed in 6.12.101 with commit a1042599fa8f9e313be176eb1ea1ae199f983419
	Issue introduced in 5.3 with commit 41aaff2a2ac01c5f5415f9de9cd7015ac2b8d569 and fixed in 6.18.42 with commit 043acb00e4edd4b9ffb9dd0e357482dcd9086486
	Issue introduced in 5.3 with commit 41aaff2a2ac01c5f5415f9de9cd7015ac2b8d569 and fixed in 7.1.5 with commit 044f7b3252d4fb2143d4999eec2800c08f1001ed
	Issue introduced in 5.3 with commit 41aaff2a2ac01c5f5415f9de9cd7015ac2b8d569 and fixed in 7.2-rc1 with commit 11d7cfe0c119691b2dafbb699bbca90258c678aa

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-72147
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/dma/dw-edma/dw-edma-pcie.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/2733b5dcb5a4ba4446f7bac954b97e4501dcaa64
	https://git.kernel.org/stable/c/a1042599fa8f9e313be176eb1ea1ae199f983419
	https://git.kernel.org/stable/c/043acb00e4edd4b9ffb9dd0e357482dcd9086486
	https://git.kernel.org/stable/c/044f7b3252d4fb2143d4999eec2800c08f1001ed
	https://git.kernel.org/stable/c/11d7cfe0c119691b2dafbb699bbca90258c678aa

                 reply	other threads:[~2026-08-15  6:13 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=2026081533-CVE-2026-72147-7d3c@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.