drm/nouveau/dmem: pin VRAM for the whole registered range
- 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 7.2.9
- 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
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/dmem: pin VRAM for the whole registered range Commit c32287471077 ("gpu/drm/nouveau: enable THP support for GPU memory migration") grew the device-private region that nouveau_dmem_chunk_alloc() registers from DMEM_CHUNK_SIZE to DMEM_CHUNK_SIZE * NR_CHUNKS, but left the VRAM buffer object backing that region at DMEM_CHUNK_SIZE. nouveau_dmem_page_addr() returns chunk->bo->offset plus the page's offset within the registered region, so every page past the first chunk resolves to VRAM outside the buffer object. Size the buffer object to the region it backs.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From c3228747107705d47c7e9a03598a434a0380cb73 · fixed in 06c69c64686a31783c8bec6495dc22822d38c4ce; From c3228747107705d47c7e9a03598a434a0380cb73 · fixed in 64ca4cdd1031206424e6455f0ae4fb0560d8f46a
- Linux Linux
6.19
- KernelLinux
From 6.19.0 · fixed in 7.2.9