CVE-2025-38354

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-07-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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/

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

July 25, 2025

Last Modified

December 16, 2025

References (6)

Patch Availability(23)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1014.14~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (6.14.0-1018.19~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1014.14) @ plucky2026-05-30ubuntu
ubuntulinux-tools-aws-edge (6.14.0-1015.15~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-34.34~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-34.34) @ plucky2026-05-30ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-05-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-05-30ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-05-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-05-30ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-05-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-05-30ubuntu
linuxKernel @ 6.1.143—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(23)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-06 13:46 UTCEPSS rescore
  2. 2026-08-04 15:09 UTCEPSS rescore
  3. 2026-08-04 10:37 UTCEPSS rescore
  4. 2026-08-03 10:35 UTCEPSS rescore
  5. 2026-08-02 02:26 UTCEPSS rescore
  6. 2026-08-01 04:15 UTCEPSS rescore
  7. 2026-07-30 16:27 UTCEPSS rescore
  8. 2026-07-28 15:35 UTCEPSS rescore
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-25 14:17 UTCEPSS rescore
  11. 2026-07-25 14:17 UTCEPSS rescore
  12. 2026-07-24 14:17 UTCEPSS rescore
  13. 2026-07-24 00:41 UTCOSV refresh
  14. 2026-07-23 02:54 UTCEG score recompute
  15. 2026-07-22 14:07 UTCEPSS rescore
  16. 2026-07-22 14:07 UTCEPSS rescore
  17. 2026-07-21 15:24 UTCEPSS rescore
  18. 2026-07-20 17:07 UTCEPSS rescore
  19. 2026-07-19 14:30 UTCEPSS rescore
  20. 2026-07-19 14:30 UTCEPSS rescore
  21. 2026-07-18 10:04 UTCEPSS rescore
  22. 2026-07-18 10:04 UTCEPSS rescore
  23. 2026-07-16 17:02 UTCEPSS rescore
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 74 more
  1. 2026-07-15 01:59 UTCEPSS rescore
  2. 2026-07-15 01:59 UTCEPSS rescore
  3. 2026-07-13 22:29 UTCEPSS rescore
  4. 2026-07-13 22:29 UTCEPSS rescore
  5. 2026-07-13 06:12 UTCEPSS rescore
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-09 19:09 UTCEPSS rescore
  10. 2026-07-09 19:09 UTCEPSS rescore
  11. 2026-07-07 13:45 UTCEPSS rescore
  12. 2026-07-06 18:51 UTCOSV refresh
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 06:30 UTCEPSS rescore
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-07-01 15:06 UTCEPSS rescore
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
  26. 2026-06-28 04:55 UTCEPSS rescore
  27. 2026-06-28 04:55 UTCEPSS rescore
  28. 2026-06-27 03:08 UTCEPSS rescore
  29. 2026-06-27 03:08 UTCEPSS rescore
  30. 2026-06-25 13:49 UTCEPSS rescore
  31. 2026-06-25 13:49 UTCEPSS rescore
  32. 2026-06-24 14:04 UTCEPSS rescore
  33. 2026-06-24 14:04 UTCEPSS rescore
  34. 2026-06-23 21:32 UTCEPSS rescore
  35. 2026-06-23 21:32 UTCEPSS rescore
  36. 2026-06-22 14:25 UTCEPSS rescore
  37. 2026-06-22 14:25 UTCEPSS rescore
  38. 2026-06-21 14:56 UTCEPSS rescore
  39. 2026-06-21 14:56 UTCEPSS rescore
  40. 2026-06-21 01:59 UTCEPSS rescore
  41. 2026-06-21 01:59 UTCEPSS rescore
  42. 2026-06-19 19:25 UTCEPSS rescore
  43. 2026-06-19 19:25 UTCEPSS rescore
  44. 2026-06-18 17:52 UTCEPSS rescore
  45. 2026-06-18 17:52 UTCEPSS rescore
  46. 2026-06-18 06:43 UTCOSV refresh
  47. 2026-06-17 17:52 UTCEPSS rescore
  48. 2026-06-16 17:52 UTCEPSS rescore
  49. 2026-06-16 17:52 UTCEPSS rescore
  50. 2026-06-14 23:17 UTCEPSS rescore
  51. 2026-06-13 23:00 UTCEPSS rescore
  52. 2026-06-12 23:11 UTCEPSS rescore
  53. 2026-06-11 14:00 UTCEPSS rescore
  54. 2026-06-10 22:18 UTCEPSS rescore
  55. 2026-06-10 13:22 UTCEPSS rescore
  56. 2026-06-08 14:16 UTCEPSS rescore
  57. 2026-06-08 14:16 UTCEPSS rescore
  58. 2026-06-07 15:24 UTCEPSS rescore
  59. 2026-06-06 13:47 UTCEPSS rescore
  60. 2026-06-06 13:47 UTCEPSS rescore
  61. 2026-06-05 22:46 UTCEPSS rescore
  62. 2026-06-05 22:46 UTCEPSS rescore
  63. 2026-06-05 06:10 UTCEPSS rescore
  64. 2026-06-05 06:10 UTCEPSS rescore
  65. 2026-06-02 20:12 UTCEPSS rescore
  66. 2026-06-01 13:51 UTCEPSS rescore
  67. 2026-06-01 13:51 UTCEPSS rescore
  68. 2026-05-31 22:30 UTCEPSS rescore
  69. 2026-05-31 22:30 UTCEPSS rescore
  70. 2026-05-31 00:16 UTCEPSS rescore
  71. 2026-05-30 01:27 UTCEG score recompute
  72. 2026-05-30 01:27 UTCVendor advisory
  73. 2026-05-30 01:26 UTCGHSA enrichment
  74. 2026-05-29 13:44 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2025-38354?
CVE-2025-38354 is a medium vulnerability published on July 25, 2025. 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 ofdevfreqcooling_register() will immediately try to apply devfreq…
When was CVE-2025-38354 disclosed?
CVE-2025-38354 was first published in the National Vulnerability Database on July 25, 2025, with the most recent update on December 16, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-38354 actively exploited?
CVE-2025-38354 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.8% of all scored CVEs.
What is the CVSS score of CVE-2025-38354?
CVE-2025-38354 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-38354?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-38354, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-38354

Explore →

Is Your Infrastructure Affected by CVE-2025-38354?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs