CVE-2025-68374
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
In the Linux kernel, a use-after-free in md_wakeup_thread arises because RCU protection is misapplied: the pointer is dereferenced before holding the RCU read lock.
Root
Cause
The vulnerability is a use-after-free in the Linux kernel's MD (Multiple Device) RAID subsystem. The function md_wakeup_thread() is called with a pointer to a thread structure that should be RCU-protected. However, the pointer value is obtained *before* entering the RCU read-side critical section, i.e., the dereference occurs outside rcu_read_lock(). This means the RCU protection is ineffective leading to a race condition. [1]
Exploitation
An attacker would need to trigger a scenario where the underlying md_thread structure is freed while md_wakeup_thread() attempts to access it. This could happen if a concurrent operation (e.g., module removal or device teardown) frees the thread object. The bug requires local access or the ability to trigger MD operations; no special privileges are mentioned beyond the ability to manipulate MD devices.
Impact
If the race is hit, the kernel dereferences a freed pointer, resulting in a use-after-free. This can cause a kernel crash (denial of service) or potentially allow an attacker to corrupt memory and escalate privileges, depending on the memory layout. [2]
Mitigation
The fix ensures that the RCU read lock is acquired before the pointer is fetched, so the dereference is properly protected. This vulnerability has been patched in the upstream Linux kernel stable branches. Users should apply the latest kernel updates to remove the race condition.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
4News mentions
0No linked articles in our index yet.