CVE-2026-43376

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