drm/gpusvm: fix hmm_pfn_to_map_order() usage
- 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.17.8
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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)
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 99624bdff8670795b678eafa6509aaad3a5c0175 · fixed in 08e9fd78ba1b9e95141181c69cc51795c9888157; From 99624bdff8670795b678eafa6509aaad3a5c0175 · fixed in c50729c68aaf93611c855752b00e49ce1fdd1558
- Linux Linux
6.15
- KernelLinux
From 6.15.0 · fixed in 6.17.8