# CVE-2026-98282: powerpc/iommu: Fix the overflow validation in iommu_tce_check_ioba

> An integer overflow in the Linux kernel's PowerPC IOMMU code allows attackers to bypass bounds checks, potentially leading to privilege escalation or code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106383, BELL-CVE-2026-98282, DEBIAN-CVE-2026-98282, GHSA-8m3g-gm8v-p3m6, UBUNTU-CVE-2026-98282

## What is CVE-2026-98282?

CVE-2026-98282 is a high-severity vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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'.

## Which versions are affected by CVE-2026-98282?


## How do I fix CVE-2026-98282?

Apply the vendor's patch.

## Is CVE-2026-98282 being exploited?

There is no known exploitation of CVE-2026-98282 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98282 and fix it if it is affected.

What it is: CVE-2026-98282 is a high-severity vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98282 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98282/ (Markdown: https://insights.sbomify.com/CVE-2026-98282/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98282
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98282
- OSV: https://osv.dev/vulnerability/CVE-2026-98282

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98282/
Summaries are generated and may contain mistakes; the official description above is the record.