CVE-2026-52979

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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...

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

Published

June 24, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jul 16, 2026
Patch available.
generic

net: psp: check for device unregister when creating assoc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e201c57073e624dd2ba5beaf9eda31e19b77b332
generic

net: psp: check for device unregister when creating assoc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b89769f936a8fa9e66de72ddc1b71a9745a488e6

Vendor Advisories for CVE-2026-52979(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 6× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 195 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 15:22 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-26 00:27 UTCEPSS rescore
  16. 2026-09-23 11:31 UTCEG score recompute
  17. 2026-09-23 11:31 UTCVendor advisory
  18. 2026-09-23 11:31 UTCGHSA enrichment
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-18 08:06 UTCEG score recompute
  21. 2026-09-18 08:06 UTCVendor advisory
  22. 2026-09-18 08:06 UTCGHSA enrichment
  23. 2026-09-16 14:08 UTCEPSS rescore
  24. 2026-09-16 05:15 UTCEPSS rescore
  25. 2026-09-14 01:53 UTCEG score recompute
Show 75 more
  1. 2026-09-14 01:53 UTCVendor advisory
  2. 2026-09-14 01:53 UTCGHSA enrichment
  3. 2026-09-13 16:47 UTCEPSS rescore
  4. 2026-09-12 17:09 UTCEG score recompute
  5. 2026-09-12 17:09 UTCVendor advisory
  6. 2026-09-12 17:09 UTCGHSA enrichment
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-10 09:35 UTCEPSS rescore
  9. 2026-09-08 22:01 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-08-30 20:14 UTCEG score recompute
  16. 2026-08-30 20:14 UTCVendor advisory
  17. 2026-08-30 20:14 UTCGHSA enrichment
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-28 04:47 UTCEG score recompute
  22. 2026-08-28 04:47 UTCVendor advisory
  23. 2026-08-28 04:47 UTCGHSA enrichment
  24. 2026-08-27 14:25 UTCEPSS rescore
  25. 2026-08-26 14:46 UTCEPSS rescore
  26. 2026-08-25 13:49 UTCEPSS rescore
  27. 2026-08-24 13:45 UTCEG score recompute
  28. 2026-08-24 13:45 UTCVendor advisory
  29. 2026-08-24 13:44 UTCGHSA enrichment
  30. 2026-08-23 10:54 UTCEG score recompute
  31. 2026-08-23 10:54 UTCVendor advisory
  32. 2026-08-23 10:53 UTCGHSA enrichment
  33. 2026-08-23 00:19 UTCEPSS rescore
  34. 2026-08-22 13:08 UTCEG score recompute
  35. 2026-08-22 13:08 UTCVendor advisory
  36. 2026-08-22 13:07 UTCGHSA enrichment
  37. 2026-08-21 23:49 UTCEPSS rescore
  38. 2026-08-21 05:20 UTCEG score recompute
  39. 2026-08-21 05:20 UTCVendor advisory
  40. 2026-08-21 05:20 UTCGHSA enrichment
  41. 2026-08-20 22:55 UTCEPSS rescore
  42. 2026-08-20 07:31 UTCVendor advisory
  43. 2026-08-20 07:30 UTCGHSA enrichment
  44. 2026-08-19 02:14 UTCEG score recompute
  45. 2026-08-19 02:14 UTCVendor advisory
  46. 2026-08-19 02:13 UTCGHSA enrichment
  47. 2026-08-18 13:48 UTCEPSS rescore
  48. 2026-08-17 14:43 UTCEG score recompute
  49. 2026-08-17 14:43 UTCVendor advisory
  50. 2026-08-17 14:42 UTCGHSA enrichment
  51. 2026-08-17 13:47 UTCEPSS rescore
  52. 2026-08-16 17:00 UTCEG score recompute
  53. 2026-08-16 17:00 UTCVendor advisory
  54. 2026-08-16 17:00 UTCGHSA enrichment
  55. 2026-08-16 14:56 UTCEPSS rescore
  56. 2026-08-16 02:14 UTCEPSS rescore
  57. 2026-08-15 19:17 UTCEG score recompute
  58. 2026-08-15 19:17 UTCVendor advisory
  59. 2026-08-15 19:17 UTCGHSA enrichment
  60. 2026-08-15 01:30 UTCEPSS rescore
  61. 2026-08-14 21:34 UTCVendor advisory
  62. 2026-08-14 21:34 UTCGHSA enrichment
  63. 2026-08-13 23:51 UTCEG score recompute
  64. 2026-08-13 23:51 UTCVendor advisory
  65. 2026-08-13 23:51 UTCGHSA enrichment
  66. 2026-08-13 22:00 UTCEPSS rescore
  67. 2026-08-13 02:01 UTCVendor advisory
  68. 2026-08-13 02:01 UTCGHSA enrichment
  69. 2026-08-12 04:18 UTCVendor advisory
  70. 2026-08-12 04:18 UTCGHSA enrichment
  71. 2026-08-11 06:36 UTCVendor advisory
  72. 2026-08-11 06:36 UTCGHSA enrichment
  73. 2026-08-10 08:53 UTCVendor advisory
  74. 2026-08-10 08:53 UTCGHSA enrichment
  75. 2026-08-09 11:10 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-52979?
CVE-2026-52979 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: net: psp: check for device unregister when creating assoc pspassocdevicegetlocked() obtains a psp_dev reference via pspdevgetforsock() (which uses pspdevtryget() under RCU); it then acquires psd->lock and drops the reference.…
When was CVE-2026-52979 disclosed?
CVE-2026-52979 was first published on June 24, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52979 actively exploited?
CVE-2026-52979 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52979?
CVE-2026-52979 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-52979?
A fix for CVE-2026-52979 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52979 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52979

Explore →

Is Your Infrastructure Affected by CVE-2026-52979?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.