firmware: arm_scmi: Avoid IDR updates while cleaning channels
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 431c6b872ba7fedcc5a3afb0ec3517db4d95d088, 54e5a4f7d83db4552d963d0785be32d9df680dcd, aed24a3c63920539e9de7fbfe7929a2e7c888cd2; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 431c6b872ba7fedcc5a3afb0ec3517db4d95d088, 54e5a4f7d83db4552d963d0785be32d9df680dcd, aed24a3c63920539e9de7fbfe7929a2e7c888cd2; azl3 kernel 6.6.152.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
In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Avoid IDR updates while cleaning channels scmi_cleanup_channels() walks the TX/RX channel IDRs with idr_for_each() to free transport resources and destroy the dedicated transport devices before calling idr_destroy(). The destroy callback removed each entry from the same IDR being walked. That is not needed for this cleanup path, and it is unsafe because idr_for_each() has not advanced its radix-tree iterator while the callback is running. Removing the current entry from the callback can invalidate the iterator state. The callback also cannot be protected by rcu_read_lock(), because scmi_device_destroy() may sleep. Leave IDR teardown to the following idr_destroy() call and keep the callback limited to device destruction.
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- EPSS
- 0.2% · 9th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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
—
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
- 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 and later · before aed24a3c63920539e9de7fbfe7929a2e7c888cd2affected · git
- 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 and later · before 431c6b872ba7fedcc5a3afb0ec3517db4d95d088affected · git
- 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 and later · before 54e5a4f7d83db4552d963d0785be32d9df680dcdaffected · git
- 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 and later · before bab26acebe55e8ad3ab545abda72faa7ca28c477affected · git
- 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 and later · before c38b1e19485aaa820e52cfe162525a8af67563daaffected · 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
- 6.18.52 and later · up to and including 6.18.*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 |
| openSUSE:Tumbleweed | kernel-source | before 7.2.9-1.1 | 7.2.9-1.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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 431c6b872ba7fedcc5a3afb0ec3517db4d95d088 | Vendor (CNA) |
| Linux Linux | 54e5a4f7d83db4552d963d0785be32d9df680dcd | Vendor (CNA) |
| Linux Linux | aed24a3c63920539e9de7fbfe7929a2e7c888cd2 | Vendor (CNA) |
| Linux Linux | bab26acebe55e8ad3ab545abda72faa7ca28c477 | Vendor (CNA) |
| Linux Linux | c38b1e19485aaa820e52cfe162525a8af67563da | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| 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) |
| opensuse:kernel-source | 7.2.9-1.1 · openSUSE:Tumbleweed | 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
- git.kernel.org/stable/c/431c6b872ba7fedcc5a3afb0ec3517db4d95d088
- git.kernel.org/stable/c/54e5a4f7d83db4552d963d0785be32d9df680dcd
- git.kernel.org/stable/c/aed24a3c63920539e9de7fbfe7929a2e7c888cd2
- git.kernel.org/stable/c/bab26acebe55e8ad3ab545abda72faa7ca28c477
- git.kernel.org/stable/c/c38b1e19485aaa820e52cfe162525a8af67563da
Vendor advisories and official records. Exploit/PoC links are deliberately left out.