drm/nouveau: fix a use-after-free in r535_gsp_rpc_push()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.1146.15.46.16In the Linux kernel, the following vulnerability has been resolved:
drm/nouveau: fix a use-after-free in r535_gsp_rpc_push()
The RPC container is released after being passed to r535_gsp_rpc_send().
When sending the initial fragment of a large RPC and passing the caller's RPC container, the container will be freed prematurely. Subsequent attempts to send remaining fragments will therefore result in a use-after-free.
Allocate a temporary RPC container for holding the initial fragment of a large RPC when sending. Free the caller's container when all fragments are successfully sent.
[ Rebase onto Blackwell changes. - Danilo ]
From the CVE record · Linux
The Linux kernel's nouveau driver can free an RPC container prematurely when sending the initial fragment of a large RPC. Sending subsequent fragments then causes a use-after-free. The input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels with the nouveau driver should check their deployments; affected versions are not specified.