Answer in brief
CVE-2025-40336 records a High severity (CVSS 8.8) vulnerability in drm/gpusvm: fix hmm_pfn_to_map_order() usage. 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.
CVSS is 8.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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=99624bdff8670795b678eafa6509aaad3a5c0175 <08e9fd78ba1b9e95141181c69cc51795c9888157 || >=99624bdff8670795b678eafa6509aaad3a5c0175 <c50729c68aaf93611c855752b00e49ce1fdd1558 | 08e9fd78ba1b9e95141181c69cc51795c9888157, c50729c68aaf93611c855752b00e49ce1fdd1558 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Dec 9, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/gpusvm: fix hmm_pfn_to_map_order() usage Handle the case where the hmm range partially covers a huge page (like 2M), otherwise we can potentially end up doing something nasty like mapping memory which is outside the range, and maybe not even mapped by the mm. Fix is based on the xe userptr code, which in a future patch will directly use gpusvm, so needs alignment here. v2: - Add kernel-doc (Matt B) - s/fls/ilog2/ (Thomas)
Quoted source text, attributed separately from HOL analysis.