CVE-2026-53010

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-24. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: fix use-after-free in smb2_open during durable reconnect

In smb2_open, the call to ksmbd_put_durable_fd(fp) drops the reference to the durable file descriptor early during the durable reconnect process. If an error occurs subsequently (eg, ksmbd_iov_pin_rsp fails) or a scavenger accesses the file, it leads to a use-after-free when accessing fp properties (eg fp->create_time).

Move the single put to the end of the function below err_out2 so fp stays valid until smb2_open returns.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Sep 9, 2026
No patch confirmed yet.
generic

ksmbd: fix use-after-free in smb2_open during durable reconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1baff47b81f94f9231c91236aa511420d0e266b9
generic

ksmbd: fix use-after-free in smb2_open during durable reconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/97a0cd55283b4e63fd92804da91c8d9896adcad9
generic

ksmbd: fix use-after-free in smb2_open during durable reconnect - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-53010(2)

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

Patch Availability(8)

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)
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

(8)

Data Freshness Timeline

(refreshed 5× in last 7d / 152× 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 498 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53010?
CVE-2026-53010 is a critical vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in smb2_open during durable reconnect In smb2open, the call to ksmbdputdurablefd(fp) drops the reference to the durable file descriptor early during the durable reconnect process. If an error occurs…
When was CVE-2026-53010 disclosed?
CVE-2026-53010 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53010 actively exploited?
CVE-2026-53010 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 63.7% of all scored CVEs.
What is the CVSS score of CVE-2026-53010?
CVE-2026-53010 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53010?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53010, 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-53010

Explore →

Is Your Infrastructure Affected by CVE-2026-53010?

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