Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-93274: pinctrl: bcm2835: Don't remove an unregistered GPIO chip

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Fixed version: Linux Linux 32711f77db0641e57fd96fdc013bf1286b9f2514, 3b978fd0a3092b25561ac26bc1a87149fa981ddc, 5.10.270; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.157.1-1.

Low priority for now. Upgrade to Linux Linux 32711f77db0641e57fd96fdc013bf1286b9f2514, 3b978fd0a3092b25561ac26bc1a87149fa981ddc, 5.10.270; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

—No exploit Fix available
Published
Sep 24, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-93274

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 75278f1aff5e14c904d3503c6f836c42a7afb441, 5.16affected
    • ba696b470839d70c6b8290c1f798bac7fb2a584c and later · before d428863ca8baa4e9eaf781266ac219b017dcf277affected · git
    • 79c6d4fa1be1fd0819c50ebb4dee101bbbc4d20e and later · before f494cfc254cd509d7cbc44b843e0a6602a520a33affected · git
    • 266423e60ea1b953fcc0cd97f3dad85857e434d1 and later · before dd6b1919e41d1260259c4505777be565fb3a7efdaffected · git
    • 266423e60ea1b953fcc0cd97f3dad85857e434d1 and later · before 3b978fd0a3092b25561ac26bc1a87149fa981ddcaffected · git
    • 266423e60ea1b953fcc0cd97f3dad85857e434d1 and later · before b8535f5c77cc61352d02a0c038a280127a8b8208affected · git
    • 266423e60ea1b953fcc0cd97f3dad85857e434d1 and later · before 68ea6dd23b732081826c36033835468383487864affected · git
    • 266423e60ea1b953fcc0cd97f3dad85857e434d1 and later · before 727f043d699ab0d5d87122c2177f2b45fbe58d35affected · git
    • 266423e60ea1b953fcc0cd97f3dad85857e434d1 and later · before 32711f77db0641e57fd96fdc013bf1286b9f2514affected · git
    • 5.10.89 and later · before 5.10.270affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-93272Sep 24, 2026 · remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3
    0Monitor
  • ← EarlierCVE-2026-93273Sep 24, 2026 · regulator: tps6594: Fix device node reference leaks in multiphase loop
    0Monitor
  • Later →CVE-2026-93275Sep 24, 2026 · perf/x86/intel/pt: Fix stop/start with no update
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux32711f77db0641e57fd96fdc013bf1286b9f2514Vendor (CNA)
Linux Linux3b978fd0a3092b25561ac26bc1a87149fa981ddcVendor (CNA)
Linux Linux5.10.270Vendor (CNA)
Linux Linux5.15.221Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux68ea6dd23b732081826c36033835468383487864Vendor (CNA)
Linux Linux727f043d699ab0d5d87122c2177f2b45fbe58d35Vendor (CNA)
Linux Linuxb8535f5c77cc61352d02a0c038a280127a8b8208Vendor (CNA)
Linux Linuxd428863ca8baa4e9eaf781266ac219b017dcf277Vendor (CNA)
Linux Linuxdd6b1919e41d1260259c4505777be565fb3a7efdVendor (CNA)
Linux Linuxf494cfc254cd509d7cbc44b843e0a6602a520a33Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records