From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98319: drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr
Date: Tue, 6 Oct 2026 10:47:00 +0200 [thread overview]
Message-ID: <2026100613-CVE-2026-98319-053d@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr
When an out_fence_ptr is provided but DRM_MODE_PAGE_FLIP_EVENT is not
set, a drm_pending_vblank_event will be allocated. If later, there is an
allocation failure or another failure at setup_out_fence(), that event
will not have base.fence set and it will not be released at
complete_signaling().
Release the event and set crtc_state->event to NULL just like in the
DRM_MODE_PAGE_FLIP_EVENT case when there is a failure at
drm_event_reserve_init(). That is, prepare_signaling() releases the
event and there is nothing to be done at complete_signaling(). Use
drm_event_cancel_free() as that will also undo drm_event_reserve_init()
in case it has been called.
The Linux kernel CVE team has assigned CVE-2026-98319 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.10 with commit 92c715fca907686f5298220ece53423e38ba3aed and fixed in 5.10.271 with commit 3d6576ed3de01e8a378397b7020e33ae3d40aa6c
Issue introduced in 4.10 with commit 92c715fca907686f5298220ece53423e38ba3aed and fixed in 5.15.222 with commit 86c33f740aa27e9cdc1259f0cc59c9c58f545e4b
Issue introduced in 4.10 with commit 92c715fca907686f5298220ece53423e38ba3aed and fixed in 6.1.189 with commit 88c450e23b8fd4f1dcd329562f5e81ef05f3d941
Issue introduced in 4.10 with commit 92c715fca907686f5298220ece53423e38ba3aed and fixed in 6.6.158 with commit 780716e2e019186fa6e5aad097a44b87b0b5388f
Issue introduced in 4.10 with commit 92c715fca907686f5298220ece53423e38ba3aed and fixed in 6.12.112 with commit d0be0516b5224eb5b6f42f8564a8deadb20ae16b
Issue introduced in 4.10 with commit 92c715fca907686f5298220ece53423e38ba3aed and fixed in 6.18.54 with commit daefd7ff159b0d1fb8c9e64430dcbe2aca1bdd09
Issue introduced in 4.10 with commit 92c715fca907686f5298220ece53423e38ba3aed and fixed in 7.2.8 with commit b9a68a9ccaada15d8dd0102c188cc6b868ff800b
Issue introduced in 4.10 with commit 92c715fca907686f5298220ece53423e38ba3aed and fixed in 7.3-rc4 with commit 9eb1a393c89a79c4210230d23e7d88d239c61d7b
Issue introduced in 4.9.10 with commit 4cd462c7f2b6fcc208aebf44f2c831681feaa925
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-98319
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/drm_atomic_uapi.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/3d6576ed3de01e8a378397b7020e33ae3d40aa6c
https://git.kernel.org/stable/c/86c33f740aa27e9cdc1259f0cc59c9c58f545e4b
https://git.kernel.org/stable/c/88c450e23b8fd4f1dcd329562f5e81ef05f3d941
https://git.kernel.org/stable/c/780716e2e019186fa6e5aad097a44b87b0b5388f
https://git.kernel.org/stable/c/d0be0516b5224eb5b6f42f8564a8deadb20ae16b
https://git.kernel.org/stable/c/daefd7ff159b0d1fb8c9e64430dcbe2aca1bdd09
https://git.kernel.org/stable/c/b9a68a9ccaada15d8dd0102c188cc6b868ff800b
https://git.kernel.org/stable/c/9eb1a393c89a79c4210230d23e7d88d239c61d7b
reply other threads:[~2026-10-06 10:27 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=2026100613-CVE-2026-98319-053d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.