CVE-2026-80903

drm/xe/oa: Fix sync entry leak on OA config emit failure

N/A
Published: September 4, 2026 at 05:19 PM UTC
Updated: September 4, 2026 at 06:36 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: drm/xe/oa: Fix sync entry leak on OA config emit failure xe_oa_emit_oa_config() releases the sync entries and the syncs array only on its success path. When it fails before the point of no return (fence allocation, config buffer allocation or batch submission), it returns without touching stream->syncs. The stream open path handles such failures in the caller, but xe_oa_config_locked() propagates the error without any cleanup, so the syncs array and the fence references held by the parsed entries are leaked. The next config ioctl overwrites stream->syncs, making the memory unreachable for good. Clean up the parsed syncs when xe_oa_emit_oa_config() fails, matching the cleanup done by the stream open error path. (cherry picked from commit 8af97b3da2cfce04e6b457c6eb17ed3c1daf912b)

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.12.18 ≤ v < 6.12.1056.13 ≤ v < 6.18.466.13 ≤ v < 7.1.106.13 ≤ v < 7.26.12.186.139920c8b88c5cf2e44f4ff508dd3c0c96e4364db0f0ab9cd205d852a9024b73c71c8d8b217a04e8f0
Vendor states this is fixed in 027150e24e173a5dffe7f5ab3a6600618f634da2 (fixed)
Vendor states this is fixed in 8d33c4987cd162527375a3905017ae129ba7c3fe (fixed)
Vendor states this is fixed in 948f346fe36e1d02353c3d61b1f6b66c6af91996 (fixed)
Vendor states this is fixed in fcf7943b0a38568c547d7b5702de1d8190480616 (fixed)
Vendor states this is fixed in 6.12.105 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.18.46 (unaffected)
Vendor states this is fixed in 7.1.10 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card