CVE-2026-43274

HIGHNVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.4EG
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.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

mailbox: mchp-ipc-sbi: fix out-of-bounds access in mchp_ipc_get_cluster_aggr_irq()

The cluster_cfg array is dynamically allocated to hold per-CPU configuration structures, with its size based on the number of online CPUs. Previously, this array was indexed using hartid, which may be non-contiguous or exceed the bounds of the array, leading to out-of-bounds access. Switch to using cpuid as the index, as it is guaranteed to be within the valid range provided by for_each_online_cpu().

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
42(Track)
EG Risk 42/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
Severity84% × 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

August 5, 2026

Advisory Details (3)

Auto-updated May 8, 2026
No patch confirmed yet.
generic

mailbox: mchp-ipc-sbi: fix out-of-bounds access in mchp_ipc_get_cluster_aggr_irq() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mailbox: mchp-ipc-sbi: fix out-of-bounds access in mchp_ipc_get_cluster_aggr_irq() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/95438699c92947155823dcd3918049a07f3cd867
generic

mailbox: mchp-ipc-sbi: fix out-of-bounds access in mchp_ipc_get_cluster_aggr_irq() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0442b6229e2eedc95a6d3d18ce75dec7f5b5377c

Vendor Advisories for CVE-2026-43274(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.16—osv

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (113 versions)6.19.6-1—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43274?
CVE-2026-43274 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: mailbox: mchp-ipc-sbi: fix out-of-bounds access in mchpipcgetclusteraggr_irq() The cluster_cfg array is dynamically allocated to hold per-CPU configuration structures, with its size based on the number of online CPUs. Previously,…
When was CVE-2026-43274 disclosed?
CVE-2026-43274 was first published in the National Vulnerability Database on May 6, 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-43274 actively exploited?
CVE-2026-43274 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.0% of all scored CVEs.
What is the CVSS score of CVE-2026-43274?
CVE-2026-43274 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-43274?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43274, 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-43274

Explore →

Is Your Infrastructure Affected by CVE-2026-43274?

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

Start Free Scan →Browse All CVEs