CVE-2026-43129

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:

ima: verify the previous kernel's IMA buffer lies in addressable RAM

Patch series "Address page fault in ima_restore_measurement_list()", v3.

When the second-stage kernel is booted via kexec with a limiting command line such as "mem=" we observe a pafe fault that happens.

BUG: unable to handle page fault for address: ffff97793ff47000 RIP: ima_restore_measurement_list+0xdc/0x45a #PF: error_code(0x0000) not-present page

This happens on x86_64 only, as this is already fixed in aarch64 in commit: cbf9c4b9617b ("of: check previous kernel's ima-kexec-buffer against memory bounds")

This patch (of 3):

When the second-stage kernel is booted with a limiting command line (e.g. "mem="), the IMA measurement buffer handed over from the previous kernel may fall outside the addressable RAM of the new kernel. Accessing such a buffer can fault during early restore.

Introduce a small generic helper, ima_validate_range(), which verifies that a physical [start, end] range for the previous-kernel IMA buffer lies within addressable memory:

  • On x86, use pfn_range_is_mapped().
  • On OF based architectures, use page_is_ram().

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

Published

May 6, 2026

Last Modified

June 19, 2026

Advisory Details (4)

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

ima: verify the previous kernel's IMA buffer lies in addressable RAM - kernel/git/stable/linux.git - Linux kernel stable tree

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

ima: verify the previous kernel's IMA buffer lies in addressable RAM - kernel/git/stable/linux.git - Linux kernel stable tree

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

ima: verify the previous kernel's IMA buffer lies in addressable RAM - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5366ec7d2f793ce703c403d7fd4c25a3db365b9d
generic

ima: verify the previous kernel's IMA buffer lies in addressable RAM - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10d1c75ed4382a8e79874379caa2ead8952734f9

Vendor Advisories for CVE-2026-43129(2)

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

Patch Availability(15)

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 ... 7.2~rc5-1~exp1 (335 versions)
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

All Vendor Advisories

(14)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-43129?
CVE-2026-43129 is a medium vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: ima: verify the previous kernel's IMA buffer lies in addressable RAM Patch series "Address page fault in imarestoremeasurement_list()", v3. When the second-stage kernel is booted via kexec with a limiting command line such as…
When was CVE-2026-43129 disclosed?
CVE-2026-43129 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43129 actively exploited?
CVE-2026-43129 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-43129?
CVE-2026-43129 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43129?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43129, 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-43129

Explore →

Is Your Infrastructure Affected by CVE-2026-43129?

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