Answer in brief
CVE-2024-43825 records a Unknown severity vulnerability in iio: Fix the sorting functionality in iio_gts_build_avail_time_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 | >=38416c28e16890b52fdd5eb73479299ec3f062f3 <31ff8464ef540785344994986a010031410f9ff3 || >=38416c28e16890b52fdd5eb73479299ec3f062f3 <b5046de32fd1532c3f67065197fc1da82f0b5193 || >=38416c28e16890b52fdd5eb73479299ec3f062f3 <5acc3f971a01be48d5ff4252d8f9cdb87998cdfb | 31ff8464ef540785344994986a010031410f9ff3, b5046de32fd1532c3f67065197fc1da82f0b5193, 5acc3f971a01be48d5ff4252d8f9cdb87998cdfb |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Aug 17, 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: Fix the sorting functionality in iio_gts_build_avail_time_table The sorting in iio_gts_build_avail_time_table is not working as intended. It could result in an out-of-bounds access when the time is zero. Here are more details: 1. When the gts->itime_table[i].time_us is zero, e.g., the time sequence is `3, 0, 1`, the inner for-loop will not terminate and do out-of-bound writes. This is because once `times[j] > new`, the value `new` will be added in the current position and the `times[j]` will be moved to `j+1` position, which makes the if-condition always hold. Meanwhile, idx will be added one, making the loop keep running without termination and out-of-bound write. 2. If none of the gts->itime_table[i].time_us is zero, the elements will just be copied without being sorted as described in the comment "Sort times from all tables to one and remove duplicates". For more details, please refer to https://lore.kernel.org/all/[email protected].
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-43825 records a Unknown severity vulnerability in iio: Fix the sorting functionality in iio_gts_build_avail_time_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 | >=38416c28e16890b52fdd5eb73479299ec3f062f3 <31ff8464ef540785344994986a010031410f9ff3 || >=38416c28e16890b52fdd5eb73479299ec3f062f3 <b5046de32fd1532c3f67065197fc1da82f0b5193 || >=38416c28e16890b52fdd5eb73479299ec3f062f3 <5acc3f971a01be48d5ff4252d8f9cdb87998cdfb | 31ff8464ef540785344994986a010031410f9ff3, b5046de32fd1532c3f67065197fc1da82f0b5193, 5acc3f971a01be48d5ff4252d8f9cdb87998cdfb |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Aug 17, 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: Fix the sorting functionality in iio_gts_build_avail_time_table The sorting in iio_gts_build_avail_time_table is not working as intended. It could result in an out-of-bounds access when the time is zero. Here are more details: 1. When the gts->itime_table[i].time_us is zero, e.g., the time sequence is `3, 0, 1`, the inner for-loop will not terminate and do out-of-bound writes. This is because once `times[j] > new`, the value `new` will be added in the current position and the `times[j]` will be moved to `j+1` position, which makes the if-condition always hold. Meanwhile, idx will be added one, making the loop keep running without termination and out-of-bound write. 2. If none of the gts->itime_table[i].time_us is zero, the elements will just be copied without being sorted as described in the comment "Sort times from all tables to one and remove duplicates". For more details, please refer to https://lore.kernel.org/all/[email protected].
Quoted source text, attributed separately from HOL analysis.