CVE-2025-40218

mm/damon/vaddr: do not repeat pte_offset_map_lock() until success

N/A
Published: December 4, 2025 at 02:50 PM UTC
Updated: October 19, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.57780d04046a2288ab85d88bedacc60fa4fad9971
Vendor states this is fixed in 0ccd91cf749536d41307a07e60ec14ab0dbf21f5 (fixed)
Vendor states this is fixed in 677ebfe5d00f94adec0c0204f6e6e2a82d3f77bf (fixed)
Vendor states this is fixed in ac42320ec873bfe726141069cfdd90ee5bc4e885 (fixed)
Vendor states this is fixed in b93af2cc8e036754c0d9970d9ddc47f43cc94b9f (fixed)
Vendor states this is fixed in 6.12.54 (unaffected)
Vendor states this is fixed in 6.17.4 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.5 (unaffected)
Vendor states this is fixed in 6.6.113 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card