From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43396: drm/xe/sync: Fix user fence leak on alloc failure
Date: Fri, 8 May 2026 16:22:05 +0200 [thread overview]
Message-ID: <2026050838-CVE-2026-43396-a177@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/xe/sync: Fix user fence leak on alloc failure
When dma_fence_chain_alloc() fails, properly release the user fence
reference to prevent a memory leak.
(cherry picked from commit a5d5634cde48a9fcd68c8504aa07f89f175074a0)
The Linux kernel CVE team has assigned CVE-2026-43396 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.18 with commit 0995c2fc39b0f998d40f5d276f67ae22fc1c37c3 and fixed in 6.18.20 with commit 05edc78eb4699e8e000a62aaa8dace50a17e19e3
Issue introduced in 6.18 with commit 0995c2fc39b0f998d40f5d276f67ae22fc1c37c3 and fixed in 6.19.9 with commit f8f90b33934b307f6e4599b9fae38aa1ee5441a7
Issue introduced in 6.18 with commit 0995c2fc39b0f998d40f5d276f67ae22fc1c37c3 and fixed in 7.0 with commit 0879c3f04f67e2a1677c25dcc24669ce21eb6a6c
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-43396
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpu/drm/xe/xe_sync.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/05edc78eb4699e8e000a62aaa8dace50a17e19e3
https://git.kernel.org/stable/c/f8f90b33934b307f6e4599b9fae38aa1ee5441a7
https://git.kernel.org/stable/c/0879c3f04f67e2a1677c25dcc24669ce21eb6a6c
reply other threads:[~2026-05-08 14:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026050838-CVE-2026-43396-a177@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox