md: fix rcu protection in md_wakeup_thread
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
md: fix rcu protection in md_wakeup_thread
We attempted to use RCU to protect the pointer 'thread', but directly passed the value when calling md_wakeup_thread(). This means that the RCU pointer has been acquired before rcu_read_lock(), which renders rcu_read_lock() ineffective and could lead to a use-after-free.
From the CVE record · Linux
The Linux kernel's md_wakeup_thread function can acquire a thread pointer before taking the RCU read lock, leaving the pointer insufficiently protected. This could lead to a use-after-free. The input does not specify whether an attacker can trigger it or what access or interaction would be required.
Engineers running Linux kernels that may contain the affected md_wakeup_thread code should check their versions against the vendor advisory; affected versions were not provided.