Bug 2365025 (CVE-2025-37832) - CVE-2025-37832 kernel: cpufreq: sun50i: prevent out-of-bounds access
Summary: CVE-2025-37832 kernel: cpufreq: sun50i: prevent out-of-bounds access
Keywords:
Status: NEW
Alias: CVE-2025-37832
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-08 07:02 UTC by OSIDB Bzimport
Modified: 2025-05-08 11:11 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-05-08 07:02:12 UTC
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.

Comment 1 Avinash Hanwate 2025-05-08 11:05:16 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025050824-CVE-2025-37832-e235@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.