CVE-2025-38449

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/gem: Acquire references on GEM handles for framebuffers

A GEM handle can be released while the GEM buffer object is attached to a DRM framebuffer. This leads to the release of the dma-buf backing the buffer object, if any. [1] Trying to use the framebuffer in further mode-setting operations leads to a segmentation fault. Most easily happens with driver that use shadow planes for vmap-ing the dma-buf during a page flip. An example is shown below.

[ 156.791968] ------------[ cut here ]------------ [ 156.796830] WARNING: CPU: 2 PID: 2255 at drivers/dma-buf/dma-buf.c:1527 dma_buf_vmap+0x224/0x430 [...] [ 156.942028] RIP: 0010:dma_buf_vmap+0x224/0x430 [ 157.043420] Call Trace: [ 157.045898] [ 157.048030] ? show_trace_log_lvl+0x1af/0x2c0 [ 157.052436] ? show_trace_log_lvl+0x1af/0x2c0 [ 157.056836] ? show_trace_log_lvl+0x1af/0x2c0 [ 157.061253] ? drm_gem_shmem_vmap+0x74/0x710 [ 157.065567] ? dma_buf_vmap+0x224/0x430 [ 157.069446] ? __warn.cold+0x58/0xe4 [ 157.073061] ? dma_buf_vmap+0x224/0x430 [ 157.077111] ? report_bug+0x1dd/0x390 [ 157.080842] ? handle_bug+0x5e/0xa0 [ 157.084389] ? exc_invalid_op+0x14/0x50 [ 157.088291] ? asm_exc_invalid_op+0x16/0x20 [ 157.092548] ? dma_buf_vmap+0x224/0x430 [ 157.096663] ? dma_resv_get_singleton+0x6d/0x230 [ 157.101341] ? __pfx_dma_buf_vmap+0x10/0x10 [ 157.105588] ? __pfx_dma_resv_get_singleton+0x10/0x10 [ 157.110697] drm_gem_shmem_vmap+0x74/0x710 [ 157.114866] drm_gem_vmap+0xa9/0x1b0 [ 157.118763] drm_gem_vmap_unlocked+0x46/0xa0 [ 157.123086] drm_gem_fb_vmap+0xab/0x300 [ 157.126979] drm_atomic_helper_prepare_planes.part.0+0x487/0xb10 [ 157.133032] ? lockdep_init_map_type+0x19d/0x880 [ 157.137701] drm_atomic_helper_commit+0x13d/0x2e0 [ 157.142671] ? drm_atomic_nonblocking_commit+0xa0/0x180 [ 157.147988] drm_mode_atomic_ioctl+0x766/0xe40 [...] [ 157.346424] ---[ end trace 0000000000000000 ]---

Acquiring GEM handles for the framebuffer's GEM buffer objects prevents this from happening. The framebuffer's cleanup later puts the handle references.

Commit 1a148af06000 ("drm/gem-shmem: Use dma_buf from GEM object instance") triggers the segmentation fault easily by using the dma-buf field more widely. The underlying issue with reference counting has been present before.

v2:

  • acquire the handle instead of the BO (Christian)
  • fix comment style (Christian)
  • drop the Fixes tag (Christian)
  • rename err_ gotos
  • add missing Link tag

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
6%
KEV
Not listed

Published

July 25, 2025

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

drm/gem: Acquire references on GEM handles for framebuffers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cb4c956a15f8b7f870649454771fc3761f504b5f
generic

drm/gem: Acquire references on GEM handles for framebuffers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5307dce878d4126e1b375587318955bd019c3741
generic

drm/gem: Acquire references on GEM handles for framebuffers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3cf520d9860d4ec9f7f32068825da31f18dd3f25
generic

drm/gem: Acquire references on GEM handles for framebuffers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/08480e285c6a82ce689008d643e4a51db0aaef8b

Vendor Advisories for CVE-2025-38449(11)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-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-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ 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
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1017.17) @ plucky2026-05-30ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1016.16~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-36.36) @ plucky2026-05-30ubuntu
ubuntulinux-tools-oracle-edge (6.14.0-1017.17~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-oem-6.14 (6.14.0-1016.16) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-6.14 (6.14.0-1018.18) @ plucky2026-05-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-05-30ubuntu
redhatkernel-0:4.18.0-305.179.1.el8_42025-12-04redhat
redhatkernel-0:4.18.0-193.173.1.el8_22025-11-18redhat
redhatkernel-0:4.18.0-372.164.1.el8_62025-10-15redhat
redhatkernel-0:4.18.0-477.114.1.el8_82025-10-08redhat
redhatkernel-0:5.14.0-427.92.1.el9_42025-10-02redhat
redhatkernel-rt-0:5.14.0-70.148.1.rt21.220.el9_02025-10-01redhat
redhatkernel-0:5.14.0-284.140.1.el9_22025-10-01redhat
redhatkernel-rt-0:5.14.0-284.140.1.rt14.425.el9_22025-10-01redhat
redhatkernel-0:5.14.0-70.148.1.el9_02025-10-01redhat
redhatkernel-rt-0:4.18.0-553.75.1.rt7.416.el8_102025-09-15redhat
redhatkernel-0:4.18.0-553.75.1.el8_102025-09-15redhat
redhatkernel-0:5.14.0-570.42.2.el9_62025-09-11redhat
redhatkernel-0:6.12.0-55.31.1.el10_02025-09-08redhat
linuxKernel @ 6.6.99—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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-16.12.41-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (62 versions)6.16.3-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(14)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 25× 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.

Showing the most recent 100 of 143 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-38449?
CVE-2025-38449 is a medium vulnerability published on July 25, 2025. In the Linux kernel, the following vulnerability has been resolved: drm/gem: Acquire references on GEM handles for framebuffers A GEM handle can be released while the GEM buffer object is attached to a DRM framebuffer. This leads to the release of the dma-buf backing the buffer object, if any. [1]…
When was CVE-2025-38449 disclosed?
CVE-2025-38449 was first published in the National Vulnerability Database on July 25, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-38449 actively exploited?
CVE-2025-38449 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.5% of all scored CVEs.
What is the CVSS score of CVE-2025-38449?
CVE-2025-38449 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-38449?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-38449, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-38449

Explore →

Is Your Infrastructure Affected by CVE-2025-38449?

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

Start Free Scan →Browse All CVEs