CVE-2026-43379
Received Received - Intake
ksmbd Use-After-Free in Linux Kernel

Publication date: 2026-05-08

Last updated on: 2026-05-08

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in smb_lazy_parent_lease_break_close() opinfo pointer obtained via rcu_dereference(fp->f_opinfo) is being accessed after rcu_read_unlock() has been called. This creates a race condition where the memory could be freed by a concurrent writer between the unlock and the subsequent pointer dereferences (opinfo->is_lease, etc.), leading to a use-after-free.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-08
Last Modified
2026-05-08
Generated
2026-05-09
AI Q&A
2026-05-08
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a use-after-free issue in the Linux kernel's ksmbd component, specifically in the smb_lazy_parent_lease_break_close() function.

The problem occurs because an opinfo pointer, obtained via rcu_dereference(fp->f_opinfo), is accessed after rcu_read_unlock() has been called. This creates a race condition where the memory pointed to by opinfo could be freed by another concurrent process before it is accessed, leading to use-after-free errors.


How can this vulnerability impact me? :

The use-after-free vulnerability can lead to undefined behavior such as system crashes, data corruption, or potential execution of arbitrary code if exploited.

Because it involves a race condition in kernel memory management, an attacker might exploit this to cause denial of service or escalate privileges on the affected system.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart