CVE-2025-38354— drm/msm/gpu: Fix crash when throttling GPU immediately during boot
Affected Version Matrix 16
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | 6694482a70e9536efbf2ac233cbf0c302d6e2dae< ae2015b0dbc0eea7aaf022194371f451f784d994 | affected |
6694482a70e9536efbf2ac233cbf0c302d6e2dae< 7946a10f8da75abc494e4bb80243e153e93e459a | affected | ||
6694482a70e9536efbf2ac233cbf0c302d6e2dae< 1847ea44e3bdf7da8ff4158bc01b43a2e46394bd | affected | ||
6694482a70e9536efbf2ac233cbf0c302d6e2dae< a6f673cc9488fd722c601fe020601dba14db21b2 | affected | ||
6694482a70e9536efbf2ac233cbf0c302d6e2dae< b71717735be48d7743a34897e9e44a0b53e30c0e | affected | ||
1f6c087dd6a915f1c3471f0f0f696847fc8c592f | affected | ||
9c8b3f05fb18fba12f3fca80a378c9b8f3d04cd6 | affected | ||
5.18.18< 5.19 | affected | ||
| … +8 more rows | |||
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2025-38354
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗ Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
drm/msm/gpu: Fix crash when throttling GPU immediately during boot
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: drm/msm/gpu: Fix crash when throttling GPU immediately during boot There is a small chance that the GPU is already hot during boot. In that case, the call to of_devfreq_cooling_register() will immediately try to apply devfreq cooling, as seen in the following crash: Unable to handle kernel paging request at virtual address 0000000000014110 pc : a6xx_gpu_busy+0x1c/0x58 [msm] lr : msm_devfreq_get_dev_status+0xbc/0x140 [msm] Call trace: a6xx_gpu_busy+0x1c/0x58 [msm] (P) devfreq_simple_ondemand_func+0x3c/0x150 devfreq_update_target+0x44/0xd8 qos_max_notifier_call+0x30/0x84 blocking_notifier_call_chain+0x6c/0xa0 pm_qos_update_target+0xd0/0x110 freq_qos_apply+0x3c/0x74 apply_constraint+0x88/0x148 __dev_pm_qos_update_request+0x7c/0xcc dev_pm_qos_update_request+0x38/0x5c devfreq_cooling_set_cur_state+0x98/0xf0 __thermal_cdev_update+0x64/0xb4 thermal_cdev_update+0x4c/0x58 step_wise_manage+0x1f0/0x318 __thermal_zone_device_update+0x278/0x424 __thermal_cooling_device_register+0x2bc/0x308 thermal_of_cooling_device_register+0x10/0x1c of_devfreq_cooling_register_power+0x240/0x2bc of_devfreq_cooling_register+0x14/0x20 msm_devfreq_init+0xc4/0x1a0 [msm] msm_gpu_init+0x304/0x574 [msm] adreno_gpu_init+0x1c4/0x2e0 [msm] a6xx_gpu_init+0x5c8/0x9c8 [msm] adreno_bind+0x2a8/0x33c [msm] ... At this point we haven't initialized the GMU at all yet, so we cannot read the GMU registers inside a6xx_gpu_busy(). A similar issue was fixed before in commit 6694482a70e9 ("drm/msm: Avoid unclocked GMU register access in 6xx gpu_busy"): msm_devfreq_init() does call devfreq_suspend_device(), but unlike msm_devfreq_suspend(), it doesn't set the df->suspended flag accordingly. This means the df->suspended flag does not match the actual devfreq state after initialization and msm_devfreq_get_dev_status() will end up accessing GMU registers, causing the crash. Fix this by setting df->suspended correctly during initialization. Patchwork: https://patchwork.freedesktop.org/patch/650772/
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于msm_devfreq_get_dev_status函数在启动时立即节流GPU导致崩溃。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
II. Public POCs for CVE-2025-38354
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POCPremium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2025-38354
请登录查看更多情报信息。
Same Patch Batch · Linux · 2025-07-25 · 114 CVEs total
| CVE-2025-38426 | drm/amdgpu: Add basic validation for RAS header | |
| CVE-2025-38440 | net/mlx5e: Fix race between DIM disable and net_dim() | |
| CVE-2025-38438 | ASoC: SOF: Intel: hda: Use devm_kstrdup() to avoid memleak. | |
| CVE-2025-38437 | ksmbd: fix potential use-after-free in oplock/lease break ack | |
| CVE-2025-38436 | drm/scheduler: signal scheduled fence when kill job | |
| CVE-2025-38435 | riscv: vector: Fix context save/restore with xtheadvector | |
| CVE-2025-38434 | Revert "riscv: Define TASK_SIZE_MAX for __access_ok()" | |
| CVE-2025-38433 | riscv: fix runtime constant support for nommu kernels | |
| CVE-2025-38432 | net: netpoll: Initialize UDP checksum field before checksumming | |
| CVE-2025-38431 | smb: client: fix regression with native SMB symlinks | |
| CVE-2025-38430 | nfsd: nfsd4_spo_must_allow() must check this is a v4 compound request | |
| CVE-2025-38429 | bus: mhi: ep: Update read pointer only after buffer is written | |
| CVE-2025-38428 | Input: ims-pcu - check record size in ims_pcu_flash_firmware() | |
| CVE-2025-38427 | video: screen_info: Relocate framebuffers behind PCI bridges | |
| CVE-2025-38425 | i2c: tegra: check msg length in SMBUS block read | |
| CVE-2025-38414 | wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 | |
| CVE-2025-38417 | ice: fix eswitch code memory leak in reset scenario | |
| CVE-2025-38416 | NFC: nci: uart: Set tty->disc_data only in success path | |
| CVE-2025-38415 | Squashfs: check return result of sb_min_blocksize | |
| CVE-2025-38418 | remoteproc: core: Release rproc->clean_table after rproc_attach() fails |
Showing top 20 of 114 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
- CVE-2026-46300
net: skbuff: preserve shared-frag marker during coalescing - CVE-2026-43503
net: skbuff: propagate shared-frag marker through frag-trans - CVE-2026-43502
net/rds: handle zerocopy send cleanup before the message is - CVE-2026-43501
ipv6: rpl: reserve mac_len headroom when recompressed SRH gr - CVE-2026-43498
accel/ivpu: Disallow re-exporting imported GEM objects
Same vendor: Linux
- CVE-2026-46300
net: skbuff: preserve shared-frag marker during coalescing - CVE-2026-43503
net: skbuff: propagate shared-frag marker through frag-trans - CVE-2026-43502
net/rds: handle zerocopy send cleanup before the message is - CVE-2026-43501
ipv6: rpl: reserve mac_len headroom when recompressed SRH gr - CVE-2026-43498
accel/ivpu: Disallow re-exporting imported GEM objects
V. Comments for CVE-2025-38354
No comments yet