CVE-2025-39752

ARM: rockchip: fix kernel hang during smp initialization

CVE-2025-39752 is fixed in 9 products on 1 platform, first by DEBIAN-CVE-2025-39752, released September 11, 2025. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
5.5
Moderate
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0018
7th percentile

In the Linux kernel, the following vulnerability has been resolved: ARM: rockchip: fix kernel hang during smp initialization In order to bring up secondary CPUs main CPU write trampoline code to SRAM. The trampoline code is written while secondary CPUs are powered on (at least that true for RK3188 CPU). Sometimes that leads to kernel hang. Probably because secondary CPU execute trampoline code while kernel doesn't expect. The patch moves SRAM initialization step to the point where all secondary CPUs are powered down. That fixes rarely hangs on RK3188: [ 0.091568] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.091996] rockchip_smp_prepare_cpus: ncores 4

Where it's fixed

ProductFixed inFixReleased
Linux
kernel-uek · ol 8 0:5.4.17-2136.348.3.el7uek ELSA-2025-20663 Oct 11, 2025
kernel-uek-container · ol 8 0:5.4.17-2136.348.3.el7uek ELSA-2025-20663 Oct 11, 2025
kernel-uek-container-debug · ol 8 0:5.4.17-2136.348.3.el7uek ELSA-2025-20663 Oct 11, 2025
kernel-uek-debug · ol 8 0:5.4.17-2136.348.3.el7uek ELSA-2025-20663 Oct 11, 2025
kernel-uek-debug-devel · ol 8 0:5.4.17-2136.348.3.el7uek ELSA-2025-20663 Oct 11, 2025
kernel-uek-devel · ol 8 0:5.4.17-2136.348.3.el7uek ELSA-2025-20663 Oct 11, 2025
kernel-uek-doc · ol 8 0:5.4.17-2136.348.3.el7uek ELSA-2025-20663 Oct 11, 2025
kernel-uek-tools · ol 8 0:5.4.17-2136.348.3.el7uek ELSA-2025-20663 Oct 11, 2025
linux · Debian 12.15 (bookworm) 6.1.153-1 DEBIAN-CVE-2025-39752 Sep 11, 2025
linux · Debian 13.5 (trixie) 6.12.43-1 DEBIAN-CVE-2025-39752 Sep 11, 2025
linux · Debian 14 6.16.3-1 DEBIAN-CVE-2025-39752 Sep 11, 2025

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.