Back

CRITICAL

ksmbd: fix use-after-free by using call_rcu() for oplock_info

Published May 8, 2026

Description

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().

Affected products

Remediation

No remediation recorded yet.

References (11)

Change history (0)

No recorded changes yet.

Sources

CVE.org / MITRE

Status PUBLISHED
Assigner Linux
Published May 8, 2026
Updated Aug 5, 2026
Reserved May 1, 2026

CISA Vulnrichment

No data

NVD

Status Analyzed
Modified Jun 17, 2026

Red Hat

Public date May 8, 2026
Bugzilla 2468218

ENISA EUVD

Assigner Linux
Published May 8, 2026
Updated Aug 5, 2026

GitHub

No data