Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 21 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-44931, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.25% · top 84% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 – < 18504710442671b02d00e6db9804a0ad26c5a479
    • affected 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 – < 9ae2d8e75b741dbcb0da374753f972410e83b5f3
    • affected 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 – < 9d682e89c44bd5819b01f3fbb45a8e3681a4b6d0
    • affected 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 – < c65ab97efcd438cb4e9f299400f2ea55251f3a67
    • affected 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 – < 672c19165fc96dfad531a5458e0b3cdab414aae4
    • affected 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 – < 1b955f786a4bcde8c0ccb2b7d519def2acb6f3cc
    • affected 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 – < d776c0486b03a5c4afca65b8ff44573592bf93bb
    • affected 521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 – < d795848ecce24a75dfd46481aee066ae6fe39775
  • Linux · Linux

    • affected 4.6
    • unaffected < 4.6
    • unaffected 4.19.323 – ≤ 4.19.*
    • unaffected 5.4.285 – ≤ 5.4.*
    • unaffected 5.10.227 – ≤ 5.10.*
    • unaffected 5.15.168 – ≤ 5.15.*
    • unaffected 6.1.112 – ≤ 6.1.*
    • unaffected 6.6.46 – ≤ 6.6.*
    • unaffected 6.10.5 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-44931 badge
[![CVE-2024-44931](https://cveledger.app/badge/CVE-2024-44931.svg)](https://cveledger.app/cve/CVE-2024-44931)

Record last updated .