CVE-2026-43376

What it is

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free by using call_rcu() for oplock_info ksmbd currently frees oplock_info immediately using kfree(), even though it is accessed under RCU read-side critical sections in places like opinfo_get() and proc_show_files(). Since there is no RCU grace period delay between nullifying the pointer and freeing the memory, a reader can still access oplock_info structure after it has been freed. This can leads to a use-after-free especially in opinfo_get() where atomic_inc_not_zero() is called on already freed memory. Fix this by switching to deferred freeing using call_rcu().

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-05-08 15:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 10:49 UTC Last updatedMost recent change to the record

Details

Published

2026-05-08 15:16 UTC

Last modified

2026-06-17 10:49 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-416 · Use after free

Record status

Analyzed

Affected

• Linux Kernel < 6.6.130
• Linux Kernel < 6.12.78
• Linux Kernel < 6.15
• Linux Kernel < 6.18.19
• Linux Kernel < 6.19.9
• Linux Kernel 6.15
• Linux Kernel 7.0

Attack profile CVSS 3.1 · 9.8

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High