From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-52978: net: psp: require admin permission for dev-set and key-rotate
Date: Wed, 24 Jun 2026 17:30:02 +0100 [thread overview]
Message-ID: <2026062441-CVE-2026-52978-fa50@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: psp: require admin permission for dev-set and key-rotate
The dev-set and key-rotate netlink operations modify shared device
state (PSP version configuration and cryptographic key material,
respectively) but do not require CAP_NET_ADMIN. The only access
control is psp_dev_check_access() which merely verifies netns
membership.
The Linux kernel CVE team has assigned CVE-2026-52978 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.18 with commit 00c94ca2b99e6610e483f92e531b319eeaed94aa and fixed in 6.18.33 with commit aa1a08a4632af5d1117779e7ff0e32e3c69f29bd
Issue introduced in 6.18 with commit 00c94ca2b99e6610e483f92e531b319eeaed94aa and fixed in 7.0.10 with commit fb88a8c86109edb15971481e3de816a8bfdfe571
Issue introduced in 6.18 with commit 00c94ca2b99e6610e483f92e531b319eeaed94aa and fixed in 7.1 with commit b718342a7fbaa2dff5fefc31988c07af8c6cbc21
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-52978
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:
Documentation/netlink/specs/psp.yaml
net/psp/psp-nl-gen.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/aa1a08a4632af5d1117779e7ff0e32e3c69f29bd
https://git.kernel.org/stable/c/fb88a8c86109edb15971481e3de816a8bfdfe571
https://git.kernel.org/stable/c/b718342a7fbaa2dff5fefc31988c07af8c6cbc21
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-52978-fa50@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.