{"vulnerability": "CVE-2025-37832", "sightings": [{"uuid": "0f0fe4aa-ee23-431d-ba0a-b5fd0b206d87", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37832", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15479", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37832\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: sun50i: prevent out-of-bounds access\n\nA KASAN enabled kernel reports an out-of-bounds access when handling the\nnvmem cell in the sun50i cpufreq driver:\n==================================================================\nBUG: KASAN: slab-out-of-bounds in sun50i_cpufreq_nvmem_probe+0x180/0x3d4\nRead of size 4 at addr ffff000006bf31e0 by task kworker/u16:1/38\n\nThis is because the DT specifies the nvmem cell as covering only two\nbytes, but we use a u32 pointer to read the value. DTs for other SoCs\nindeed specify 4 bytes, so we cannot just shorten the variable to a u16.\n\nFortunately nvmem_cell_read() allows to return the length of the nvmem\ncell, in bytes, so we can use that information to only access the valid\nportion of the data.\nTo cover multiple cell sizes, use memcpy() to copy the information into a\nzeroed u32 buffer, then also make sure we always read the data in little\nendian fashion, as this is how the data is stored in the SID efuses.\n\ud83d\udccf Published: 2025-05-08T06:26:22.965Z\n\ud83d\udccf Modified: 2025-05-08T06:26:22.965Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/40bf7f560ca4c2468d518cebf14561bc864f58f8\n2. https://git.kernel.org/stable/c/dba5a1f963cf781c0b60f4b7f07465a6c687c27e\n3. https://git.kernel.org/stable/c/14c8a418159e541d70dbf8fc71225d1623beaf0f", "creation_timestamp": "2025-05-08T07:23:04.000000Z"}, {"uuid": "b8116048-1f80-4d12-91e9-cb2d5e3f87c6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37832", "type": "seen", "source": "https://t.me/cvedetector/24795", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37832 - Allwinner cpufreq sun50i Linux Kernel Out-of-Bounds Read Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37832 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncpufreq: sun50i: prevent out-of-bounds access  \n  \nA KASAN enabled kernel reports an out-of-bounds access when handling the  \nnvmem cell in the sun50i cpufreq driver:  \n==================================================================  \nBUG: KASAN: slab-out-of-bounds in sun50i_cpufreq_nvmem_probe+0x180/0x3d4  \nRead of size 4 at addr ffff000006bf31e0 by task kworker/u16:1/38  \n  \nThis is because the DT specifies the nvmem cell as covering only two  \nbytes, but we use a u32 pointer to read the value. DTs for other SoCs  \nindeed specify 4 bytes, so we cannot just shorten the variable to a u16.  \n  \nFortunately nvmem_cell_read() allows to return the length of the nvmem  \ncell, in bytes, so we can use that information to only access the valid  \nportion of the data.  \nTo cover multiple cell sizes, use memcpy() to copy the information into a  \nzeroed u32 buffer, then also make sure we always read the data in little  \nendian fashion, as this is how the data is stored in the SID efuses. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:51.000000Z"}, {"uuid": "c65f97a9-9079-43ba-962d-6dc2ad360d07", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37832", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3loneb3on7cx2", "content": "", "creation_timestamp": "2025-05-08T07:11:29.091875Z"}, {"uuid": "0f3bbba6-b7fc-4afe-a570-3b00375d1f0e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37832", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqs67sz2r", "content": "", "creation_timestamp": "2025-05-08T08:31:42.309472Z"}]}