CVE-2026-63910

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
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:

dma-buf: fix UAF in dma_buf_fd() tracepoint

Once FD_ADD() returns, the fd is live in the file descriptor table and a thread sharing that table can close() it before DMA_BUF_TRACE() runs. The close drops the last reference, __fput() frees the dma_buf, and the tracepoint then dereferences dmabuf to take dmabuf->name_lock -- slab-use-after-free.

Split FD_ADD() back into get_unused_fd_flags() + fd_install() and emit the tracepoint between them. While the fdtable slot is reserved with a NULL file pointer, a racing close() returns -EBADF without entering __fput(), so the dma_buf stays alive across the trace. Same approach as commit 2d76319c4cbb ("dma-buf: fix UAF in dma_buf_put() tracepoint").

This undoes the FD_ADD() conversion done in commit 34dfce523c90 ("dma: convert dma_buf_fd() to FD_ADD()"); FD_ADD() has no place to hook the tracepoint safely.

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

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

dma-buf: fix UAF in dma_buf_fd() tracepoint - kernel/git/stable/linux.git - Linux kernel stable tree

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

dma-buf: fix UAF in dma_buf_fd() tracepoint - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b569f86e2f8dbf6f11d31d3de794d22e18098b23

Vendor Advisories for CVE-2026-63910(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

All Vendor Advisories

(5)

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 34× in last 7d / 165× 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 211 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63910?
CVE-2026-63910 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: dma-buf: fix UAF in dmabuffd() tracepoint Once FD_ADD() returns, the fd is live in the file descriptor table and a thread sharing that table can close() it before DMABUFTRACE() runs. The close drops the last reference, fput() frees…
When was CVE-2026-63910 disclosed?
CVE-2026-63910 was first published in the National Vulnerability Database on July 19, 2026, 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-2026-63910 actively exploited?
CVE-2026-63910 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-63910?
CVE-2026-63910 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63910?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63910, 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-2026-63910

Explore →

Is Your Infrastructure Affected by CVE-2026-63910?

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

Start Free Scan →Browse All CVEs