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-2026-98971gpio: exar: initialize the ID before registering its cleanup

Description

In the Linux kernel, the following vulnerability has been resolved: gpio: exar: initialize the ID before registering its cleanup devm_add_action_or_reset() invokes the cleanup action immediately when registering the action fails. gpio_exar_probe() currently stores the allocated ID in exar_gpio only after registering the action, so that failure makes exar_devm_ida_free() release ID 0. If the allocated ID is nonzero, this leaks that ID and can free ID 0 belonging to another device. Store the ID before registering the cleanup action so both the immediate failure path and normal device teardown release the correct allocation.

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

  3. · 7 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (14 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 5300ebb695fa0672589ab191062392f686fca75d – < 0250acba81654b2ee50bde324ad72b3f0c04d0bd
    • affected 5300ebb695fa0672589ab191062392f686fca75d – < 88b9c4bbf83d940ab672956e5af921215905dcb4
    • affected 5300ebb695fa0672589ab191062392f686fca75d – < bf3d841ef12fcbec4458e2750956b738b043a226
    • affected 5300ebb695fa0672589ab191062392f686fca75d – < b78c114600ae3df90c083c72c290437b068577c8
    • affected 5300ebb695fa0672589ab191062392f686fca75d – < 01318927a9055136c207399eeb36ce07becac179
    • affected 5300ebb695fa0672589ab191062392f686fca75d – < f7ec4dbd2a073dd53b6349be1c586fe8580dd6b2
    • affected 5300ebb695fa0672589ab191062392f686fca75d – < 4d69e74034b208588636ecc177e0dd43a7696af3
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .