CVE-2025-21872: Linux kernel · efi: Don't map the entire mokvar table to determine its size
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 6.8.0-1039.41~22.04.1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.8.0-1039.41~22.04.1, 6.8.0-1036.42~22.04.1, 6.8.0-1040.42~22.04.1 +33
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux@6.8.0-84.84?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws@6.8.0-1039.41?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure@6.8.0-1038.44?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11@6.11.0-1015.15~24.04.1?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia@6.8.0-1025.27?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp@6.8.0-1040.42?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: efi: Don't map the entire mokvar table to determine its size Currently, when validating the mokvar table, we (re)map the entire table on each iteration of the loop, adding space as we discover new entries. If the table grows over a certain size, this fails due to limitations of early_memmap(), and we get a failure and traceback: ------------[ cut here ]------------ WARNING: CPU: 0 PID: 0 at mm/early_ioremap.c:139 __early_ioremap+0xef/0x220 ... Call Trace: <TASK> ? __early_ioremap+0xef/0x220 ? __warn.cold+0x93/0xfa ? __early_ioremap+0xef/0x220 ? report_bug+0xff/0x140 ? early_fixup_exception+0x5d/0xb0 ? early_idt_handler_common+0x2f/0x3a ? __early_ioremap+0xef/0x220 ? efi_mokvar_table_init+0xce/0x1d0 ? setup_arch+0x864/0xc10 ? start_kernel+0x6b/0xa10 ? x86_64_start_reservations+0x24/0x30 ? x86_64_start_kernel+0xed/0xf0 ? common_startup_64+0x13e/0x141 </TASK> ---[ end trace 0000000000000000 ]--- mokvar: Failed to map EFI MOKvar config table pa=0x7c4c3000, size=265187. Mapping the entire structure isn't actually necessary, as we don't ever need more than one entry header mapped at once. Changes efi_mokvar_table_init() to only map each entry header, not the entire table, when determining the table size. Since we're not mapping any data past the variable name, it also changes the code to enforce that each variable name is NUL terminated, rather than attempting to verify it in place.
References
- ubuntu.com/security/CVE-2025-21872 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2025-21872 (opens in a new tab)
- git.kernel.org/linus/2b90e7ace79774a3540ce569e000388f8d22c9e0 (opens in a new tab)
- git.kernel.org/stable/c/2b90e7ace79774a3540ce569e000388f8d22c9e0 (opens in a new tab)
- git.kernel.org/stable/c/46c0454ffb78ce9d3355a3cccac86383ea8ddd55 (opens in a new tab)
- git.kernel.org/stable/c/65f4aebb8127708ba668dd938e83b8558abfc5cd (opens in a new tab)
- git.kernel.org/stable/c/97bd560b6cc4c26386a53b4881bf03e96f9ba03a (opens in a new tab)
- git.kernel.org/stable/c/ea3f0b362dfe4ef885ef812bfaf4088176422c91 (opens in a new tab)
- ubuntu.com/security/notices/USN-7521-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7521-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7521-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7764-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7765-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7766-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7767-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7779-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7767-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7764-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7790-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7800-1 (opens in a new tab)