CVE-2026-43201

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:

APEI/GHES: ARM processor Error: don't go past allocated memory

If the BIOS generates a very small ARM Processor Error, or an incomplete one, the current logic will fail to deferrence

err->section_length and ctx_info->size

Add checks to avoid that. With such changes, such GHESv2 records won't cause OOPSes like this:

[ 1.492129] Internal error: Oops: 0000000096000005 [#1] SMP [ 1.495449] Modules linked in: [ 1.495820] CPU: 0 UID: 0 PID: 9 Comm: kworker/0:0 Not tainted 6.18.0-rc1-00017-gabadcc3553dd-dirty #18 PREEMPT [ 1.496125] Hardware name: QEMU QEMU Virtual Machine, BIOS unknown 02/02/2022 [ 1.496433] Workqueue: kacpi_notify acpi_os_execute_deferred [ 1.496967] pstate: 814000c5 (Nzcv daIF +PAN -UAO -TCO +DIT -SSBS BTYPE=--) [ 1.497199] pc : log_arm_hw_error+0x5c/0x200 [ 1.497380] lr : ghes_handle_arm_hw_error+0x94/0x220

0xffff8000811c5324 is in log_arm_hw_error (../drivers/ras/ras.c:75). 70 err_info = (struct cper_arm_err_info *)(err + 1); 71 ctx_info = (struct cper_arm_ctx_info *)(err_info + err->err_info_num); 72 ctx_err = (u8 *)ctx_info; 73 74 for (n = 0; n < err->context_info_num; n++) { 75 sz = sizeof(struct cper_arm_ctx_info) + ctx_info->size; 76 ctx_info = (struct cper_arm_ctx_info *)((long)ctx_info + sz); 77 ctx_len += sz; 78 } 79

and similar ones while trying to access section_length on an error dump with too small size.

[ rjw: Subject tweaks ]

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 11, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

APEI/GHES: ARM processor Error: don't go past allocated memory - kernel/git/stable/linux.git - Linux kernel stable tree

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

APEI/GHES: ARM processor Error: don't go past allocated memory - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/87880af2d24e62a84ed19943dbdd524f097172f2
generic

APEI/GHES: ARM processor Error: don't go past allocated memory - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/242c652849d979d0133c315a42d9acea0ff88390
generic

APEI/GHES: ARM processor Error: don't go past allocated memory - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/136093ba4161e0080088abff48273f6830a47766

Vendor Advisories for CVE-2026-43201(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

(2 across 2 ecosystems)
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 (113 versions)6.19.6-1

Additional Vendor Advisories

(12)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-43201?
CVE-2026-43201 is a medium vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: APEI/GHES: ARM processor Error: don't go past allocated memory If the BIOS generates a very small ARM Processor Error, or an incomplete one, the current logic will fail to deferrence err->section_length and ctx_info->size Add…
When was CVE-2026-43201 disclosed?
CVE-2026-43201 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43201 actively exploited?
CVE-2026-43201 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.3% of all scored CVEs.
What is the CVSS score of CVE-2026-43201?
CVE-2026-43201 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43201?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43201, 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-43201

Explore →

Is Your Infrastructure Affected by CVE-2026-43201?

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