CVE-2026-63954

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:

hpfs: fix a crash if hpfs_map_dnode_bitmap fails

If hpfs_map_dnode_bitmap fails, the code would call hpfs_brelse4 on uninitialized quad buffer head, causing a crash.

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

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (8)

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

hpfs: fix a crash if hpfs_map_dnode_bitmap fails - kernel/git/stable/linux.git - Linux kernel stable tree

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

hpfs: fix a crash if hpfs_map_dnode_bitmap fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/974820a59efde7c1a7e1260bcfe9bb81f833cc9f
generic

hpfs: fix a crash if hpfs_map_dnode_bitmap fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c58c55a2a16f7274772507bd1637be609351b4f
generic

hpfs: fix a crash if hpfs_map_dnode_bitmap fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4f37bb30b57d6d403d02673074555bd3c3602bef
generic

hpfs: fix a crash if hpfs_map_dnode_bitmap fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d73a533760bc5abb83b3cc759133596f7bb708f
generic

hpfs: fix a crash if hpfs_map_dnode_bitmap fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1648a3c7f4e18f46a4881920133fc4f2494185a0
generic

hpfs: fix a crash if hpfs_map_dnode_bitmap fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0886c6f257fe3663f80218aa1919b0f3f21bf22c
generic

hpfs: fix a crash if hpfs_map_dnode_bitmap fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/010b08084000ef018f1a8de5197087f3b91d8cfe

Vendor Advisories for CVE-2026-63954(2)

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

Patch Availability(6)

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 ... 5.10.92-2 (54 versions)5.10.259-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 17× in last 7d / 111× 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 223 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63954?
CVE-2026-63954 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: hpfs: fix a crash if hpfsmapdnode_bitmap fails If hpfsmapdnodebitmap fails, the code would call hpfsbrelse4 on uninitialized quad buffer head, causing a crash.
When was CVE-2026-63954 disclosed?
CVE-2026-63954 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-63954 actively exploited?
CVE-2026-63954 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-63954?
CVE-2026-63954 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63954?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63954, 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-63954

Explore →

Is Your Infrastructure Affected by CVE-2026-63954?

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