MEDIUM 5.5

CVE-2026-52978: Linux Kernel PSP Missing CAP_NET_ADMIN Permission Check

A Linux kernel networking subsystem (PSP) fails to enforce proper permission checks on two critical operations: changing device settings (dev-set) and rotating cryptographic keys (key-rotate). Currently, any user on the system who has access to the network namespace can perform these operations, even though they modify shared device state that should be restricted to administrators. This allows unprivileged local users to tamper with PSP configuration and key material without needing root-level capabilities.

Source data · NVD / CISA · public domain

CVSS
3.1 · 5.5 MEDIUM · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weaknesses (CWE)
Affected products
2 configuration(s)
Published / Modified
2026-06-24 / 2026-07-14

NVD description (verbatim)

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.

3 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

The vulnerability exists in the Linux kernel's PSP (Protocol Security Processor) netlink implementation. The dev-set and key-rotate netlink operations lack CAP_NET_ADMIN capability checks, relying solely on psp_dev_check_access() which only validates network namespace membership. This permits unprivileged users within the same netns to invoke operations that modify PSP version configuration and cryptographic key material—state that should be protected by administrative privilege. The fix requires adding proper capability enforcement to these operations before processing the netlink requests.

Business impact

Organizations using Linux systems with PSP networking features in multi-tenant or shared-namespace environments face elevated risk of configuration tampering and cryptographic key compromise. An unprivileged local attacker could alter PSP settings or rotate keys maliciously, potentially degrading the security of encrypted traffic or enabling denial of service. The impact is confined to local attack scenarios but could compromise the integrity of network security controls that depend on PSP's proper configuration.

Affected systems

The Linux kernel is affected. While the specific affected versions are not enumerated in the source data, the vulnerability resolution indicates this impacts kernel builds that include PSP networking support. Organizations should verify their kernel version against the vendor advisory and check whether PSP is enabled and actively used in their deployment. Systems without PSP functionality enabled are not at risk.

Exploitability

Exploitability is moderate but practical. An attacker must have local user-level access to the affected system and reside within the same network namespace as the target PSP device. No authentication bypass, race conditions, or kernel bugs are required—the flaw is straightforward permission enforcement. No public exploit code is known at this time, and the CVSS score of 5.5 reflects local-only attack vector and lack of confidentiality impact, though availability and integrity are directly threatened.

Remediation

Apply kernel updates from your Linux distribution that patch PSP to enforce CAP_NET_ADMIN capability checks on dev-set and key-rotate netlink operations. Verify the patch against the vendor advisory to confirm the specific kernel version that resolves this issue. Until patched, restrict network namespace access to trusted users only, and monitor netlink activity for suspicious PSP-related calls.

Patch guidance

Contact your Linux distribution vendor for patched kernel versions. The fix requires adding CAP_NET_ADMIN checks to the PSP netlink command handlers before processing dev-set and key-rotate operations. Rebuild and test the patched kernel in a staging environment before production deployment. Verify that PSP functionality remains operational post-patch and that administrative operations still work as expected.

Detection guidance

Monitor netlink traffic for PSP operations (dev-set, key-rotate) originating from unprivileged user contexts. Use audit framework rules to log CAP_NET_ADMIN capability checks and denials. Check kernel logs for permission-related errors in PSP subsystem operations. On vulnerable systems, correlate local user activity with netlink operations targeting PSP configuration to identify reconnaissance or tampering attempts.

Why prioritize this

While the CVSS score of 5.5 is medium, this vulnerability should be prioritized for rapid patching in environments where PSP is actively deployed for network encryption or security policy enforcement. The combination of local access, direct manipulation of cryptographic key material, and lack of current awareness (not in CISA KEV) means this may be overlooked—but the integrity threat to security-critical infrastructure justifies prompt remediation. Organizations not using PSP can defer this update.

Risk score, explained

CVSS 5.5 (Medium) reflects: local-only attack vector (AV:L), low attack complexity (AC:L), low privilege requirements (PR:L), no user interaction (UI:N), unchanged scope (S:U), no confidentiality impact (C:N), no integrity impact directly on user data (I:N), but high availability impact (A:H) due to key rotation and configuration tampering. The score appropriately captures the threat to system availability and operational integrity of PSP, though the ability to modify cryptographic keys elevates real-world risk beyond the numerical score alone.

Frequently asked questions

Does this vulnerability affect systems that do not use PSP?

No. This vulnerability is specific to the Linux kernel PSP networking subsystem. If your system does not enable or use PSP, you are not affected. Check your kernel configuration and running services to confirm PSP is not in active use.

Can this be exploited remotely?

No. The CVSS vector and vulnerability description both confirm this is a local-only attack. An attacker must have user-level access to the affected system and reside within the same network namespace. Remote exploitation is not possible.

What is the actual risk of key rotation tampering?

If an attacker rotates PSP keys without authorization, they could degrade the security of encrypted traffic or cause legitimate traffic to fail authentication, resulting in denial of service. The true risk depends on whether PSP keys protect critical network paths in your infrastructure.

Is there a workaround if I cannot patch immediately?

Until patched, restrict namespace access and container/VM isolation to trusted users only. Monitor netlink and audit logs for suspicious PSP operations. However, patching is strongly recommended because the fix is straightforward and low-risk.

This analysis is based on the CVE record and vendor description as of the publication and modification dates provided. Affected kernel versions and patch availability must be verified against the official Linux kernel security advisory and your distribution vendor. This document does not constitute a guarantee of vulnerability presence or absence in any specific system configuration. Organizations should conduct their own risk assessment and testing before deploying patches in production environments. Source: NVD (public-domain), retrieved 2026-07-30. Analysis generated by SEC.co (claude-haiku-4-5).