nouveau/dmem: Fix vulnerability in migrate_to_ram upon copy error
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5be73b690875f7eb2d2defb54ccd7f2f12074984 · < ab4d113b6718b076046018292f821d5aa4b844f8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nouveau/dmem: Fix vulnerability in migrate_to_ram upon copy error
The `nouveau_dmem_copy_one` function ensures that the copy push command is sent to the device firmware but does not track whether it was executed successfully.
In the case of a copy error (e.g., firmware or hardware failure), the copy push command will be sent via the firmware channel, and `nouveau_dmem_copy_one` will likely report success, leading to the `migrate_to_ram` function returning a dirty HIGH_USER page to the user.
This can result in a security vulnerability, as a HIGH_USER page that may contain sensitive or corrupted data could be returned to the user.
To prevent this vulnerability, we allocate a zero page. Thus, in case of an error, a non-dirty (zero) page will be returned to the user.
From the CVE record · Linux
The Linux kernel's nouveau/dmem copy function can report success even when a device copy fails. If a firmware or hardware copy error occurs, migrate_to_ram may return a dirty HIGH_USER page containing sensitive or corrupted data to a user.
Anyone running the Linux kernel with nouveau/dmem should check whether their kernel includes the fix; affected versions were not specified.