Linux Kernel up to 6.18.32/7.0.9 net psp_assoc_device_get_locked lock locking

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.18.32/7.0.9. It has been rated as critical. The affected element is the function psp_assoc_device_get_locked of the component net. Performing a manipulation of the argument lock results in locking. This vulnerability is identified as CVE-2026-52979. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel up to 6.18.32/7.0.9. This affects the function psp_assoc_device_get_locked of the component net. The manipulation of the argument lock with an unknown input leads to a locking vulnerability. CWE is classifying the issue as CWE-667. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. This is going to have an impact on availability. The summary by CVE is:

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 advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-52979 since 06/09/2026. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 323351 (Linux Distros Unpatched Vulnerability : CVE-2026-52979), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.18.33 or 7.0.10 eliminates this vulnerability. Applying the patch d90df5ce6deb2424de3ad89bcc693ac1b67accc9/e201c57073e624dd2ba5beaf9eda31e19b77b332/b89769f936a8fa9e66de72ddc1b71a9745a488e6 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (323351) and CERT Bund (WID-SEC-2026-2077). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• SUSE openSUSE
• Open Source Linux Kernel
• RESF Rocky Linux
• Oracle Linux

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 6.18.0
• 6.18.1
• 6.18.2
• 6.18.3
• 6.18.4
• 6.18.5
• 6.18.6
• 6.18.7
• 6.18.8
• 6.18.9
• 6.18.10
• 6.18.11
• 6.18.12
• 6.18.13
• 6.18.14
• 6.18.15
• 6.18.16
• 6.18.17
• 6.18.18
• 6.18.19
• 6.18.20
• 6.18.21
• 6.18.22
• 6.18.23
• 6.18.24
• 6.18.25
• 6.18.26
• 6.18.27
• 6.18.28
• 6.18.29
• 6.18.30
• 6.18.31
• 6.18.32
• 7.0.0
• 7.0.1
• 7.0.2
• 7.0.3
• 7.0.4
• 7.0.5
• 7.0.6
• 7.0.7
• 7.0.8
• 7.0.9

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion