CVE-2026-45865

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

mctp i2c: initialise event handler read bytes

Set a 0xff value for i2c reads of an mctp-i2c device. Otherwise reads will return "val" from the i2c bus driver. For i2c-aspeed and i2c-npcm7xx that is a stack uninitialised u8.

Tested with "i2ctransfer -y 1 r10@0x34" where 0x34 is a mctp-i2c instance, now it returns all 0xff.

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

Published

May 27, 2026

Last Modified

June 25, 2026

Advisory Details (6)

Auto-updated Jun 25, 2026
No patch confirmed yet.
generic

mctp i2c: initialise event handler read bytes - kernel/git/stable/linux.git - Linux kernel stable tree

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

mctp i2c: initialise event handler read bytes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/93e01e837e105299f1c259ef71f6e1ec4fe806e3
generic

mctp i2c: initialise event handler read bytes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ff2ebfef75fbc57d937d8fbe738b967edf2d331
generic

mctp i2c: initialise event handler read bytes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a14e91b6d76639dac70ea170f4384c1ee3cb48d
generic

mctp i2c: initialise event handler read bytes - kernel/git/stable/linux.git - Linux kernel stable tree

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

mctp i2c: initialise event handler read bytes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/11f83253244060b5de5eac787f61ae3f3e559d01

Vendor Advisories for CVE-2026-45865(1)

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

Patch Availability(13)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (103 versions)6.18.14-1

All Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 10× in last 7d / 42× 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 193 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45865?
CVE-2026-45865 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: mctp i2c: initialise event handler read bytes Set a 0xff value for i2c reads of an mctp-i2c device. Otherwise reads will return "val" from the i2c bus driver. For i2c-aspeed and i2c-npcm7xx that is a stack uninitialised u8. Tested…
When was CVE-2026-45865 disclosed?
CVE-2026-45865 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45865 actively exploited?
CVE-2026-45865 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 94.4% of all scored CVEs.
What is the CVSS score of CVE-2026-45865?
CVE-2026-45865 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45865?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45865, 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-45865

Explore →

Is Your Infrastructure Affected by CVE-2026-45865?

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