drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.57, 7.0.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure When ttm_tt_swapout() fails, the current code calls ttm_resource_add_bulk_move() followed by ttm_resource_move_to_lru_tail() to restore the resource's bulk_move membership. However, ttm_resource_move_to_lru_tail() places the resource at the tail of the LRU list which, relative to the walk cursor's hitch node (placed immediately after the resource when it was yielded), puts the resource in front of the the hitch. The next list_for_each_entry_continue() from the hitch finds the same resource again, causing an infinite loop. Fix by deferring del_bulk_move to the success path only. On the success path, TTM_TT_FLAG_SWAPPED has just been set by ttm_tt_swapout() but the resource is still tracked in the bulk_move range, so ttm_resource_del_bulk_move()'s !ttm_resource_unevictable() guard would incorrectly skip the removal. Introduce ttm_resource_del_bulk_move_unevictable() which bypasses that guard.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From fc5d96670eb2540d2572a14351e82ffe45d5ac11 · fixed in 060f8f3020516d71bc4d6159d4d0beef85606a74; From fc5d96670eb2540d2572a14351e82ffe45d5ac11 · fixed in 0124a09e3e5f5f6080efe9663b27af27933f8382; From fc5d96670eb2540d2572a14351e82ffe45d5ac11 · fixed in b2ed01e7ad3de80333e9b962a44024b094bc0b2b
- Linux Linux
6.13
- KernelLinux
From 6.13.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.0.10