CVE-2026-92490: firmware: arm_scmi: Unrequest devices if driver registration fails
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.21% (FIRST EPSS).
- Fixed version: Linux Linux 06e65e07a1bcb39a1ebc8bb89a981f8e07900497, 35a36fbbc985135f0d35a89d7f9d035ffc499d6e, 4520d4a1db37198756ad23568e36cdf091b6ffff.
Low priority for now. Upgrade to Linux Linux 06e65e07a1bcb39a1ebc8bb89a981f8e07900497, 35a36fbbc985135f0d35a89d7f9d035ffc499d6e, 4520d4a1db37198756ad23568e36cdf091b6ffff 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: firmware: arm_scmi: Unrequest devices if driver registration fails scmi_driver_register() requests protocol devices before registering the driver. If driver_register() fails, those requests remain in the global IDR and retain pointers to the module's ID table. Once the failed module load releases that storage, later request matching or SCMI device creation can dereference the stale pointers. Unrequest the complete protocol table before returning the registration failure. At this point table registration succeeded, so every entry is owned by the current registration attempt.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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
- 6.3affected
- a6fe96b2e371d5fd300cca24459cdcf471c2c741 and later · before 35a36fbbc985135f0d35a89d7f9d035ffc499d6eaffected · git
- d3cd7c525fd2ecce3a6c963f314969a54783d211 and later · before 524e57035af2d32498af9dd8fa6fdc92fcc8f80aaffected · git
- d3cd7c525fd2ecce3a6c963f314969a54783d211 and later · before 06e65e07a1bcb39a1ebc8bb89a981f8e07900497affected · git
- d3cd7c525fd2ecce3a6c963f314969a54783d211 and later · before a76b20b1f03099204db29b90e1024fe1c2b2cdd7affected · git
- d3cd7c525fd2ecce3a6c963f314969a54783d211 and later · before 4520d4a1db37198756ad23568e36cdf091b6ffffaffected · git
- d3cd7c525fd2ecce3a6c963f314969a54783d211 and later · before 9f7cd6a62aa754ed6b48cbd5d50de40add1bcc86affected · git
- before 6.3not affected · semver
- 6.6.157 and later · up to and including 6.6.*not affected · semver
- 6.12.110 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-92488Sep 17, 2026 · RDMA/erdma: complete object teardown when the destroy command fails28Monitor
- ← EarlierCVE-2026-92489Sep 17, 2026 · xfrm: Fix skb double-free in xfrm_dev_direct_output()39Monitor
- Later →CVE-2026-92491Sep 17, 2026 · firmware: arm_scmi: Roll back partial protocol table registration0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 06e65e07a1bcb39a1ebc8bb89a981f8e07900497 | Vendor (CNA) |
| Linux Linux | 35a36fbbc985135f0d35a89d7f9d035ffc499d6e | Vendor (CNA) |
| Linux Linux | 4520d4a1db37198756ad23568e36cdf091b6ffff | Vendor (CNA) |
| Linux Linux | 524e57035af2d32498af9dd8fa6fdc92fcc8f80a | Vendor (CNA) |
| Linux Linux | 9f7cd6a62aa754ed6b48cbd5d50de40add1bcc86 | Vendor (CNA) |
| Linux Linux | a76b20b1f03099204db29b90e1024fe1c2b2cdd7 | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package 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.
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 researchersFinders, 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/35a36fbbc985135f0d35a89d7f9d035ffc499d6e
- git.kernel.org/stable/c/4520d4a1db37198756ad23568e36cdf091b6ffff
- git.kernel.org/stable/c/524e57035af2d32498af9dd8fa6fdc92fcc8f80a
- git.kernel.org/stable/c/9f7cd6a62aa754ed6b48cbd5d50de40add1bcc86
- git.kernel.org/stable/c/a76b20b1f03099204db29b90e1024fe1c2b2cdd7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.