CVE-2025-21872
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 5.10.235
- Linux Kernel < 6.6.83
- Linux Kernel < 6.12.18
- Linux Kernel < 6.13.6
- Linux Kernel 6.14
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-21872.md and follow it. Check whether this project is affected by CVE-2025-21872. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/2b90e7ace79774a3540ce569e000388f8d22c9e0
- https://git.kernel.org/stable/c/46c0454ffb78ce9d3355a3cccac86383ea8ddd55
- https://git.kernel.org/stable/c/65f4aebb8127708ba668dd938e83b8558abfc5cd
- https://git.kernel.org/stable/c/97bd560b6cc4c26386a53b4881bf03e96f9ba03a
- https://git.kernel.org/stable/c/ea3f0b362dfe4ef885ef812bfaf4088176422c91
References
- https://git.kernel.org/stable/c/2b90e7ace79774a3540ce569e000388f8d22c9e0
- https://git.kernel.org/stable/c/46c0454ffb78ce9d3355a3cccac86383ea8ddd55
- https://git.kernel.org/stable/c/65f4aebb8127708ba668dd938e83b8558abfc5cd
- https://git.kernel.org/stable/c/97bd560b6cc4c26386a53b4881bf03e96f9ba03a
- https://git.kernel.org/stable/c/ea3f0b362dfe4ef885ef812bfaf4088176422c91
- https://git.kernel.org/stable/c/f17a72ac7dd6f9469c9e6185bdbb22dbb744dd74
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html