drm/ttm: fix bulk_move corruption when adding a entry
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.1.426.4.76.5In the Linux kernel, the following vulnerability has been resolved:
drm/ttm: fix bulk_move corruption when adding a entry
When the resource is the first in the bulk_move range, adding it again (thus moving it to the tail) will corrupt the list since the first pointer is not moved. This eventually lead to null pointer deref in ttm_lru_bulk_move_del()
From the CVE record · Linux
The Linux kernel’s drm/ttm bulk_move list can become corrupted when the first resource in the range is added again. This can eventually cause a null pointer dereference in ttm_lru_bulk_move_del(). The input does not establish whether an attacker can trigger it or what access or interaction would be required.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.