linux-cve-announce - CVE-2025-37832: cpufreq: sun50i: prevent out-of-bounds access

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: <2025050824-CVE-2025-37832-e235@gregkh>
Date: Thu,  8 May 2025 08:39:41 +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-37832: cpufreq: sun50i: prevent out-of-bounds access

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

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

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

cpufreq: sun50i: prevent out-of-bounds access

A KASAN enabled kernel reports an out-of-bounds access when handling the
nvmem cell in the sun50i cpufreq driver:
==================================================================
BUG: KASAN: slab-out-of-bounds in sun50i_cpufreq_nvmem_probe+0x180/0x3d4
Read of size 4 at addr ffff000006bf31e0 by task kworker/u16:1/38

This is because the DT specifies the nvmem cell as covering only two
bytes, but we use a u32 pointer to read the value. DTs for other SoCs
indeed specify 4 bytes, so we cannot just shorten the variable to a u16.

Fortunately nvmem_cell_read() allows to return the length of the nvmem
cell, in bytes, so we can use that information to only access the valid
portion of the data.
To cover multiple cell sizes, use memcpy() to copy the information into a
zeroed u32 buffer, then also make sure we always read the data in little
endian fashion, as this is how the data is stored in the SID efuses.

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


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

	Issue introduced in 6.10 with commit 6cc4bcceff9af0e6be9738096d95e4ba75e75123 and fixed in 6.12.26 with commit 40bf7f560ca4c2468d518cebf14561bc864f58f8
	Issue introduced in 6.10 with commit 6cc4bcceff9af0e6be9738096d95e4ba75e75123 and fixed in 6.14.5 with commit dba5a1f963cf781c0b60f4b7f07465a6c687c27e
	Issue introduced in 6.10 with commit 6cc4bcceff9af0e6be9738096d95e4ba75e75123 and fixed in 6.15-rc4 with commit 14c8a418159e541d70dbf8fc71225d1623beaf0f

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-37832
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/cpufreq/sun50i-cpufreq-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/40bf7f560ca4c2468d518cebf14561bc864f58f8
	https://git.kernel.org/stable/c/dba5a1f963cf781c0b60f4b7f07465a6c687c27e
	https://git.kernel.org/stable/c/14c8a418159e541d70dbf8fc71225d1623beaf0f