From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2025-38368: misc: tps6594-pfsm: Add NULL pointer check in tps6594_pfsm_probe()
Date: Fri, 25 Jul 2025 14:48:09 +0200 [thread overview]
Message-ID: <2025072559-CVE-2025-38368-e561@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
misc: tps6594-pfsm: Add NULL pointer check in tps6594_pfsm_probe()
The returned value, pfsm->miscdev.name, from devm_kasprintf()
could be NULL.
A pointer check is added to prevent potential NULL pointer dereference.
This is similar to the fix in commit 3027e7b15b02
("ice: Fix some null pointer dereference issues in ice_ptp.c").
This issue is found by our static analysis tool.
The Linux kernel CVE team has assigned CVE-2025-38368 to this issue.
Affected and fixed versions
===========================
Fixed in 6.6.96 with commit a8d1b4f219e8833130927f19d1c8bfbf49215ce4
Fixed in 6.12.36 with commit a10c8bff454b11ef553d9df19ee722d2df34cd0e
Fixed in 6.15.5 with commit d27ee5c59881a64ea92e363502742cb4f38b7460
Fixed in 6.16-rc1 with commit a99b598d836c9c6411110c70a2da134c78d96e67
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-38368
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/misc/tps6594-pfsm.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/a8d1b4f219e8833130927f19d1c8bfbf49215ce4
https://git.kernel.org/stable/c/a10c8bff454b11ef553d9df19ee722d2df34cd0e
https://git.kernel.org/stable/c/d27ee5c59881a64ea92e363502742cb4f38b7460
https://git.kernel.org/stable/c/a99b598d836c9c6411110c70a2da134c78d96e67
reply other threads:[~2025-07-25 12:48 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=2025072559-CVE-2025-38368-e561@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.