Answer in brief
CVE-2024-50091 records a Unknown severity vulnerability in dm vdo: don't refer to dedupe_context after releasing it. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=cfaf07fae7a262865a67b6010eef3bc0a1ae50b2 <63ef073084c67878d7a92e15ad055172da3f05a3 || >=cfaf07fae7a262865a67b6010eef3bc0a1ae50b2 <0808ebf2f80b962e75741a41ced372a7116f1e26 | 63ef073084c67878d7a92e15ad055172da3f05a3, 0808ebf2f80b962e75741a41ced372a7116f1e26 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Nov 5, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-50091 records a Unknown severity vulnerability in dm vdo: don't refer to dedupe_context after releasing it. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=cfaf07fae7a262865a67b6010eef3bc0a1ae50b2 <63ef073084c67878d7a92e15ad055172da3f05a3 || >=cfaf07fae7a262865a67b6010eef3bc0a1ae50b2 <0808ebf2f80b962e75741a41ced372a7116f1e26 | 63ef073084c67878d7a92e15ad055172da3f05a3, 0808ebf2f80b962e75741a41ced372a7116f1e26 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Nov 5, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.