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

Published Aug 26, 2024
·
Updated

gpio: prevent potential speculation leaks in gpiodevicegetdesc()

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

7 affected componentsFixes available
Linux Linux kernel<6.6.46
Linux Linux kernel>=6.7<6.10.5
debian/linux<=5.10.223-1
5.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Microsoft cbl2 kernel 5.15.180.1-1
Microsoft cbl2 kernel 5.15.176.3-1<5.15.176.3-1
5.15.176.3-1
Microsoft cbl2 kernel 5.15.180.1-1<5.15.176.3-1
5.15.176.3-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.129-1~deb11u1
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.15.176.3-1
  4. Configuration

    Update the Linux kernel gpio code so that the user-provided offset used as an index in gpio_device_get_desc() is sanitized by using array_index_nospec(), mitigating speculative information leaks when userspace calls gpio_ioctl() with an out-of-range offset.

    Linux kernel gpio offset sanitization in gpio_device_get_desc() = use array_index_nospec()

Event History

Aug 26, 2024
CVE Published
via MITRE·10:11 AM
Data Sourced
via MITRE·10:11 AM
Description
Data Sourced
via NVD·11:15 AM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Red Hat·11:21 AM
DescriptionSeverityAffected Software
Feb 26, 2025
Data Sourced
via Launchpad·07:27 PM
Description
May 5, 2025
Data Sourced
via Ubuntu·07:40 PM
RemedyDescriptionSeverityAffected Software
Sep 4, 2025
Data Sourced
via Microsoft·03:05 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·03:05 AM
Affected Software
Updated
via Microsoft·03:05 AM
Severity
Updated
via Microsoft·03:05 AM
Affected Software
Updated
via Microsoft·03:05 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2024-44931?

CVE-2024-44931 has been rated as a high severity vulnerability due to its potential for speculative information leaks.

2

How do I fix CVE-2024-44931?

To fix CVE-2024-44931, upgrade the Linux kernel to versions 6.6.46 or later, or ensure you are running a patched version of affected Linux distributions.

3

Who is affected by CVE-2024-44931?

CVE-2024-44931 affects users of specific versions of the Linux kernel, particularly those in the 6.7 to 6.10.5 range and below 6.1.123.

4

What is the impact of CVE-2024-44931 on systems?

The impact of CVE-2024-44931 includes the possible exposure of sensitive data through speculative reads triggered by user actions.

5

Is there a workaround for CVE-2024-44931?

Currently, the best approach for CVE-2024-44931 is to apply the available patches rather than relying on a workaround.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203