CVE-2026-53046

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: 1%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 from async crypto on Qualcomm crypto engine

ksmbd_crypt_message() sets a NULL completion callback on AEAD requests and does not handle the -EINPROGRESS return code from async hardware crypto engines like the Qualcomm Crypto Engine (QCE). When QCE returns -EINPROGRESS, ksmbd treats it as an error and immediately frees the request while the hardware DMA operation is still in flight. The DMA completion callback then dereferences freed memory, causing a NULL pointer crash:

pc : qce_skcipher_done+0x24/0x174 lr : vchan_complete+0x230/0x27c ... el1h_64_irq+0x68/0x6c ksmbd_free_work_struct+0x20/0x118 [ksmbd] ksmbd_exit_file_cache+0x694/0xa4c [ksmbd]

Use the standard crypto_wait_req() pattern with crypto_req_done() as the completion callback, matching the approach used by the SMB client in fs/smb/client/smb2ops.c. This properly handles both synchronous engines (immediate return) and async engines (-EINPROGRESS followed by callback notification).

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%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 2026

Advisory Details (7)

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

ksmbd: fix use-after-free from async crypto on Qualcomm crypto engine - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e298897f41c61450c2e7a4f457e8b2485eb35b3
generic

ksmbd: fix use-after-free from async crypto on Qualcomm crypto engine - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: fix use-after-free from async crypto on Qualcomm crypto engine - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7164b3953cefd540e7ebca828c793bc6869cfbc4
generic

ksmbd: fix use-after-free from async crypto on Qualcomm crypto engine - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ef183216feaa24b66b940510d8b68f680eb56e9
generic

ksmbd: fix use-after-free from async crypto on Qualcomm crypto engine - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8fcefe840fa8c14ce667768e5b043286ac3bbcbe
generic

ksmbd: fix use-after-free from async crypto on Qualcomm crypto engine - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: fix use-after-free from async crypto on Qualcomm crypto engine - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/57b47231055b431ed0a1a55f33cac32981564405

Vendor Advisories for CVE-2026-53046(2)

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

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-31ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-31ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-31ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-31ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-31ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-31ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-31ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-31ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-31ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-31ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-31ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-31ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-31ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-31ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-31ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-31ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-31ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-31ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-31ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-31ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-31ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-31ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-31ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-31ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-31ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-31ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-31ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-31ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-31ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-31ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
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

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53046?
CVE-2026-53046 is a critical vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free from async crypto on Qualcomm crypto engine ksmbdcryptmessage() sets a NULL completion callback on AEAD requests and does not handle the -EINPROGRESS return code from async hardware crypto engines like the…
When was CVE-2026-53046 disclosed?
CVE-2026-53046 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-53046 actively exploited?
CVE-2026-53046 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.2% of all scored CVEs.
What is the CVSS score of CVE-2026-53046?
CVE-2026-53046 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53046?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53046, 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-53046

Explore →

Is Your Infrastructure Affected by CVE-2026-53046?

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

Start Free Scan →Browse All CVEs