Skip to main content
Mallory
CriticalVulnerability

CVE-2025-68263: Use-after-free in Linux kernel ksmbd IPC response handling

Published Dec 16, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS0.47%42nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Linux
IdentifiersCVE-2025-68263CWE-416

CVE-2025-68263 is a use-after-free vulnerability in the Linux kernel ksmbd IPC implementation. ipc_msg_send_request() waits for a generic netlink reply using a stack-allocated ipc_msg_table_entry. The response handlers populate entry->response while holding ipc_msg_table_lock, but the request function previously validated and freed that response without holding the same lock. Under high concurrency, handle_response() can copy data into a response buffer that ipc_msg_send_request() has already freed, producing a slab use-after-free write detected by KASAN in handle_generic_event(). The fix synchronizes response validation, invalid-response cleanup, and hash-table removal under ipc_msg_table_lock before returning the final response pointer.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

The race causes kernel memory corruption through a write to a freed ksmbd response buffer. It can cause a kernel crash or denial of service. Privilege escalation or arbitrary code execution in kernel context may also be possible, depending on exploitability; these outcomes are not demonstrated by the supplied technical details.

Mitigation

If you can’t patch tonight, do this now.

Until patched, disable ksmbd and prevent its kernel module from loading where feasible. If ksmbd must remain enabled, restrict SMB access to trusted hosts and networks to reduce exposure to traffic that could trigger the concurrency race. Access restrictions do not correct the underlying memory-safety defect.

Remediation

Patch, then assume compromise.

Update to a vendor-supported Linux kernel containing the CVE-2025-68263 fix, or backport the upstream ksmbd patch. The patch holds ipc_msg_table_lock while validating and freeing invalid responses and removing the IPC table entry, returns the response pointer only after locked removal, and preserves NULL returns on error. For Debian oldstable (bookworm), upgrade the linux packages to version 6.1.162-1 or a later fixed version. Applicable Tanzu fixes are included in Ubuntu Jammy Stemcells 1.1282.x and Foundation Core releases 3.1.13 or 3.3.4, according to the deployed product branch.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system
FAQ

Frequently asked questions

Is CVE-2025-68263 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2025-68263 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-68263?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2025-68263.
Is there a patch for CVE-2025-68263?
Update to a vendor-supported Linux kernel containing the CVE-2025-68263 fix, or backport the upstream ksmbd patch. The patch holds ipc_msg_table_lock while validating and freeing invalid responses and removing the IPC table entry, returns the response pointer only after locked removal, and preserves NULL returns on error.
What products are affected by CVE-2025-68263?
Linux Kernel.
How severe is CVE-2025-68263?
CVE-2025-68263 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.47% (42nd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

16 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.