LiveActive security incident?Get immediate response
CVE Record

CVE-2024-57908: iio: imu: kmx61: fix information leak in triggered buffer

In the Linux kernel, the following vulnerability has been resolved: iio: imu: kmx61: fix information leak in triggered buffer The 'buffer' local array is used to push data to user space from a triggered buffer, but it does not set values for inactive channels, as it only uses iio_for_each_active_channel() to assign new values. Initialize the array to zero before using it to avoid pushing uninitialized information to userspace.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-57908 is a Linux kernel issue in the KMX61 IMU sensor driver. A local user who can access the relevant sensor buffer may receive uninitialized kernel memory in user space. The business risk is mainly data exposure on systems with this hardware or driver enabled.

Executive priority

Prioritize patching for laptops, embedded devices, industrial systems, or shared Linux hosts with motion-sensor hardware. Risk is narrower than internet-facing vulnerabilities, but kernel memory disclosure can support broader compromise chains.

Technical view

The kmx61 Industrial I/O triggered buffer filled only active channels, leaving inactive channel slots uninitialized before pushing the buffer to user space. The kernel fix zero-initializes the local array before use. CVSS 3.1 is 7.1, with local access and low privileges required.

Likely exposure

Exposure is likely limited to Linux systems using or loading the kmx61 IIO IMU driver and allowing local users to read triggered buffers. Distribution kernels may differ due to backports, so package-level vendor status matters.

Exploitation context

The provided sources do not show active exploitation, and KEV is false. The CVSS vector indicates local, low-privilege exploitation without user interaction. No remote attack path is supported by the source bundle.

Researcher notes

Focus validation on driver reachability, IIO triggered-buffer access, and vendor backport status. The source bundle names the root cause and fix pattern but does not provide exploit evidence or complete distribution-specific affected ranges.

Mitigation direction

  • Update to a vendor kernel containing the kmx61 buffer initialization fix.
  • Use distribution security advisories, including Debian LTS notices where applicable.
  • Disable or unload the kmx61 driver if unused and operationally safe.
  • Restrict local access to affected sensor interfaces where feasible.

Validation and detection

  • Inventory Linux kernels and identify systems with the kmx61 driver present or loaded.
  • Confirm whether vendor packages include one of the referenced stable fixes.
  • Check Debian LTS advisory applicability for Debian-based affected systems.
  • Review IIO device permissions for unnecessary local user access.
Prepared
Confidence
medium
Sources
11

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.

cwe · low confidence lookup

CWE-908: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-57908 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.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
2ADP providers
10Source 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.1CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H1.85.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc3a23ecc0901f624b681bbfbc4829766c5aa3070, c3a23ecc0901f624b681bbfbc4829766c5aa3070, c3a23ecc0901f624b681bbfbc4829766c5aa3070, c3a23ecc0901f624b681bbfbc4829766c5aa3070, c3a23ecc0901f624b681bbfbc4829766c5aa3070, c3a23ecc0901f624b681bbfbc4829766c5aa3070, c3a23ecc0901f624b681bbfbc4829766c5aa3070unaffected
LinuxLinux4.0, 0, 5.4.290, 5.10.234, 5.15.177, 6.1.125, 6.6.72, 6.12.10, 6.13affected
Weakness

CWE details

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

CWE-908 · source CWE mapping

Use of Uninitialized Resource

Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.