From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2025-38138: dmaengine: ti: Add NULL check in udma_probe()
Date: Thu, 3 Jul 2025 10:35:55 +0200 [thread overview]
Message-ID: <2025070332-CVE-2025-38138-e28b@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: ti: Add NULL check in udma_probe()
devm_kasprintf() returns NULL when memory allocation fails. Currently,
udma_probe() does not check for this case, which results in a NULL
pointer dereference.
Add NULL check after devm_kasprintf() to prevent this issue.
The Linux kernel CVE team has assigned CVE-2025-38138 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.6 with commit 25dcb5dd7b7ce5587c1df18f584ff78f51a68a94 and fixed in 5.10.239 with commit ec1ea394c40523835bbedd8fc4934b77b461b6fe
Issue introduced in 5.6 with commit 25dcb5dd7b7ce5587c1df18f584ff78f51a68a94 and fixed in 5.15.186 with commit 9f133e04c62246353b8b1f0a679535c65161ebcf
Issue introduced in 5.6 with commit 25dcb5dd7b7ce5587c1df18f584ff78f51a68a94 and fixed in 6.1.142 with commit d61d5ba5bd5b0e39e30b34dcd92946e084bca0d0
Issue introduced in 5.6 with commit 25dcb5dd7b7ce5587c1df18f584ff78f51a68a94 and fixed in 6.6.94 with commit b79e10050d9d1e200541d25751dd5cb8ec58483c
Issue introduced in 5.6 with commit 25dcb5dd7b7ce5587c1df18f584ff78f51a68a94 and fixed in 6.12.34 with commit bc6ddff79835f71310a21645d8fcf08ec473e969
Issue introduced in 5.6 with commit 25dcb5dd7b7ce5587c1df18f584ff78f51a68a94 and fixed in 6.15.3 with commit 643db430f4cbd91dd2b63c49d62d0abb6debc13b
Issue introduced in 5.6 with commit 25dcb5dd7b7ce5587c1df18f584ff78f51a68a94 and fixed in 6.16-rc1 with commit fd447415e74bccd7362f760d4ea727f8e1ebfe91
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-2025-38138
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/ti/k3-udma.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/ec1ea394c40523835bbedd8fc4934b77b461b6fe
https://git.kernel.org/stable/c/9f133e04c62246353b8b1f0a679535c65161ebcf
https://git.kernel.org/stable/c/d61d5ba5bd5b0e39e30b34dcd92946e084bca0d0
https://git.kernel.org/stable/c/b79e10050d9d1e200541d25751dd5cb8ec58483c
https://git.kernel.org/stable/c/bc6ddff79835f71310a21645d8fcf08ec473e969
https://git.kernel.org/stable/c/643db430f4cbd91dd2b63c49d62d0abb6debc13b
https://git.kernel.org/stable/c/fd447415e74bccd7362f760d4ea727f8e1ebfe91
reply other threads:[~2025-07-03 8: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=2025070332-CVE-2025-38138-e28b@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.