CVE-2025-68374
What it is
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.
At a glance
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Deferred
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-68374.md and follow it. Check whether this project is affected by CVE-2025-68374. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- https://git.kernel.org/stable/c/0dc76205549b4c25705e54345f211b9f66e018a0
- https://git.kernel.org/stable/c/21989cb5034c835b212385a2afadf279d8069da0
- https://git.kernel.org/stable/c/a4bd1caf591faeae44cb10b6517e7dacb5139bda
- https://git.kernel.org/stable/c/dc6d1249ee35c1c76700b4b96281daeb7637bce1
- https://git.kernel.org/stable/c/f98b191f78124405294481dea85f8a22a3eb0a59