Answer in brief
CVE-2024-50264 records a Unknown severity vulnerability in vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans. 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.
Answer in brief
CVE-2024-50264 records a Unknown severity vulnerability in vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans. 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 | >=06a8fc78367d070720af960dcecec917d3ae5f3b <5f092a4271f6dccf88fe0d132475a17b69ef71df || >=06a8fc78367d070720af960dcecec917d3ae5f3b <fd8ae346692a56b4437d626c5460c7104980f389 || >=06a8fc78367d070720af960dcecec917d3ae5f3b <eb1bdcb7dfc30b24495ee4c5533af0ed135cb5f1 || >=06a8fc78367d070720af960dcecec917d3ae5f3b <2a6a4e69f255b7aed17f93995691ab4f0d3c2203 || >=06a8fc78367d070720af960dcecec917d3ae5f3b <44d29897eafd0e1196453d3003a4d5e0b968eeab || >=06a8fc78367d070720af960dcecec917d3ae5f3b <b110196fec44fe966952004bd426967c2a8fd358 || >=06a8fc78367d070720af960dcecec917d3ae5f3b <5f970935d09934222fdef3d0e20c648ea7a963c1 || >=06a8fc78367d070720af960dcecec917d3ae5f3b <6ca575374dd9a507cdd16dfa0e78c2e9e20bd05f | 5f092a4271f6dccf88fe0d132475a17b69ef71df, fd8ae346692a56b4437d626c5460c7104980f389, eb1bdcb7dfc30b24495ee4c5533af0ed135cb5f1, 2a6a4e69f255b7aed17f93995691ab4f0d3c2203, 44d29897eafd0e1196453d3003a4d5e0b968eeab, b110196fec44fe966952004bd426967c2a8fd358, 5f970935d09934222fdef3d0e20c648ea7a963c1, 6ca575374dd9a507cdd16dfa0e78c2e9e20bd05f |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
Nov 19, 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: vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans During loopback communication, a dangling pointer can be created in vsk->trans, potentially leading to a Use-After-Free condition. This issue is resolved by initializing vsk->trans to NULL.
Quoted source text, attributed separately from HOL analysis.
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 | >=06a8fc78367d070720af960dcecec917d3ae5f3b <5f092a4271f6dccf88fe0d132475a17b69ef71df || >=06a8fc78367d070720af960dcecec917d3ae5f3b <fd8ae346692a56b4437d626c5460c7104980f389 || >=06a8fc78367d070720af960dcecec917d3ae5f3b <eb1bdcb7dfc30b24495ee4c5533af0ed135cb5f1 || >=06a8fc78367d070720af960dcecec917d3ae5f3b <2a6a4e69f255b7aed17f93995691ab4f0d3c2203 || >=06a8fc78367d070720af960dcecec917d3ae5f3b <44d29897eafd0e1196453d3003a4d5e0b968eeab || >=06a8fc78367d070720af960dcecec917d3ae5f3b <b110196fec44fe966952004bd426967c2a8fd358 || >=06a8fc78367d070720af960dcecec917d3ae5f3b <5f970935d09934222fdef3d0e20c648ea7a963c1 || >=06a8fc78367d070720af960dcecec917d3ae5f3b <6ca575374dd9a507cdd16dfa0e78c2e9e20bd05f | 5f092a4271f6dccf88fe0d132475a17b69ef71df, fd8ae346692a56b4437d626c5460c7104980f389, eb1bdcb7dfc30b24495ee4c5533af0ed135cb5f1, 2a6a4e69f255b7aed17f93995691ab4f0d3c2203, 44d29897eafd0e1196453d3003a4d5e0b968eeab, b110196fec44fe966952004bd426967c2a8fd358, 5f970935d09934222fdef3d0e20c648ea7a963c1, 6ca575374dd9a507cdd16dfa0e78c2e9e20bd05f |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
Nov 19, 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: vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans During loopback communication, a dangling pointer can be created in vsk->trans, potentially leading to a Use-After-Free condition. This issue is resolved by initializing vsk->trans to NULL.
Quoted source text, attributed separately from HOL analysis.