CVE-2025-38091

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-07-02. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

drm/amd/display: check stream id dml21 wrapper to get plane_id

[Why & How] Fix a false positive warning which occurs due to lack of correct checks when querying plane_id in DML21. This fixes the warning when performing a mode1 reset (cat /sys/kernel/debug/dri/1/amdgpu_gpu_recover):

[ 35.751250] WARNING: CPU: 11 PID: 326 at /tmp/amd.PHpyAl7v/amd/amdgpu/../display/dc/dml2/dml2_dc_resource_mgmt.c:91 dml2_map_dc_pipes+0x243d/0x3f40 [amdgpu] [ 35.751434] Modules linked in: amdgpu(OE) amddrm_ttm_helper(OE) amdttm(OE) amddrm_buddy(OE) amdxcp(OE) amddrm_exec(OE) amd_sched(OE) amdkcl(OE) drm_suballoc_helper drm_ttm_helper ttm drm_display_helper cec rc_core i2c_algo_bit rfcomm qrtr cmac algif_hash algif_skcipher af_alg bnep amd_atl intel_rapl_msr intel_rapl_common snd_hda_codec_hdmi snd_hda_intel edac_mce_amd snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec kvm_amd snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi crct10dif_pclmul polyval_clmulni polyval_generic btusb ghash_clmulni_intel sha256_ssse3 btrtl sha1_ssse3 snd_seq btintel aesni_intel btbcm btmtk snd_seq_device crypto_simd sunrpc cryptd bluetooth snd_timer ccp binfmt_misc rapl snd i2c_piix4 wmi_bmof gigabyte_wmi k10temp i2c_smbus soundcore gpio_amdpt mac_hid sch_fq_codel msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid crc32_pclmul igc ahci xhci_pci libahci xhci_pci_renesas video wmi [ 35.751501] CPU: 11 UID: 0 PID: 326 Comm: kworker/u64:9 Tainted: G OE 6.11.0-21-generic #21~24.04.1-Ubuntu [ 35.751504] Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE [ 35.751505] Hardware name: Gigabyte Technology Co., Ltd. X670E AORUS PRO X/X670E AORUS PRO X, BIOS F30 05/22/2024 [ 35.751506] Workqueue: amdgpu-reset-dev amdgpu_debugfs_reset_work [amdgpu] [ 35.751638] RIP: 0010:dml2_map_dc_pipes+0x243d/0x3f40 [amdgpu] [ 35.751794] Code: 6d 0c 00 00 8b 84 24 88 00 00 00 41 3b 44 9c 20 0f 84 fc 07 00 00 48 83 c3 01 48 83 fb 06 75 b3 4c 8b 64 24 68 4c 8b 6c 24 40 <0f> 0b b8 06 00 00 00 49 8b 94 24 a0 49 00 00 89 c3 83 f8 07 0f 87 [ 35.751796] RSP: 0018:ffffbfa3805d7680 EFLAGS: 00010246 [ 35.751798] RAX: 0000000000010000 RBX: 0000000000000006 RCX: 0000000000000000 [ 35.751799] RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000000 [ 35.751800] RBP: ffffbfa3805d78f0 R08: 0000000000000000 R09: 0000000000000000 [ 35.751801] R10: 0000000000000000 R11: 0000000000000000 R12: ffffbfa383249000 [ 35.751802] R13: ffffa0e68f280000 R14: ffffbfa383249658 R15: 0000000000000000 [ 35.751803] FS: 0000000000000000(0000) GS:ffffa0edbe580000(0000) knlGS:0000000000000000 [ 35.751804] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 35.751805] CR2: 00005d847ef96c58 CR3: 000000041de3e000 CR4: 0000000000f50ef0 [ 35.751806] PKRU: 55555554 [ 35.751807] Call Trace: [ 35.751810] [ 35.751816] ? show_regs+0x6c/0x80 [ 35.751820] ? __warn+0x88/0x140 [ 35.751822] ? dml2_map_dc_pipes+0x243d/0x3f40 [amdgpu] [ 35.751964] ? report_bug+0x182/0x1b0 [ 35.751969] ? handle_bug+0x6e/0xb0 [ 35.751972] ? exc_invalid_op+0x18/0x80 [ 35.751974] ? asm_exc_invalid_op+0x1b/0x20 [ 35.751978] ? dml2_map_dc_pipes+0x243d/0x3f40 [amdgpu] [ 35.752117] ? math_pow+0x48/0xa0 [amdgpu] [ 35.752256] ? srso_alias_return_thunk+0x5/0xfbef5 [ 35.752260] ? math_pow+0x48/0xa0 [amdgpu] [ 35.752400] ? srso_alias_return_thunk+0x5/0xfbef5 [ 35.752403] ? math_pow+0x11/0xa0 [amdgpu] [ 35.752524] ? srso_alias_return_thunk+0x5/0xfbef5 [ 35.752526] ? core_dcn4_mode_programming+0xe4d/0x20d0 [amdgpu] [ 35.752663] ? srso_alias_return_thunk+0x5/0xfbef5 [ 35.752669] dml21_validate+0x3d4/0x980 [amdgpu]

(cherry picked from commit f8ad62c0a93e5dd94243e10f1b742232e4d6411e)

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

July 2, 2025

Last Modified

November 20, 2025

Patch Availability(8)

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

(8)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2025-38091?
CVE-2025-38091 is a high vulnerability published on July 2, 2025. In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: check stream id dml21 wrapper to get plane_id [Why & How] Fix a false positive warning which occurs due to lack of correct checks when querying plane_id in DML21. This fixes the warning when performing a mode1…
When was CVE-2025-38091 disclosed?
CVE-2025-38091 was first published in the National Vulnerability Database on July 2, 2025, with the most recent update on November 20, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-38091 actively exploited?
CVE-2025-38091 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 95.7% of all scored CVEs.
What is the CVSS score of CVE-2025-38091?
CVE-2025-38091 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-38091?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-38091, 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-38091

Explore →

Is Your Infrastructure Affected by CVE-2025-38091?

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