powerpc/iommu: Fix the overflow validation in iommu_tce_check_ioba
Noroxi assessment
Priority: Monitor (action score 35/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.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0543813753ef5cfbd6fa96694f7acf783fa01af7, 0b271f7d7f5ed45bc498a03ce0aa9cfd8402fc71, 314091243159f8e3749bc719bb129f423f72fd86; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 0543813753ef5cfbd6fa96694f7acf783fa01af7, 0b271f7d7f5ed45bc498a03ce0aa9cfd8402fc71, 314091243159f8e3749bc719bb129f423f72fd86; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.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: powerpc/iommu: Fix the overflow validation in iommu_tce_check_ioba The commit b1af23d836f8 ("KVM: PPC: iommu: Unify TCE checking") unified IOBA parameter checking across KVM and VFIO into iommu_tce_check_ioba(). While doing so, the passed in argument npages is ignored and constant value '1' is used leaving out a possible overflow as the callers can legitimately be using npages > 1 for H_STUFF_TCE or H_PUT_TCE_INDIRECT cases. Fix this by accounting for 'npages', checking for arithmetic overflow, and verifying that the entire requested range (ioba - offset + npages) does not exceed the table capacity 'size'.
- Published
- Oct 6, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- 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.12affected
- b1af23d836f811137d504d14d4cbdd01929dec34 and later · before 98d8dcc4ebd10523507d4478e148809a7771a213affected · git
- b1af23d836f811137d504d14d4cbdd01929dec34 and later · before 9fd9c9bbb05417f468a11fb6d145d7ff61f4a868affected · git
- b1af23d836f811137d504d14d4cbdd01929dec34 and later · before 3776bf56e06980e8a12c8c0565d9e6ac44965f03affected · git
- b1af23d836f811137d504d14d4cbdd01929dec34 and later · before d6a1779129d936bc1fbab80181165da544eab736affected · git
- b1af23d836f811137d504d14d4cbdd01929dec34 and later · before d48ceb6e1a6915c7bac4f902554a1047365cdff2affected · git
- b1af23d836f811137d504d14d4cbdd01929dec34 and later · before 0543813753ef5cfbd6fa96694f7acf783fa01af7affected · git
- b1af23d836f811137d504d14d4cbdd01929dec34 and later · before 314091243159f8e3749bc719bb129f423f72fd86affected · git
- b1af23d836f811137d504d14d4cbdd01929dec34 and later · before 0b271f7d7f5ed45bc498a03ce0aa9cfd8402fc71affected · git
- before 4.12not 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 | before 6.1.190-1 | 6.1.190-1 |
| 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.8-1 | 7.2.8-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-98280Oct 6, 2026 · drm/xe/i2c: Disable IRQ on unbind0Monitor
- ← EarlierCVE-2026-98281Oct 6, 2026 · futex: Also allocate private hash on vfork()31Monitor
- Later →CVE-2026-98283Oct 6, 2026 · KVM: PPC: Book3S HV: fix use-after-free in kvmhv_emulate_tlbie_all_lpid()35Monitor
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 | 0543813753ef5cfbd6fa96694f7acf783fa01af7 | Vendor (CNA) |
| Linux Linux | 0b271f7d7f5ed45bc498a03ce0aa9cfd8402fc71 | Vendor (CNA) |
| Linux Linux | 314091243159f8e3749bc719bb129f423f72fd86 | Vendor (CNA) |
| Linux Linux | 3776bf56e06980e8a12c8c0565d9e6ac44965f03 | Vendor (CNA) |
| Linux Linux | 98d8dcc4ebd10523507d4478e148809a7771a213 | Vendor (CNA) |
| Linux Linux | 9fd9c9bbb05417f468a11fb6d145d7ff61f4a868 | Vendor (CNA) |
| Linux Linux | d48ceb6e1a6915c7bac4f902554a1047365cdff2 | Vendor (CNA) |
| Linux Linux | d6a1779129d936bc1fbab80181165da544eab736 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.8-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-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.
- Published
- Fix recordedsame day
- TodayOct 25, 2026+19 d
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
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- 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
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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
- CVSS— → 8.8
- Severity— → high
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/0b271f7d7f5ed45bc498a03ce0aa9cfd8402fc71
- git.kernel.org/stable/c/314091243159f8e3749bc719bb129f423f72fd86
- git.kernel.org/stable/c/3776bf56e06980e8a12c8c0565d9e6ac44965f03
- git.kernel.org/stable/c/98d8dcc4ebd10523507d4478e148809a7771a213
- git.kernel.org/stable/c/9fd9c9bbb05417f468a11fb6d145d7ff61f4a868
- git.kernel.org/stable/c/d48ceb6e1a6915c7bac4f902554a1047365cdff2
- git.kernel.org/stable/c/d6a1779129d936bc1fbab80181165da544eab736
Vendor advisories and official records. Exploit/PoC links are deliberately left out.