CVE-2026-63879

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:

drm/amdgpu: fix amdgpu_hmm_range_get_pages

The notifier sequence must only be read once or otherwise we could work with invalid pages.

While at it also fix the coding style, e.g. drop the pre-initialized return value and use the common define for 2G range.

(cherry picked from commit c08972f555945cda57b0adb72272a37910153390)

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
7%
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

drm/amdgpu: fix amdgpu_hmm_range_get_pages - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/962d684b5dc0741dcd93485d41b450de402d5592
generic

drm/amdgpu: fix amdgpu_hmm_range_get_pages - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2fd24407457a6b181ba827705678da70e528dcd0

Vendor Advisories for CVE-2026-63879(3)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
redhatkernel-0:6.12.0-211.49.1.el10_22026-08-20redhat
redhatkernel-0:5.14.0-687.41.1.el9_82026-08-20redhat
redhatkernel-rt-0:4.18.0-553.156.1.rt7.497.el8_102026-08-17redhat
redhatkernel-0:4.18.0-553.156.1.el8_102026-08-17redhat

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

Additional Vendor Advisories

(8)

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 32× in last 7d / 163× 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 212 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63879?
CVE-2026-63879 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix amdgpuhmmrangegetpages The notifier sequence must only be read once or otherwise we could work with invalid pages. While at it also fix the coding style, e.g. drop the pre-initialized return value and use the common…
When was CVE-2026-63879 disclosed?
CVE-2026-63879 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-63879 actively exploited?
CVE-2026-63879 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 93.2% of all scored CVEs.
What is the CVSS score of CVE-2026-63879?
CVE-2026-63879 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63879?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63879, 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-63879

Explore →

Is Your Infrastructure Affected by CVE-2026-63879?

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

Start Free Scan →Browse All CVEs