From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98697: USB: serial: fix dynamic id driver deregistration race
Date: Sun, 18 Oct 2026 17:44:32 +0200 [thread overview]
Message-ID: <2026101804-CVE-2026-98697-3afc@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
USB: serial: fix dynamic id driver deregistration race
Only free the dynamic ids after having deregistered the driver and
removed the "new_id" attribute to avoid leaking any id added by a racing
write to the attribute.
The Linux kernel CVE team has assigned CVE-2026-98697 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.21 with commit 93bacefc4cc0b53e1cb6a336d43847154fdf6886 and fixed in 6.12.113 with commit ebd8fcaaacb66c15ae7e19d14619abe3762e0701
Issue introduced in 2.6.21 with commit 93bacefc4cc0b53e1cb6a336d43847154fdf6886 and fixed in 6.18.56 with commit 4d6da6867b4ac6468d634a0dd3c35dfc0dc8af81
Issue introduced in 2.6.21 with commit 93bacefc4cc0b53e1cb6a336d43847154fdf6886 and fixed in 7.2.10 with commit 380f57cd58e26e0f3687451196ec446c473c52d9
Issue introduced in 2.6.21 with commit 93bacefc4cc0b53e1cb6a336d43847154fdf6886 and fixed in 7.3-rc6 with commit 63594e8ffe097bc0b7639936f33799a7653dded2
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-98697
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/usb/serial/bus.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/ebd8fcaaacb66c15ae7e19d14619abe3762e0701
https://git.kernel.org/stable/c/4d6da6867b4ac6468d634a0dd3c35dfc0dc8af81
https://git.kernel.org/stable/c/380f57cd58e26e0f3687451196ec446c473c52d9
https://git.kernel.org/stable/c/63594e8ffe097bc0b7639936f33799a7653dded2
reply other threads:[~2026-10-18 15:52 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=2026101804-CVE-2026-98697-3afc@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.