Linux Kernel dm-vdo use-after-free fix in dedupe.c

From this webpage screenshot, we can obtain the following key information about the vulnerability: 1. Vulnerability Description: - The vulnerability is described as "dm vdo: don't refer to dedupe_context after releasing it". - The context is "Upstream commit 0808ebf2f80b962e75741a41ced372a7116f1e26". 2. Fix Description: - The fix is: "Clear the dedupe_context pointer in a data_vio whenever ownership of the context is lost, so that vdo can't examine it accidentally". - This means that whenever ownership of the context is lost in a data_vio, the dedupe_context pointer should be cleared to prevent vdo from accidentally accessing it. 3. Sign-off Submitters: - The fix was signed off by the following individuals: - Ken Raeburn - Matthew Sakai - Mikulas Patocka - Sasha Levin 4. Diffstat: - The diffstat shows 3 insertions and 0 deletions in the file "drivers/md/dm-vdo/dedupe.c". 5. Code Changes: - The code changes include: - In the function, setting to . - In the function, if returns , setting to . - In the function, setting to . These details indicate that the vulnerability fix addresses the issue of not referencing after releasing ownership in a data_vio, preventing vdo from accidentally examining it. The fix involves clearing the pointer in relevant functions.

Goal Reached Thanks to every supporter — we hit 100%!

Linux Kernel dm-vdo use-after-free fix in dedupe.c