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-92482pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip

Description

In the Linux kernel, the following vulnerability has been resolved: pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip The gpio_chip is allocated with device-managed memory but registered with the non-managed gpiochip_add_data(). This was harmless while the drivers were built-in, but once they can be built as modules and unbound/rmmod'd, devm frees the gpio_chip's memory while it is still registered, causing a use-after-free. Register it with devm_gpiochip_add_data() so it shares the same device-managed lifecycle, which also lets the manual gpiochip_remove() error paths go away.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 43 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 88% of all CVEs (12 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 a6df410d420aa4ff316797d352f69e7ebae5ff98 – < 13a25cb4f0f0863afded5e915cb3bceede221426
    • affected a6df410d420aa4ff316797d352f69e7ebae5ff98 – < dc6e5d802c88468290fee8826dd3a54cf58da25a
    • affected a6df410d420aa4ff316797d352f69e7ebae5ff98 – < 2490528a90a26f408ec3e95f865bad35454f9ff3
    • affected a6df410d420aa4ff316797d352f69e7ebae5ff98 – < 01b5fcdc30c0ab35af960b60508eae1f7f7d32fd
    • affected a6df410d420aa4ff316797d352f69e7ebae5ff98 – < b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b
    • affected a6df410d420aa4ff316797d352f69e7ebae5ff98 – < 9c650317ba553d297f3fc5f0ae40ec53d86f9dab
  • Linux · Linux

    • affected 4.1
    • unaffected < 4.1
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .