VulnerabilityPublished 17 Sep 2026Updated 30 Oct 2026

CVE-2026-92491: Linux kernel · firmware: arm_scmi: Roll back partial protocol table registration

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in ee556d118b11c6f5b60a32c1e84f366b336ac7d7 : update Linux kernel when convenient.

Data as of 30 Oct 2026, 13:04 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in ee556d118b11c6f5b60a32c1e84f366b336ac7d7, 826413b858ea2969e4c3e8197d0065efc47c6343, 456856a34906475fcf4b23879237103770dc7ef2 +3

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=6.1.191 <6.2	Fixed in ee556d118b11c6f5b60a32c1e84f366b336ac7d7 826413b858ea2969e4c3e8197d0065efc47c6343 456856a34906475fcf4b23879237103770dc7ef2 2224b622260ba590ab56ea1585d6bf7610be25b2 6.2 3fa8cabd2d8ed80dd0b818ca7fd410b591392ff6
LinuxLinux	Affected =6.9	Fixed in–

AI-suggested

A fix is available in Linux kernel version 6.2 and later, as well as specific commits identified by their hashes. Users should upgrade affected Linux kernel versions (>=6.1.191 <6.2 and =6.9) to 6.2 or later to remediate this issue.

Description

A vulnerability in the Linux kernel's arm_scmi firmware component involves improper cleanup during partial protocol table registration. When scmi_protocol_table_register() fails partway through registering entries, some earlier requests remain registered with dangling pointers to the driver's ID table after module unload. This can lead to use-after-free or invalid pointer dereferences. The issue is fixed by ensuring only successfully registered prefixes are unregistered in reverse order on failure, leaving failed and remaining entries untouched.

Impact

This vulnerability can cause dangling pointers after a failed module load, potentially leading to use-after-free conditions or invalid memory access within the kernel. Such issues can result in kernel instability or crashes. There is no indication of active exploitation in the wild.

Summary

The Linux kernel's arm_scmi firmware interface had a flaw in scmi_protocol_table_register() where partial failures during protocol table registration left earlier requests registered. Each request holds a pointer to the driver's ID table, so if a later entry fails, the earlier registered requests retain pointers to freed module storage, causing dangling pointers. The fix involves rolling back only the successfully registered prefixes in reverse order upon failure, avoiding leaving dangling pointers and preserving entries owned by other drivers.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 12:51 UTC

Technical details

References

Community reviews

Related threats