Answer in brief
CVE-2022-50758 records a High severity (CVSS 7.8) vulnerability in staging: vt6655: fix potential memory leak. 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.
CVSS is 7.8. 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 | >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <e741e38aa98704fbb959650ecd270b71b2670680 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <16a45e78a687eb6c69acc4e62b94b6508b0bfbda || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <1b3cebeca99e8e0aa4fa57faac8dbf41e967317a || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <ff8551d411f12b5abc5ca929ab87643afa8a9588 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <fb5f569bcda8f87bd47d8030bfae343d757fa3ea || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <cfdf139258614ef65b0f68b857ada5328fb7c0e5 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <c8ff91535880d41b49699b3829fb6151942de29e | e741e38aa98704fbb959650ecd270b71b2670680, 16a45e78a687eb6c69acc4e62b94b6508b0bfbda, 1b3cebeca99e8e0aa4fa57faac8dbf41e967317a, ff8551d411f12b5abc5ca929ab87643afa8a9588, fb5f569bcda8f87bd47d8030bfae343d757fa3ea, cfdf139258614ef65b0f68b857ada5328fb7c0e5, c8ff91535880d41b49699b3829fb6151942de29e |
| Linux/Linuxgeneric | 4.18 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: staging: vt6655: fix potential memory leak In function device_init_td0_ring, memory is allocated for member td_info of priv->apTD0Rings[i], with i increasing from 0. In case of allocation failure, the memory is freed in reversed order, with i decreasing to 0. However, the case i=0 is left out and thus memory is leaked. Modify the memory freeing loop to include the case i=0.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-50758 records a High severity (CVSS 7.8) vulnerability in staging: vt6655: fix potential memory leak. 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.
CVSS is 7.8. 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 | >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <e741e38aa98704fbb959650ecd270b71b2670680 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <16a45e78a687eb6c69acc4e62b94b6508b0bfbda || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <1b3cebeca99e8e0aa4fa57faac8dbf41e967317a || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <ff8551d411f12b5abc5ca929ab87643afa8a9588 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <fb5f569bcda8f87bd47d8030bfae343d757fa3ea || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <cfdf139258614ef65b0f68b857ada5328fb7c0e5 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <c8ff91535880d41b49699b3829fb6151942de29e | e741e38aa98704fbb959650ecd270b71b2670680, 16a45e78a687eb6c69acc4e62b94b6508b0bfbda, 1b3cebeca99e8e0aa4fa57faac8dbf41e967317a, ff8551d411f12b5abc5ca929ab87643afa8a9588, fb5f569bcda8f87bd47d8030bfae343d757fa3ea, cfdf139258614ef65b0f68b857ada5328fb7c0e5, c8ff91535880d41b49699b3829fb6151942de29e |
| Linux/Linuxgeneric | 4.18 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: staging: vt6655: fix potential memory leak In function device_init_td0_ring, memory is allocated for member td_info of priv->apTD0Rings[i], with i increasing from 0. In case of allocation failure, the memory is freed in reversed order, with i decreasing to 0. However, the case i=0 is left out and thus memory is leaked. Modify the memory freeing loop to include the case i=0.
Quoted source text, attributed separately from HOL analysis.