CVE-2026-63915

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

nfc: hci: fix out-of-bounds read in HCP header parsing

Both nfc_hci_recv_from_llc() and nci_hci_data_received_cb() read packet->header from skb->data at function entry without first checking that the buffer holds at least one byte. A malicious NFC peer can send a 0-byte HCP frame that passes through the SHDLC layer and reaches these functions, causing an out-of-bounds heap read of packet->header. The same 0-byte frame, if queued as a non-final fragment, also causes the reassembly loop to underflow msg_len to UINT_MAX, triggering skb_over_panic() when the reassembled skb is written.

Fix this by adding a pskb_may_pull() check at the entry of each function before packet->header is first accessed. The existing pskb_may_pull() checks before the reassembled hcp_skb is cast to struct hcp_packet remain in place to guard the 2-byte HCP message header.

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

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (8)

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

nfc: hci: fix out-of-bounds read in HCP header parsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

nfc: hci: fix out-of-bounds read in HCP header parsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

nfc: hci: fix out-of-bounds read in HCP header parsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

nfc: hci: fix out-of-bounds read in HCP header parsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

nfc: hci: fix out-of-bounds read in HCP header parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83b1362edc9d6ae376c6f36da116e2c70f2e70a6
generic

nfc: hci: fix out-of-bounds read in HCP header parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/37382293f174b82a0616c8295e32b1fc8e13d1ed
generic

nfc: hci: fix out-of-bounds read in HCP header parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/22d41b176b9989efd21c3b2d3abf6728f05b9d9a
generic

nfc: hci: fix out-of-bounds read in HCP header parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1905f5ec3641b2b234bb63549c8ca11ab85466eb

Vendor Advisories for CVE-2026-63915(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)

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 (138 versions)7.0.12-1

All Vendor Advisories

(5)

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 215 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63915?
CVE-2026-63915 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: nfc: hci: fix out-of-bounds read in HCP header parsing Both nfchcirecvfromllc() and ncihcidatareceivedcb() read packet->header from skb->data at function entry without first checking that the buffer holds at least one byte. A…
When was CVE-2026-63915 disclosed?
CVE-2026-63915 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-63915 actively exploited?
CVE-2026-63915 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 71.8% of all scored CVEs.
What is the CVSS score of CVE-2026-63915?
CVE-2026-63915 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63915?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63915, 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-63915

Explore →

Is Your Infrastructure Affected by CVE-2026-63915?

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