drm/i915/gt: Cleanup partial engine discovery failures
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/i915/gt: Cleanup partial engine discovery failures
If we abort driver initialisation in the middle of gt/engine discovery, some engines will be fully setup and some not. Those incompletely setup engines only have 'engine->release == NULL' and so will leak any of the common objects allocated.
v2: - Drop the destroy_pinned_context() helper for now. It's not really worth it with just a single callsite at the moment. (Janusz)
From the CVE record · Linux
The Linux kernel's drm/i915/gt driver can leak allocated objects if initialization stops partway through engine discovery. Some engines are then only partially set up and cannot release those objects. The input does not specify an attacker action, access requirement, or user interaction.
Engineers running Linux kernels with the drm/i915/gt driver should check whether their kernel is affected; affected versions are not specified.