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-93274pinctrl: bcm2835: Don't remove an unregistered GPIO chip

Description

In the Linux kernel, the following vulnerability has been resolved: pinctrl: bcm2835: Don't remove an unregistered GPIO chip If the devm_pinctrl_register() function fails, bcm2835_pinctrl_probe() calls gpiochip_remove() before gpiochip_add_data() has registered the GPIO chip. This means that upon failure the gpio_chip.gpiodev is NULL resulting in a null pointer dereference inside the gpiochip_remove() function. Remove the unnecessary function call to gpiochip_remove(). No GPIO cleanup is required because the GPIO chip has not yet been registered. Without this change there is potential for a kernel panic upon registration failure

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 25 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.20% · top 90% of all CVEs (15 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 ba696b470839d70c6b8290c1f798bac7fb2a584c – < d428863ca8baa4e9eaf781266ac219b017dcf277
    • affected 79c6d4fa1be1fd0819c50ebb4dee101bbbc4d20e – < f494cfc254cd509d7cbc44b843e0a6602a520a33
    • affected 266423e60ea1b953fcc0cd97f3dad85857e434d1 – < dd6b1919e41d1260259c4505777be565fb3a7efd
    • affected 266423e60ea1b953fcc0cd97f3dad85857e434d1 – < 3b978fd0a3092b25561ac26bc1a87149fa981ddc
    • affected 266423e60ea1b953fcc0cd97f3dad85857e434d1 – < b8535f5c77cc61352d02a0c038a280127a8b8208
    • affected 266423e60ea1b953fcc0cd97f3dad85857e434d1 – < 68ea6dd23b732081826c36033835468383487864
    • affected 266423e60ea1b953fcc0cd97f3dad85857e434d1 – < 727f043d699ab0d5d87122c2177f2b45fbe58d35
    • affected 266423e60ea1b953fcc0cd97f3dad85857e434d1 – < 32711f77db0641e57fd96fdc013bf1286b9f2514
    • affected 75278f1aff5e14c904d3503c6f836c42a7afb441
    • affected 5.10.89 – < 5.10.270
    • affected 5.15.12 – < 5.15.221
    • affected 5.4.175 – < 5.5
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .