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
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jul 16, 2026
No patch confirmed yet.
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(9)

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 rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1

Weakness Classification(1)

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

All Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 10× in last 7d / 47× 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 177 total refreshes for this CVE.

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

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 99.3% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52979, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.