dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53010

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.7 / 6.18.33 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A use-after-free vulnerability exists in the Linux kernel's ksmbd SMB server. During the durable reconnect process in smb2_open, ksmbd_put_durable_fd(fp) is called prematurely, releasing the file descriptor reference early. If subsequent errors occur (such as ksmbd_iov_pin_rsp failing) or a scavenger accesses the file, the freed fp structure is accessed, causing use-after-free when reading fp properties like create_time.

MitigationApply the kernel patch that relocates ksmbd_put_durable_fd() to the end of smb2_open after err_out2, or upgrade to a kernel version containing this fix. Given the critical severity and network-exploitable nature (CVSS 9.8), prioritize immediate patching of affected systems running ksmbd.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.6.32, < 6.7>= 6.9, < 6.18.33>= 6.19, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify ksmbd is active
    Run 'lsmod | grep ksmbd' or check if ksmbd process is running via 'ps aux | grep ksmbd'
    Affected if ksmbd module is loaded or running as a daemon/service
  2. Confirm SMB durable handles are enabled
    Check ksmbd configuration file (typically /etc/ksmbd/ksmbd.conf or /etc/samba/smb.conf for ksmbd settings) for 'durable handle' or 'share' configurations that enable durable handles
    Affected if SMB shares with durable handles are configured and active
  3. Check kernel version
    Run 'uname -r' to obtain the kernel version; compare against upstream kernel versions that contain the fix (the patch moves ksmbd_put_durable_fd from its premature location to below err_out2 in smb2_open)
    Affected if Kernel version predates the patch that relocates ksmbd_put_durable_fd in the smb2_open function
  4. Inspect smb2_open source if accessible
    Locate the ksmbd source file containing smb2_open function (typically in the kernel source under fs/ksmbd/smb2pdu.c); search for 'ksmbd_put_durable_fd' calls within the function to verify if the vulnerability condition exists
    Affected if The ksmbd_put_durable_fd(fp) call appears before error handling code (err_out2 label) rather than after all error paths have completed

A system is affected if it runs ksmbd with SMB durable handles enabled on a kernel version where ksmbd_put_durable_fd is called prematurely inside smb2_open, allowing the file descriptor to be freed before all error paths complete.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 6.7 / 6.18.33 / 7.0.10 or later
Fixed in 6.76.18.337.0.10
Interim mitigation

Apply the kernel patch that relocates ksmbd_put_durable_fd() to the end of smb2_open after err_out2, or upgrade to a kernel version containing this fix. Given the critical severity and network-exploitable nature (CVSS 9.8), prioritize immediate patching of affected systems running ksmbd.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53010 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53010 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data