CVE-2026-52979
Last modified
CVE-2026-52979 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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...
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.18, < 6.18.33 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.10 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-52979?
How severe is CVE-2026-52979?
How do I fix CVE-2026-52979?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-52973In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-52974In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-52975In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-52976In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-52977In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52978In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52980In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52981In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-52982In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-52983In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-52984In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52985In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-52979?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST