Answer in brief
CVE-2026-64244 records a Unknown severity vulnerability in drivers/base/memory: set mem->altmap after successful device registration. The current sources do not mark it as known exploited. The current feed maps 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.
Answer in brief
CVE-2026-64244 records a Unknown severity vulnerability in drivers/base/memory: set mem->altmap after successful device registration. The current sources do not mark it as known exploited. The current feed maps 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.
A CVSS score is not reported in the current record. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1a8c64e110435e44e71bcd50a75663174b575f22 <802e113cf120df7208e4c7e604950a85e87120a8 || >=1a8c64e110435e44e71bcd50a75663174b575f22 <22dc0d042f02ce82aa61422ea5f232628bfd9e9c || >=1a8c64e110435e44e71bcd50a75663174b575f22 <6c25bf4e44a2b6a14332f952bba0974521f5b72d || >=1a8c64e110435e44e71bcd50a75663174b575f22 <bc3dd82a0ffd488bb902f4c69c3d28fd4088d973 || >=1a8c64e110435e44e71bcd50a75663174b575f22 <059ac6252a63edf1cea79bf30bd860a8c264b62c || >=1a8c64e110435e44e71bcd50a75663174b575f22 <a2b8d7827f48ee54a686cb80e4a1d0ff954ec42a | 802e113cf120df7208e4c7e604950a85e87120a8, 22dc0d042f02ce82aa61422ea5f232628bfd9e9c, 6c25bf4e44a2b6a14332f952bba0974521f5b72d, bc3dd82a0ffd488bb902f4c69c3d28fd4088d973, 059ac6252a63edf1cea79bf30bd860a8c264b62c, a2b8d7827f48ee54a686cb80e4a1d0ff954ec42a |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Jul 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
In the Linux kernel, the following vulnerability has been resolved: drivers/base/memory: set mem->altmap after successful device registration If __add_memory_block() fails at xa_store() (under memory pressure for example), device_unregister() is called, which eventually triggers memory_block_release() with mem->altmap still set, causing a WARN_ON(mem->altmap). This was triggered by modifying virtio-mem driver. Fix this by delaying the assignment of mem->altmap until after __add_memory_block() has succeeded.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1a8c64e110435e44e71bcd50a75663174b575f22 <802e113cf120df7208e4c7e604950a85e87120a8 || >=1a8c64e110435e44e71bcd50a75663174b575f22 <22dc0d042f02ce82aa61422ea5f232628bfd9e9c || >=1a8c64e110435e44e71bcd50a75663174b575f22 <6c25bf4e44a2b6a14332f952bba0974521f5b72d || >=1a8c64e110435e44e71bcd50a75663174b575f22 <bc3dd82a0ffd488bb902f4c69c3d28fd4088d973 || >=1a8c64e110435e44e71bcd50a75663174b575f22 <059ac6252a63edf1cea79bf30bd860a8c264b62c || >=1a8c64e110435e44e71bcd50a75663174b575f22 <a2b8d7827f48ee54a686cb80e4a1d0ff954ec42a | 802e113cf120df7208e4c7e604950a85e87120a8, 22dc0d042f02ce82aa61422ea5f232628bfd9e9c, 6c25bf4e44a2b6a14332f952bba0974521f5b72d, bc3dd82a0ffd488bb902f4c69c3d28fd4088d973, 059ac6252a63edf1cea79bf30bd860a8c264b62c, a2b8d7827f48ee54a686cb80e4a1d0ff954ec42a |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Jul 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
In the Linux kernel, the following vulnerability has been resolved: drivers/base/memory: set mem->altmap after successful device registration If __add_memory_block() fails at xa_store() (under memory pressure for example), device_unregister() is called, which eventually triggers memory_block_release() with mem->altmap still set, causing a WARN_ON(mem->altmap). This was triggered by modifying virtio-mem driver. Fix this by delaying the assignment of mem->altmap until after __add_memory_block() has succeeded.
Quoted source text, attributed separately from HOL analysis.