[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025071013-CVE-2025-38301-694f@gregkh>
Date: Thu, 10 Jul 2025 09:42:42 +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-38301: nvmem: zynqmp_nvmem: unbreak driver after cleanup
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nvmem: zynqmp_nvmem: unbreak driver after cleanup
Commit 29be47fcd6a0 ("nvmem: zynqmp_nvmem: zynqmp_nvmem_probe cleanup")
changed the driver to expect the device pointer to be passed as the
"context", but in nvmem the context parameter comes from nvmem_config.priv
which is never set - Leading to null pointer exceptions when the device is
accessed.
The Linux kernel CVE team has assigned CVE-2025-38301 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.9 with commit 29be47fcd6a06ea2e79eeeca6e69ad1e23254a69 and fixed in 6.12.34 with commit c8bb1bcea877446f86922a8fd1661b8c07d90e5c
Issue introduced in 6.9 with commit 29be47fcd6a06ea2e79eeeca6e69ad1e23254a69 and fixed in 6.15.3 with commit 3728101f56ef54425a11027a3ddc2c3941d60b71
Issue introduced in 6.9 with commit 29be47fcd6a06ea2e79eeeca6e69ad1e23254a69 and fixed in 6.16-rc1 with commit fe8abdd175d7b547ae1a612757e7902bcd62e9cf
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-38301
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/nvmem/zynqmp_nvmem.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/c8bb1bcea877446f86922a8fd1661b8c07d90e5c
https://git.kernel.org/stable/c/3728101f56ef54425a11027a3ddc2c3941d60b71
https://git.kernel.org/stable/c/fe8abdd175d7b547ae1a612757e7902bcd62e9cf
Powered by blists - more mailing lists