linux-cve-announce - CVE-2025-38210: configfs-tsm-report: Fix NULL dereference of tsm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025070421-CVE-2025-38210-3804@gregkh>
Date: Fri,  4 Jul 2025 15:37:39 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38210: configfs-tsm-report: Fix NULL dereference of tsm_ops

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

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

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

configfs-tsm-report: Fix NULL dereference of tsm_ops

Unlike sysfs, the lifetime of configfs objects is controlled by
userspace. There is no mechanism for the kernel to find and delete all
created config-items. Instead, the configfs-tsm-report mechanism has an
expectation that tsm_unregister() can happen at any time and cause
established config-item access to start failing.

That expectation is not fully satisfied. While tsm_report_read(),
tsm_report_{is,is_bin}_visible(), and tsm_report_make_item() safely fail
if tsm_ops have been unregistered, tsm_report_privlevel_store()
tsm_report_provider_show() fail to check for ops registration. Add the
missing checks for tsm_ops having been removed.

Now, in supporting the ability for tsm_unregister() to always succeed,
it leaves the problem of what to do with lingering config-items. The
expectation is that the admin that arranges for the ->remove() (unbind)
of the ${tsm_arch}-guest driver is also responsible for deletion of all
open config-items. Until that deletion happens, ->probe() (reload /
bind) of the ${tsm_arch}-guest driver fails.

This allows for emergency shutdown / revocation of attestation
interfaces, and requires coordinated restart.

The Linux kernel CVE team has assigned CVE-2025-38210 to this issue.

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

	Issue introduced in 6.7 with commit 70e6f7e2b98575621019aa40ac616be58ff984e0 and fixed in 6.12.35 with commit 015f04ac884a454d4d8aaa7b67758f047742b1cf
	Issue introduced in 6.7 with commit 70e6f7e2b98575621019aa40ac616be58ff984e0 and fixed in 6.15.4 with commit cefbafcbdef011d6ef9414902311afdfba3c33eb
	Issue introduced in 6.7 with commit 70e6f7e2b98575621019aa40ac616be58ff984e0 and fixed in 6.16-rc1 with commit fba4ceaa242d2bdf4c04b77bda41d32d02d3925d

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-38210
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/virt/coco/tsm.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/015f04ac884a454d4d8aaa7b67758f047742b1cf
	https://git.kernel.org/stable/c/cefbafcbdef011d6ef9414902311afdfba3c33eb
	https://git.kernel.org/stable/c/fba4ceaa242d2bdf4c04b77bda41d32d02d3925d