From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98513: drm/nouveau: Fix runtime PM leak in nouveau_connector_detect()
Date: Sun, 18 Oct 2026 17:16:17 +0200 [thread overview]
Message-ID: <2026101820-CVE-2026-98513-d60e@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/nouveau: Fix runtime PM leak in nouveau_connector_detect()
If nvif_outp_edid_get() fails, nouveau_connector_detect() returns
early without dropping the runtime PM reference taken at the start
of the function, keeping the device powered on until the next
successful detect.
Balance the reference on the error path like the other exit paths
do.
The Linux kernel CVE team has assigned CVE-2026-98513 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.7 with commit 0cd7e07181390085742bf623d6af3eef215c0503 and fixed in 6.12.112 with commit 87c2f8ce1100ccbbc40bfab067741edbd1f0ef02
Issue introduced in 6.7 with commit 0cd7e07181390085742bf623d6af3eef215c0503 and fixed in 6.18.55 with commit 59aa1f8c95941e623891d46c805e8fb1257b5a3d
Issue introduced in 6.7 with commit 0cd7e07181390085742bf623d6af3eef215c0503 and fixed in 7.2.9 with commit 780ad8e4df9f767806587d33b42372acf8fbe5e6
Issue introduced in 6.7 with commit 0cd7e07181390085742bf623d6af3eef215c0503 and fixed in 7.3-rc5 with commit 1e04611d3735543bd80a67d9d13dc13f503746fb
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-98513
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/nouveau/nouveau_connector.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/87c2f8ce1100ccbbc40bfab067741edbd1f0ef02
https://git.kernel.org/stable/c/59aa1f8c95941e623891d46c805e8fb1257b5a3d
https://git.kernel.org/stable/c/780ad8e4df9f767806587d33b42372acf8fbe5e6
https://git.kernel.org/stable/c/1e04611d3735543bd80a67d9d13dc13f503746fb
reply other threads:[~2026-10-18 15:24 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=2026101820-CVE-2026-98513-d60e@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.