CVE-2026-43404

published 8 May 2026 · updated 13 Nov 2026

mm: Fix a hmm_range_fault() livelock / starvation problem

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.18.19, Kernel 6.19.9, Kernel 94b6d0ba4b640ba23bb6c708a59316e74e5ede63 and 2 more.

In the Linux kernel, the following vulnerability has been resolved: mm: Fix a hmm_range_fault() livelock / starvation problem If hmm_range_fault() fails a folio_trylock() in do_swap_page, trying to acquire the lock of a device-private folio for migration, to ram, the function will spin until it succeeds grabbing the lock. However, if the process holding the lock is depending on a work item to be completed, which is scheduled on the same CPU as the spinning hmm_range_fault(), that work item might be starved and we end up in a livelock / starvation situation which is never resolved. This can happen, for example if the process holding the device-private folio lock is stuck in migrate_device_unmap()->lru_add_drain_all() sinc lru_add_drain_all() requires a short work-item to be run on all online cpus to complete. A prerequisite for this to happen is: a) Both zone device and system memory folios are considered in migrate_device_unmap(), so that there is a reason to call lru_add_drain_all() for a system memory folio while a folio lock is held on a zone device folio. b) The zone device folio has an initial mapcount > 1 which causes at least one migration PTE entry insertion to be deferred to try_to_migrate(), which can happen after the call to lru_add_drain_all(). c) No or voluntary only preemption. This all seems pretty unlikely to happen, but indeed is hit by the "xe_exec_system_allocator" igt test. Resolve this by waiting for the folio to be unlocked if the folio_trylock() fails in do_swap_page(). Rename migration_entry_wait_on_locked() to softleaf_entry_wait_unlock() and update its documentation to indicate the new use-case. Future code improvements might consider moving the lru_add_drain_all() call in migrate_device_unmap() to be called *after* all pages have migration entries inserted. That would eliminate also b) above. v2: - Instead of a cond_resched() in hmm_range_fault(), eliminate the problem by waiting for the folio to be unlocked in do_swap_page() (Alistair Popple, Andrew Morton) v3: - Add a stub migration_entry_wait_on_locked() for the !CONFIG_MIGRATION case. (Kernel Test Robot) v4: - Rename migrate_entry_wait_on_locked() to softleaf_entry_wait_on_locked() and update docs (Alistair Popple) v5: - Add a WARN_ON_ONCE() for the !CONFIG_MIGRATION version of softleaf_entry_wait_on_locked(). - Modify wording around function names in the commit message (Andrew Morton) (cherry picked from commit a69d1ab971a624c6f112cea61536569d579c3215)

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=6.15 <6.18.19, >=6.19 <6.19.9, =7.0, >=1afaeb8293c9addbf4f9140bdd22635fed763459 <94b6d0ba4b640ba23bb6c708a59316e74e5ede63, >=1afaeb8293c9addbf4f9140bdd22635fed763459 <b570f37a2ce480be26c665345c5514686a8a0274, =6.15, >=1afaeb8293c9addbf4f9140bdd22635fed763459 <7e6e2fc91d4b9b12ec6e137019532568ebcf26806.18.19, 6.19.9, 94b6d0ba4b640ba23bb6c708a59316e74e5ede63, b570f37a2ce480be26c665345c5514686a8a0274, 7e6e2fc91d4b9b12ec6e137019532568ebcf2680
linux-kernel: Kernel>=6.15.0 <6.18.19, >=6.19.0 <6.19.96.18.19, 6.19.9

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-43404 severity on Zeptric[![CVE-2026-43404](https://zeptric.io/badge/cve/CVE-2026-43404.svg)](https://zeptric.io/cve/CVE-2026-43404)