LiveActive security incident?Get immediate response
CVE Record

CVE-2024-44931: gpio: prevent potential speculation leaks in gpio_device_get_desc()

In the Linux kernel, the following vulnerability has been resolved: gpio: prevent potential speculation leaks in gpio_device_get_desc() Userspace may trigger a speculative read of an address outside the gpio descriptor array. Users can do that by calling gpio_ioctl() with an offset out of range. Offset is copied from user and then used as an array index to get the gpio descriptor without sanitization in gpio_device_get_desc(). This change ensures that the offset is sanitized by using array_index_nospec() to mitigate any possibility of speculative information leaks. This bug was discovered and resolved using Coverity Static Analysis Security Testing (SAST) by Synopsys, Inc.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-44931 is a Linux kernel GPIO issue where a local userspace caller may cause speculative access outside a GPIO descriptor array. The concern is potential information leakage through CPU speculation, not direct remote takeover. No CVSS score or KEV listing is provided in the bundle.

Executive priority

Prioritize through normal kernel security maintenance unless the environment has multi-tenant local users, containers, or workloads with GPIO access. Lack of KEV status and missing CVSS reduce urgency, but kernel speculative leaks still merit timely patching.

Technical view

In gpio_device_get_desc(), an offset copied from userspace could be used as an array index before speculation-safe sanitization. The kernel fix applies array_index_nospec() to reduce speculative out-of-bounds reads when gpio_ioctl() receives an out-of-range offset.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel branches where local users or processes can reach GPIO ioctl paths. Internet-facing exposure is not indicated by the provided sources.

Exploitation context

The bundle does not show active exploitation, public weaponization, or CISA KEV inclusion. The described trigger is local userspace interaction with gpio_ioctl(), and the impact is a potential speculative information leak.

Researcher notes

Evidence supports a local, speculation-related bounds-sanitization flaw in Linux GPIO handling. The source bundle does not provide CVSS, CWE, exploit reports, or detailed distro package matrices beyond referenced kernel commits and Debian LTS announcements.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable GPIO fix.
  • Use distribution security updates where available, including Debian LTS kernel advisories.
  • If immediate patching is unavailable, check vendor guidance for supported mitigations.
  • Limit unnecessary local access to GPIO device interfaces where operationally feasible.

Validation and detection

  • Inventory Linux kernel versions against the affected branches in the CVE record.
  • Confirm installed kernel includes the relevant stable commit for its branch.
  • Review distribution advisories for patched package versions and reboot requirements.
  • Check whether untrusted local workloads can access GPIO device interfaces.
Prepared
Confidence
medium
Sources
12

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-44931 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
2ADP providers
11Source links

SSVC decision data

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

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
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux521a2ad6f862a28e2e43cb3e254a26bf0f9452e9, 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9, 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9, 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9, 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9, 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9, 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9, 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9unaffected
LinuxLinux4.6, 0, 4.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.112, 6.6.46, 6.10.5, 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.