CVE-2024-50091Published Nov 5, 2024 · Nov 5Updated Oct 28
dm vdo: don't refer to dedupe_context after releasing it
Linux
High7.8Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's dm vdo component can refer to a dedupe_context after releasing it. The input does not specify what an attacker could do or whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with dm vdo should check their installations; affected versions are not specified.