LiveActive security incident?Get immediate response
CVE Record

CVE-2024-43825: iio: Fix the sorting functionality in iio_gts_build_avail_time_table

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/6dd0d822-046c-4dd2-9532-79d7ab96ec05@gmail.com.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel flaw in industrial I/O timing-table handling can write beyond allocated memory when a timing value is zero. Kernel memory corruption could crash a system or potentially compromise confidentiality and integrity. The supplied CVSS score is 7.8, but exploitation requires local, low-privileged access.

Executive priority

Treat this as a high-priority kernel maintenance issue on Linux systems using industrial-I/O or sensor functionality, especially multi-user and locally accessible hosts. It is not supported as an emergency internet-scale threat because the supplied evidence requires local access and shows no active exploitation.

Technical view

The insertion logic in iio_gts_build_avail_time_table fails to advance correctly when time_us equals zero. Repeated element movement allows the loop index to grow beyond the destination array, causing out-of-bounds writes. Without zero values, the routine may copy entries without performing its intended sorting and deduplication.

Likely exposure

Exposure is limited to Linux systems containing and reaching the vulnerable IIO GTS code. Systems using relevant sensor or industrial-I/O drivers deserve priority. The supplied normalized version data is ambiguous, so exact affected and fixed releases must be confirmed through the system vendor and referenced stable commits.

Exploitation context

The CVSS vector describes local, low-complexity exploitation requiring low privileges and no user interaction. CISA KEV status is false, and the supplied evidence does not establish active exploitation or a public exploit. Practical reachability likely depends on kernel configuration, loaded drivers, and whether a zero timing value can reach the function.

Researcher notes

The critical condition is a zero time_us entry, which can make the insertion loop continue while incrementing its index and writing beyond bounds. Nonzero inputs also expose a correctness defect because sorting may not occur. The sources do not establish attacker-controlled reachability, reliable exploitation, or affected distribution-specific builds.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable referenced stable fix.
  • Confirm the fix commit for each deployed kernel branch before treating systems as remediated.
  • Prioritize systems using relevant IIO or sensor functionality and allowing untrusted local access.
  • If updating is delayed, follow distributor guidance and restrict untrusted local access; no specific workaround is supplied.

Validation and detection

  • Inventory running kernel packages and versions across affected Linux systems.
  • Check vendor advisories or changelogs for CVE-2024-43825 and the branch-specific fix commit.
  • Determine whether the vulnerable IIO GTS code and relevant drivers are built, loaded, or used.
  • After updating, verify the fixed kernel is running and survives reboot or replacement cycles.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-43825 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-43825Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux38416c28e16890b52fdd5eb73479299ec3f062f3, 38416c28e16890b52fdd5eb73479299ec3f062f3, 38416c28e16890b52fdd5eb73479299ec3f062f3unaffected
LinuxLinux6.4, 0, 6.6.44, 6.10.3, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.