Answer in brief
CVE-2026-89755 records a High severity (CVSS 7.8) vulnerability in mm/migrate_device: clear stale mapping after freeing swapcache. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=df263d9a7dffee94ca5391120ee3b0587efa07f1 <8ffedc6573a665cdc31ebe47eae7b32b78d0df83 || >=df263d9a7dffee94ca5391120ee3b0587efa07f1 <34a00895d032a414830d41106a09329ae6c251b6 | 8ffedc6573a665cdc31ebe47eae7b32b78d0df83, 34a00895d032a414830d41106a09329ae6c251b6 |
| Linux/Linuxgeneric | 6.6 | Not reported |
| Linux/Linuxgeneric | >=df263d9a7dffee94ca5391120ee3b0587efa07f1 <4fa91f7bbc4135240b67daac03fc17d9e180a331 || >=df263d9a7dffee94ca5391120ee3b0587efa07f1 <8ffedc6573a665cdc31ebe47eae7b32b78d0df83 || >=df263d9a7dffee94ca5391120ee3b0587efa07f1 <34a00895d032a414830d41106a09329ae6c251b6 | 4fa91f7bbc4135240b67daac03fc17d9e180a331, 8ffedc6573a665cdc31ebe47eae7b32b78d0df83, 34a00895d032a414830d41106a09329ae6c251b6 |
| Linux/Linuxgeneric | >=df263d9a7dffee94ca5391120ee3b0587efa07f1 <92db780dd644590c751246187e1229d5ac2e5544 || >=df263d9a7dffee94ca5391120ee3b0587efa07f1 <4fa91f7bbc4135240b67daac03fc17d9e180a331 || >=df263d9a7dffee94ca5391120ee3b0587efa07f1 <8ffedc6573a665cdc31ebe47eae7b32b78d0df83 || >=df263d9a7dffee94ca5391120ee3b0587efa07f1 <34a00895d032a414830d41106a09329ae6c251b6 | 92db780dd644590c751246187e1229d5ac2e5544, 4fa91f7bbc4135240b67daac03fc17d9e180a331, 8ffedc6573a665cdc31ebe47eae7b32b78d0df83, 34a00895d032a414830d41106a09329ae6c251b6 |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: mm/migrate_device: clear stale mapping after freeing swapcache __migrate_device_pages() reads the folio mapping before calling folio_free_swap(). When folio_free_swap() succeeds, the folio is removed from the swap cache, but the saved mapping still points to swap_space. Passing the stale mapping to folio_migrate_mapping() makes it use the mapped-folio path for a folio that is no longer in swapcache. It can then operate on swap_space.i_pages with invalid reference accounting, eventually triggering a folio reference count BUG. After a successful split, nr still contains the number of pages in the original large folio, although each resulting page is now a separate order-0 folio. Reset nr to 1 so each split folio is processed separately, including its own swapcache removal and mapping lookup. Refresh the saved mapping after folio_free_swap() so the current folio state is used during migration.
Quoted source text, attributed separately from HOL analysis.