mm/damon/vaddr: do not repeat pte_offset_map_lock() until success
CVE-2025-40218 is fixed in 36 products on 1 platform, first by DEBIAN-CVE-2025-40218, released December 4, 2025. It is not reported as exploited. Patch Radar priority: Routine.
In the Linux kernel, the following vulnerability has been resolved: mm/damon/vaddr: do not repeat pte_offset_map_lock() until success DAMON's virtual address space operation set implementation (vaddr) calls pte_offset_map_lock() inside the page table walk callback function. This is for reading and writing page table accessed bits. If pte_offset_map_lock() fails, it retries by returning the page table walk callback function with ACTION_AGAIN. pte_offset_map_lock() can continuously fail if the target is a pmd migration entry, though. Hence it could cause an infinite page table walk if the migration cannot be done until the page table walk is finished. This indeed caused a soft lockup when CPU hotplugging and DAMON were running in parallel. Avoid the infinite loop by simply not retrying the page table walk. DAMON is promising only a best-effort accuracy, so missing access to such pages is no problem.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool6.12 · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| bpftool6.12-debuginfo · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| dtb-aarch64 · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-64kb · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-64kb · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-azure · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-azure · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-default · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-default · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-default-base · opensuse-leap 16.0 | 6.12.0-160000.9.1.160000.2.6 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-default-base · sles 16.0 | 6.12.0-160000.9.1.160000.2.6 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-docs · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-docs · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-kvmsmall · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-kvmsmall · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-livepatch-6.12.55-74.119 · amzn 2023 | 1:1.0-0.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel-obs-build · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-obs-qa · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-obs-qa · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-rt · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-source · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-source · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-syms · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-syms · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-zfcpdump · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-zfcpdump · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel6.12 · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel6.12-debuginfo · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel6.12-debuginfo-common-aarch64 · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel6.12-debuginfo-common-x86_64 · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel6.12-devel · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel6.12-headers · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel6.12-libbpf · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel6.12-libbpf-debuginfo · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel6.12-libbpf-devel · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel6.12-libbpf-static · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel6.12-modules-extra · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel6.12-modules-extra-common · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel6.12-tools · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel6.12-tools-debuginfo · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| kernel6.12-tools-devel · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| linux · Debian 13.5 (trixie) | 6.12.57-1 | DEBIAN-CVE-2025-40218 | Dec 4, 2025 |
| linux · Debian 14 | 6.17.6-1 | DEBIAN-CVE-2025-40218 | Dec 4, 2025 |
| perf6.12 · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| perf6.12-debuginfo · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| python3-perf6.12 · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
| python3-perf6.12-debuginfo · amzn 2023 | 1:6.12.55-74.119.amzn2023 | ALAS2023-2025-1316 | Dec 8, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.