CVE-2026-63995

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:

ethtool: cmis: validate start_cmd_payload_size from module

The CMIS firmware update code reads start_cmd_payload_size from the module's FW Management Features CDB reply and uses it directly as the byte count for memcpy. The destination buffer is 112 bytes (ETHTOOL_CMIS_CDB_LPL_MAX_PL_LENGTH - 8). So a malicious module (or corrupted response) can cause a OOB write later on in cmis_fw_update_start_download().

Let's error out. If modules that expect longer LPL writes actually exist we should revisit.

struct cmis_cdb_start_fw_download_pl's definition has to move, no change there.

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

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (4)

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

ethtool: cmis: validate start_cmd_payload_size from module - kernel/git/stable/linux.git - Linux kernel stable tree

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

ethtool: cmis: validate start_cmd_payload_size from module - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/63112b4515469d00008452d9cfe3fb3bf1aa2df3
generic

ethtool: cmis: validate start_cmd_payload_size from module - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/12c2496a71f82f63617971ca9b730dffa05cf58b
generic

ethtool: cmis: validate start_cmd_payload_size from module - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0696709e951be54c699664adf546d16e28974d53

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

(2 across 2 ecosystems)
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 30× in last 7d / 158× 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 208 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63995?
CVE-2026-63995 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: ethtool: cmis: validate startcmdpayload_size from module The CMIS firmware update code reads startcmdpayload_size from the module's FW Management Features CDB reply and uses it directly as the byte count for memcpy. The destination…
When was CVE-2026-63995 disclosed?
CVE-2026-63995 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-63995 actively exploited?
CVE-2026-63995 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 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-63995?
CVE-2026-63995 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63995?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63995, 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-63995

Explore →

Is Your Infrastructure Affected by CVE-2026-63995?

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