CVE-2026-72453: regcache: Do not overwrite error code when finalizing cache after error

CVE-2026-72453: regcache: Do not overwrite error code when finalizing cache after error

[Greg Kroah-Hartman]

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

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

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

regcache: Do not overwrite error code when finalizing cache after error

During regcache initialization, if an error occurs in the
cache_ops->populate callback, and if cache operations include an exit
callback, the error code from populate() is overwritten with the return
value from exit(). This hides the error condition from the caller of
regcache_init(), and can cause NULL pointer dereferences when the regcache
is later accessed.

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


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

	Issue introduced in 6.19 with commit 94a3a95f03154d8d4c6206950a7f6ef9a30baec6 and fixed in 7.1.5 with commit 9f171aa115ec76be02c76c5765cd2c865279e34a
	Issue introduced in 6.19 with commit 94a3a95f03154d8d4c6206950a7f6ef9a30baec6 and fixed in 7.2-rc1 with commit 9108f7fa493b4c88cbc09503e0c164244456bad5

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-72453
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/base/regmap/regcache.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/9f171aa115ec76be02c76c5765cd2c865279e34a
	https://git.kernel.org/stable/c/9108f7fa493b4c88cbc09503e0c164244456bad5