Description (CNA)
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().
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| Linux / Linux | affected 296cb5457cc6f4a754c4ae29855f8a253d52bcc6 before 302fef75512b2c8329a3f5efab1ae7ba2562387a; affected d54ab1520d43e95f9b2e22d7a05fc9614192e5a5 before 08aa9f3c8cf4d0bee44df540dfe34e8d64069f2c; affected 18b4fac5ef17f77fed9417d22210ceafd6525fc7 before 1d6abf145615dbfe267ce3b0a271f95e3780e18e; affected 18b4fac5ef17f77fed9417d22210ceafd6525fc7 before ce8507ee82c888126d8e7565e27c016308d24cde; affected 18b4fac5ef17f77fed9417d22210ceafd6525fc7 before 1dfd062caa165ec9d7ee0823087930f3ab8a6294; affected d73686367ad68534257cd88a36ca3c52cb8b81d8; affected 6.6.88 before 6.6.130; affected 6.12.25 before 6.12.78; affected 6.14.4 before 6.15 |
| Linux / Linux | affected 6.15; unaffected 0 before 6.15; unaffected 6.6.130 through 6.6.*; unaffected 6.12.78 through 6.12.*; unaffected 6.18.19 through 6.18.*; unaffected 6.19.9 through 6.19.*; unaffected 7.0 through * |
CWE
No CWE identifiers supplied.
References
- https://git.kernel.org/stable/c/302fef75512b2c8329a3f5efab1ae7ba2562387a
- https://git.kernel.org/stable/c/08aa9f3c8cf4d0bee44df540dfe34e8d64069f2c
- https://git.kernel.org/stable/c/1d6abf145615dbfe267ce3b0a271f95e3780e18e
- https://git.kernel.org/stable/c/ce8507ee82c888126d8e7565e27c016308d24cde
- https://git.kernel.org/stable/c/1dfd062caa165ec9d7ee0823087930f3ab8a6294