CVE-2026-89452: iommu/msm: Unwind probe state on registration failure
Noroxi assessment
Priority: Monitor (action score 33/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.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 51424c14dbdadc8c2ad4abf842265a50f69d78aa, 51e37f9179387b6e3fa64a3d3b4fece1a38b3a02, 535a200220ca2c83bc8bf54bd2cbe045d6ee70c4.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 51424c14dbdadc8c2ad4abf842265a50f69d78aa, 51e37f9179387b6e3fa64a3d3b4fece1a38b3a02, 535a200220ca2c83bc8bf54bd2cbe045d6ee70c4 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: iommu/msm: Unwind probe state on registration failure msm_iommu_probe() adds its devm-managed IOMMU object to qcom_iommu_devices before adding the IOMMU sysfs device and registering it with the IOMMU core. If iommu_device_sysfs_add() fails, probe returns with the object still on qcom_iommu_devices. The driver core then releases the devm allocation, leaving a dangling list entry that later list walks may dereference. If iommu_device_register() fails, the same dangling list entry remains and the sysfs device is left registered as well. Unwind the sysfs device and global list entry in reverse setup order on the corresponding failure paths.
- Published
- Sep 11, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
- 4.11affected
- 42df43b36163ed7d0ab13992e411093252903273 and later · before 51424c14dbdadc8c2ad4abf842265a50f69d78aaaffected · git
- 42df43b36163ed7d0ab13992e411093252903273 and later · before 6a1ae472113762f794682229a0f233f1ee0f69a4affected · git
- 42df43b36163ed7d0ab13992e411093252903273 and later · before 51e37f9179387b6e3fa64a3d3b4fece1a38b3a02affected · git
- 42df43b36163ed7d0ab13992e411093252903273 and later · before f532401be9312ecd166f616bb74a65b0b4c150faaffected · git
- 42df43b36163ed7d0ab13992e411093252903273 and later · before 7f7074a886c4a93e3d12076ce60a510a1ebe400caffected · git
- 42df43b36163ed7d0ab13992e411093252903273 and later · before 535a200220ca2c83bc8bf54bd2cbe045d6ee70c4affected · git
- before 4.11not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*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 | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.2.7-1.1 | 7.2.7-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
Published before and after this one in the same product
- ← EarlierCVE-2026-89450Sep 11, 2026 · iommu/tegra241-cmdqv: Reject a vSID wider than the SID_MATCH field35Monitor
- ← EarlierCVE-2026-89451Sep 11, 2026 · iommu/sva: Set handle->dev before the SVA handle is visible0Monitor
- Later →CVE-2026-89453Sep 11, 2026 · iommu/amd: Put PCI device after handling PPR faults0Monitor
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 | 51424c14dbdadc8c2ad4abf842265a50f69d78aa | Vendor (CNA) |
| Linux Linux | 51e37f9179387b6e3fa64a3d3b4fece1a38b3a02 | Vendor (CNA) |
| Linux Linux | 535a200220ca2c83bc8bf54bd2cbe045d6ee70c4 | Vendor (CNA) |
| Linux Linux | 6a1ae472113762f794682229a0f233f1ee0f69a4 | Vendor (CNA) |
| Linux Linux | 7f7074a886c4a93e3d12076ce60a510a1ebe400c | Vendor (CNA) |
| Linux Linux | f532401be9312ecd166f616bb74a65b0b4c150fa | Vendor (CNA) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 7.2.7-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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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/51e37f9179387b6e3fa64a3d3b4fece1a38b3a02
- git.kernel.org/stable/c/535a200220ca2c83bc8bf54bd2cbe045d6ee70c4
- git.kernel.org/stable/c/6a1ae472113762f794682229a0f233f1ee0f69a4
- git.kernel.org/stable/c/7f7074a886c4a93e3d12076ce60a510a1ebe400c
- git.kernel.org/stable/c/f532401be9312ecd166f616bb74a65b0b4c150fa
Vendor advisories and official records. Exploit/PoC links are deliberately left out.