CVE 9.8 CRITICAL

ksmbd: fix use-after-free by using call_rcu() for oplock_info_CVE-2026-43376

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

Description

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

Basic Information

ID CVE-2026-43376
Source Linux
Published May 8, 2026 at 14:21
Modified May 11, 2026 at 06:33

Affected Product

Vendor Linux
Product Linux
Version 296cb5457cc6f4a754c4ae29855f8a253d52bcc6
Affected Versions Linux Linux 296cb5457cc6f4a754c4ae29855f8a253d52bcc6
Linux Linux d54ab1520d43e95f9b2e22d7a05fc9614192e5a5
Linux Linux 18b4fac5ef17f77fed9417d22210ceafd6525fc7
Linux Linux 18b4fac5ef17f77fed9417d22210ceafd6525fc7
Linux Linux 18b4fac5ef17f77fed9417d22210ceafd6525fc7
Linux Linux d73686367ad68534257cd88a36ca3c52cb8b81d8
Linux Linux 6.15

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.