CVE-2026-43129: ima: verify the previous kernel's IMA buffer lies in addressable RAM
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 10d1c75ed4382a8e79874379caa2ead8952734f9, 43308106a1762b72f3b20a44b75b2df5cb25b77b, 5366ec7d2f793ce703c403d7fd4c25a3db365b9d.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 10d1c75ed4382a8e79874379caa2ead8952734f9, 43308106a1762b72f3b20a44b75b2df5cb25b77b, 5366ec7d2f793ce703c403d7fd4c25a3db365b9d or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- May 6, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.0 and later · before 6.12.77
- linux linux kernel6.13 and later · before 6.18.16
- linux linux kernel6.19 and later · before 6.19.6
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.0affected
- b69a2afd5afce9bf6d56e349d6ab592c916e20f2 and later · before 5bfa1941ec40d5bed68f3e3f22ea13aff9c6d67aaffected · git
- b69a2afd5afce9bf6d56e349d6ab592c916e20f2 and later · before 43308106a1762b72f3b20a44b75b2df5cb25b77baffected · git
- b69a2afd5afce9bf6d56e349d6ab592c916e20f2 and later · before f11d7d088f5ed54b31c6735854c12845eb60eb4aaffected · git
- b69a2afd5afce9bf6d56e349d6ab592c916e20f2 and later · before 9e1f51c1ad57cc76a0e8b5eb27038f8973fff4faaffected · git
- b69a2afd5afce9bf6d56e349d6ab592c916e20f2 and later · before 5366ec7d2f793ce703c403d7fd4c25a3db365b9daffected · git
- b69a2afd5afce9bf6d56e349d6ab592c916e20f2 and later · before 10d1c75ed4382a8e79874379caa2ead8952734f9affected · git
- before 6.0not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.143 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.6-1 | 6.19.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43127May 6, 2026 · ntfs3: fix circular locking dependency in run_unpack_ex22Monitor
- ← EarlierCVE-2026-43128May 6, 2026 · RDMA/umem: Fix double dma_buf_unpin in failure path31Monitor
- Later →CVE-2026-43133May 6, 2026 · KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 10d1c75ed4382a8e79874379caa2ead8952734f9 | Vendor (CNA) |
| Linux Linux | 43308106a1762b72f3b20a44b75b2df5cb25b77b | Vendor (CNA) |
| Linux Linux | 5366ec7d2f793ce703c403d7fd4c25a3db365b9d | Vendor (CNA) |
| Linux Linux | 5bfa1941ec40d5bed68f3e3f22ea13aff9c6d67a | Vendor (CNA) |
| Linux Linux | 9e1f51c1ad57cc76a0e8b5eb27038f8973fff4fa | Vendor (CNA) |
| Linux Linux | f11d7d088f5ed54b31c6735854c12845eb60eb4a | Vendor (CNA) |
| debian:linux | 6.12.85-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0196 · May 8, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/43308106a1762b72f3b20a44b75b2df5cb25b77b
- git.kernel.org/stable/c/5366ec7d2f793ce703c403d7fd4c25a3db365b9d
- git.kernel.org/stable/c/5bfa1941ec40d5bed68f3e3f22ea13aff9c6d67a
- git.kernel.org/stable/c/9e1f51c1ad57cc76a0e8b5eb27038f8973fff4fa
- git.kernel.org/stable/c/f11d7d088f5ed54b31c6735854c12845eb60eb4a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.