mm/damon/vaddr: do not repeat pte_offset_map_lock() until success
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
DAMON's virtual address monitoring can retry a page-table walk indefinitely when a page-table entry remains a migration entry. A soft lockup occurred when CPU hotplugging and DAMON ran in parallel. The input does not describe an attacker-controlled trigger, authentication requirement, or user interaction.
Engineers running the Linux kernel with DAMON virtual address monitoring should check their kernel; affected versions are not specified.