From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99776: net/9p/usbg: clear stale client pointer on close
Date: Fri, 20 Nov 2026 06:52:42 +0100 [thread overview]
Message-ID: <2026112030-CVE-2026-99776-6ffa@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net/9p/usbg: clear stale client pointer on close
p9_usbg_close() tears down the client transport, but usb9pfs keeps
using usb9pfs->client from asynchronous TX and RX completion handlers.
A late completion can therefore dereference a client that has already
been freed during mount teardown.
Clear usb9pfs->client under usb9pfs->lock when closing the transport,
detach any pending TX request from in_req->context, and make the TX/RX
completion handlers bail out once the transport has been detached. This
keeps late completions from touching a freed or rebound p9_client.
The Linux kernel CVE team has assigned CVE-2026-99776 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 6.12.118 with commit e56ec7e03bec90050368b9bc268d1de098bb92bc
Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 6.18.64 with commit 951a7562ecde301a30ded7305b61dd0e9784bee8
Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 7.3.5 with commit c090c95f747714999a3fdebafa07b663473b7b7b
Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 7.4-rc2 with commit a478958f4c1181ff3362f8857b489c2d069f9c7d
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-99776
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:
net/9p/trans_usbg.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/e56ec7e03bec90050368b9bc268d1de098bb92bc
https://git.kernel.org/stable/c/951a7562ecde301a30ded7305b61dd0e9784bee8
https://git.kernel.org/stable/c/c090c95f747714999a3fdebafa07b663473b7b7b
https://git.kernel.org/stable/c/a478958f4c1181ff3362f8857b489c2d069f9c7d
reply other threads:[~2026-11-20 6:02 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=2026112030-CVE-2026-99776-6ffa@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.