Answer in brief
CVE-2024-53076 records a Unknown severity vulnerability in iio: gts-helper: Fix memory leaks for the error path of iio_gts_build_avail_scale_table(). 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 | 6.4 | Not reported |
| Linux/Linuxgeneric | >=38416c28e16890b52fdd5eb73479299ec3f062f3 <62c11896683129790b8f5ab6eb7e695818b0b723 || >=38416c28e16890b52fdd5eb73479299ec3f062f3 <b304362ce836968b803e5d4c5f84dcb51a7bf0f2 || >=38416c28e16890b52fdd5eb73479299ec3f062f3 <369f05688911b05216cfcd6ca74473bec87948d7 | 62c11896683129790b8f5ab6eb7e695818b0b723, b304362ce836968b803e5d4c5f84dcb51a7bf0f2, 369f05688911b05216cfcd6ca74473bec87948d7 |
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: iio: gts-helper: Fix memory leaks for the error path of iio_gts_build_avail_scale_table() If per_time_scales[i] or per_time_gains[i] kcalloc fails in the for loop of iio_gts_build_avail_scale_table(), the err_free_out will fail to call kfree() each time when i is reduced to 0, so all the per_time_scales[0] and per_time_gains[0] will not be freed, which will cause memory leaks. Fix it by checking if i >= 0.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-53076 records a Unknown severity vulnerability in iio: gts-helper: Fix memory leaks for the error path of iio_gts_build_avail_scale_table(). 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 | 6.4 | Not reported |
| Linux/Linuxgeneric | >=38416c28e16890b52fdd5eb73479299ec3f062f3 <62c11896683129790b8f5ab6eb7e695818b0b723 || >=38416c28e16890b52fdd5eb73479299ec3f062f3 <b304362ce836968b803e5d4c5f84dcb51a7bf0f2 || >=38416c28e16890b52fdd5eb73479299ec3f062f3 <369f05688911b05216cfcd6ca74473bec87948d7 | 62c11896683129790b8f5ab6eb7e695818b0b723, b304362ce836968b803e5d4c5f84dcb51a7bf0f2, 369f05688911b05216cfcd6ca74473bec87948d7 |
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: iio: gts-helper: Fix memory leaks for the error path of iio_gts_build_avail_scale_table() If per_time_scales[i] or per_time_gains[i] kcalloc fails in the for loop of iio_gts_build_avail_scale_table(), the err_free_out will fail to call kfree() each time when i is reduced to 0, so all the per_time_scales[0] and per_time_gains[0] will not be freed, which will cause memory leaks. Fix it by checking if i >= 0.
Quoted source text, attributed separately from HOL analysis.