published 5 Nov 2024 · updated 12 Aug 2026
dm vdo: don't refer to dedupe_context after releasing it
7.8HighCVSS 7.8EPSS 0%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0808ebf2f80b962e75741a41ced372a7116f1e26 and Kernel 63ef073084c67878d7a92e15ad055172da3f05a3.
In the Linux kernel, the following vulnerability has been resolved: dm vdo: don't refer to dedupe_context after releasing it Clear the dedupe_context pointer in a data_vio whenever ownership of the context is lost, so that vdo can't examine it accidentally.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.9, >=cfaf07fae7a262865a67b6010eef3bc0a1ae50b2 <0808ebf2f80b962e75741a41ced372a7116f1e26, >=cfaf07fae7a262865a67b6010eef3bc0a1ae50b2 <63ef073084c67878d7a92e15ad055172da3f05a3 | 0808ebf2f80b962e75741a41ced372a7116f1e26, 63ef073084c67878d7a92e15ad055172da3f05a3 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
10.0CriticalPublic exploit
10.0CriticalPublic exploit
Embed
A live severity badge for an advisory, README or ticket