CVE-2026-43281

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1EG
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.1Exploit: 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: Prevent out-of-bounds access in fw_mbox_index_xlate()

Although it is guided that #mbox-cells must be at least 1, there are many instances of #mbox-cells = <0>; in the device tree. If that is the case and the corresponding mailbox controller does not provide fw_xlate and of_xlate function pointers, fw_mbox_index_xlate()` will be used by default and out-of-bounds accesses could occur due to lack of bounds check in that function.

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

Published

May 6, 2026

Last Modified

June 1, 2026

Advisory Details (6)

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

mailbox: Prevent out-of-bounds access in fw_mbox_index_xlate() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mailbox: Prevent out-of-bounds access in fw_mbox_index_xlate() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mailbox: Prevent out-of-bounds access in fw_mbox_index_xlate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4caae8168d1b808c7d4ff481295292e3f97f90fb
generic

mailbox: Prevent out-of-bounds access in fw_mbox_index_xlate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/31c4c67dec3362094a6747a171a4848e98542265
generic

mailbox: Prevent out-of-bounds access in of_mbox_index_xlate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2662ed331a69c0b551f78af58f12eb629a89a36f
generic

mailbox: Prevent out-of-bounds access in fw_mbox_index_xlate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01d9a8c2615d436b2b30c19c1afe9fcd5726ff6d

Vendor Advisories for CVE-2026-43281(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 @ 5.10.258—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.

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43281?
CVE-2026-43281 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: mailbox: Prevent out-of-bounds access in fwmboxindex_xlate() Although it is guided that #mbox-cells must be at least 1, there are many instances of #mbox-cells = <0>; in the device tree. If that is the case and the corresponding…
When was CVE-2026-43281 disclosed?
CVE-2026-43281 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on June 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43281 actively exploited?
CVE-2026-43281 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-43281?
CVE-2026-43281 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-43281?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43281, 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

Explore the affected products and dependency analysis for CVE-2026-43281

Explore →

Is Your Infrastructure Affected by CVE-2026-43281?

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

Start Free Scan →Browse All CVEs