Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2026-53046

A critical use‑after‑free bug in the Linux kernel’s ksmbd component can crash the system when Qualcomm crypto engines are used. The flaw occurs when the kernel incorrectly handles asynchronous crypto requests, freeing memory before the hardware operation completes. An attacker could trigger a crash, potentially leading to denial of service.

publishedJun 24, 2026
last modifiedJul 21, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
42th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 20, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel (all versions before the ksmbd patch) – Linux system administrators and users running older kernel versions are affected.

02

Real-world impact

An attacker could crash the system, causing a denial of service and potentially disrupting services that rely on the kernel’s SMB server.

03

Why this severity

The CVSS score of 9.8 reflects that the vulnerability can be exploited remotely without authentication, leading to a complete loss of confidentiality, integrity, and availability. The attack requires no user interaction and can crash the system, making it a critical threat.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade the Linux kernel to a version that includes the ksmbd patch that fixes the use‑after‑free vulnerability.
  2. 02Reboot the system to load the new kernel.

NVD-referenced vendor advisory

05

Timeline

  1. Jun 24, 2026 · Jun 24, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 21, 2026 · 13d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 21, 2026 · 13d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →