CVE-2026-43221

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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:

ipmi: ipmb: initialise event handler read bytes

IPMB doesn't use i2c reads, but the handler needs to set a value. Otherwise an i2c read will return an uninitialised value from the bus driver.

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

Published

May 6, 2026

Last Modified

May 12, 2026

Advisory Details (6)

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

ipmi: ipmb: initialise event handler read bytes - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipmi: ipmb: initialise event handler read bytes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f235ccecd03c436cb1683eac16b12f119e54aa9
generic

ipmi: ipmb: initialise event handler read bytes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/905554ebd76aeee370bfd5136ea11e0b9d75c6f1
generic

ipmi: ipmb: initialise event handler read bytes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/56d5c0557e53c4d8d92a619fa83eaae178165e07
generic

ipmi: ipmb: initialise event handler read bytes - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipmi: ipmb: initialise event handler read bytes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/102712417bb6aa9a00d852bc59cb0a276db486c4

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.19~rc8-1~exp1 (116 versions)6.19.6-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(12)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43221?
CVE-2026-43221 is a medium vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: ipmi: ipmb: initialise event handler read bytes IPMB doesn't use i2c reads, but the handler needs to set a value. Otherwise an i2c read will return an uninitialised value from the bus driver.
When was CVE-2026-43221 disclosed?
CVE-2026-43221 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43221 actively exploited?
CVE-2026-43221 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-43221?
CVE-2026-43221 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43221?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43221, 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-43221

Explore →

Is Your Infrastructure Affected by CVE-2026-43221?

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