CVE-2026-45865: Linux kernel · mctp i2c: initialise event handler read bytes
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
Description
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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-45865 (opens in a new tab)
- git.kernel.org/stable/c/11f83253244060b5de5eac787f61ae3f3e559d01 (opens in a new tab)
- git.kernel.org/stable/c/1eeedb310229bfee9dd4d992e5bba33fe1378a8f (opens in a new tab)
- git.kernel.org/stable/c/2a14e91b6d76639dac70ea170f4384c1ee3cb48d (opens in a new tab)
- git.kernel.org/stable/c/6ff2ebfef75fbc57d937d8fbe738b967edf2d331 (opens in a new tab)
- git.kernel.org/stable/c/93e01e837e105299f1c259ef71f6e1ec4fe806e3 (opens in a new tab)
- git.kernel.org/stable/c/fa9861e5c8af7651dddfa8d490aaada17ae33b6c (opens in a new tab)