CVE-2025-39728
clk: samsung: Fix UBSAN panic in samsung_clk_init()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: clk: samsung: Fix UBSAN panic in samsung_clk_init() With UBSAN_ARRAY_BOUNDS=y, I'm hitting the below panic due to dereferencing `ctx->clk_data.hws` before setting `ctx->clk_data.num = nr_clks`. Move that up to fix the crash. UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP <snip> Call trace: samsung_clk_init+0x110/0x124 (P) samsung_clk_init+0x48/0x124 (L) samsung_cmu_register_one+0x3c/0xa0 exynos_arm64_register_cmu+0x54/0x64 __gs101_cmu_top_of_clk_init_declare+0x28/0x60 ...
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.5
References 8
git.kernel.org
- stable/c/00307934eb94aaa0a99addfb37b9fe206f945004
- stable/c/d974e177369c034984cece9d7d4fada9f8b9c740
- stable/c/0fef48f4a70e45a93e73c39023c3a6ea624714d6
- stable/c/4d29a6dcb51e346595a15b49693eeb728925ca43
- stable/c/24307866e0ac0a5ddb462e766ceda5e27a6fbbe3
- stable/c/a1500b98cd81a32fdfb9bc63c33bb9f0c2a0a1bf
- stable/c/157de9e48007a20c65d02fc0229a16f38134a72d
- stable/c/d19d7345a7bcdb083b65568a11b11adffe0687af