From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-52979: net: psp: check for device unregister when creating assoc
Date: Wed, 24 Jun 2026 17:30:03 +0100 [thread overview]
Message-ID: <2026062441-CVE-2026-52979-3fee@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: psp: check for device unregister when creating assoc
psp_assoc_device_get_locked() obtains a psp_dev reference via
psp_dev_get_for_sock() (which uses psp_dev_tryget() under RCU);
it then acquires psd->lock and drops the reference. Before
the lock is taken, psp_dev_unregister() can run to completion:
take psd->lock, clear out state, unlock, drop the registration
reference.
The expectation is that the lock prevents device unregistration,
but much like with netdevs special care has to be taken when
"upgrading" a reference to a locked device. Add the missing
check if device is still alive. psp_dev_is_registered() exists
already but had no callers, which makes me wonder if I either
forgot to add this or lost the check during refactoring...
The Linux kernel CVE team has assigned CVE-2026-52979 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.18 with commit 6b46ca260e2290e3453d1355ab5b6d283d73d780 and fixed in 6.18.33 with commit d90df5ce6deb2424de3ad89bcc693ac1b67accc9
Issue introduced in 6.18 with commit 6b46ca260e2290e3453d1355ab5b6d283d73d780 and fixed in 7.0.10 with commit e201c57073e624dd2ba5beaf9eda31e19b77b332
Issue introduced in 6.18 with commit 6b46ca260e2290e3453d1355ab5b6d283d73d780 and fixed in 7.1 with commit b89769f936a8fa9e66de72ddc1b71a9745a488e6
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-52979
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/psp/psp_nl.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/d90df5ce6deb2424de3ad89bcc693ac1b67accc9
https://git.kernel.org/stable/c/e201c57073e624dd2ba5beaf9eda31e19b77b332
https://git.kernel.org/stable/c/b89769f936a8fa9e66de72ddc1b71a9745a488e6
reply other threads:[~2026-06-24 16:34 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=2026062441-CVE-2026-52979-3fee@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.