CVE-2026-43129ima: verify the previous kernel's IMA buffer lies in addressable RAM
- 5.5MediumCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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=<size>" 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=<size>"), 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().
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 6 months later
· 6 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected b69a2afd5afce9bf6d56e349d6ab592c916e20f2 – < 5bfa1941ec40d5bed68f3e3f22ea13aff9c6d67a
- affected b69a2afd5afce9bf6d56e349d6ab592c916e20f2 – < 43308106a1762b72f3b20a44b75b2df5cb25b77b
- affected b69a2afd5afce9bf6d56e349d6ab592c916e20f2 – < f11d7d088f5ed54b31c6735854c12845eb60eb4a
- affected b69a2afd5afce9bf6d56e349d6ab592c916e20f2 – < 9e1f51c1ad57cc76a0e8b5eb27038f8973fff4fa
- affected b69a2afd5afce9bf6d56e349d6ab592c916e20f2 – < 5366ec7d2f793ce703c403d7fd4c25a3db365b9d
- affected b69a2afd5afce9bf6d56e349d6ab592c916e20f2 – < 10d1c75ed4382a8e79874379caa2ead8952734f9
- affected 6.0
- unaffected < 6.0
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.143 – ≤ 6.6.*
- unaffected 6.12.77 – ≤ 6.12.*
- unaffected 6.18.16 – ≤ 6.18.*
- unaffected 6.19.6 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References6
- https://git.kernel.org/stable/c/5bfa1941ec40d5bed68f3e3f22ea13aff9c6d67a (opens in a new tab)
- https://git.kernel.org/stable/c/43308106a1762b72f3b20a44b75b2df5cb25b77b (opens in a new tab)
- https://git.kernel.org/stable/c/f11d7d088f5ed54b31c6735854c12845eb60eb4a (opens in a new tab)
- https://git.kernel.org/stable/c/9e1f51c1ad57cc76a0e8b5eb27038f8973fff4fa (opens in a new tab)
- https://git.kernel.org/stable/c/5366ec7d2f793ce703c403d7fd4c25a3db365b9d (opens in a new tab)
- https://git.kernel.org/stable/c/10d1c75ed4382a8e79874379caa2ead8952734f9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-27690 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-43129)Record last updated .