---
title: "CVE-2026-98282: Linux Kernel - Integer Overflow"
description: "Linux kernel contains an integer overflow vulnerability in powerpc/iommu due to improper validation of npages in iommu_tce_check_ioba, letting attackers cause potential memory corruption, exploit requires crafted input with npages > 1."
url: https://panop.io/threat-heartbeat/CVE-2026-98282/
---

# CVE-2026-98282 Linux Kernel - Integer Overflow

Linux kernel contains an integer overflow vulnerability in powerpc/iommu due to improper validation of npages in iommu\_tce\_check\_ioba, letting attackers cause potential memory corruption, exploit requires crafted input with npages > 1.

CVSS base score 8.8 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.14% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-98282)

## Details

Type

Integer Overflow

Impact

Denial Of Service

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Published

6 October 2026

Updated

15 October 2026

## Vendor fix

Update to the latest Linux kernel version containing the fix for iommu\_tce\_check\_ioba.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-98282](https://nvd.nist.gov/vuln/detail/CVE-2026-98282)
- [https://git.kernel.org/stable/c/0b271f7d7f5ed45bc498a03ce0aa9cfd8402fc71](https://git.kernel.org/stable/c/0b271f7d7f5ed45bc498a03ce0aa9cfd8402fc71)
- [https://git.kernel.org/stable/c/314091243159f8e3749bc719bb129f423f72fd86](https://git.kernel.org/stable/c/314091243159f8e3749bc719bb129f423f72fd86)
- [https://git.kernel.org/stable/c/3776bf56e06980e8a12c8c0565d9e6ac44965f03](https://git.kernel.org/stable/c/3776bf56e06980e8a12c8c0565d9e6ac44965f03)
- [https://git.kernel.org/stable/c/98d8dcc4ebd10523507d4478e148809a7771a213](https://git.kernel.org/stable/c/98d8dcc4ebd10523507d4478e148809a7771a213)
- [https://git.kernel.org/stable/c/9fd9c9bbb05417f468a11fb6d145d7ff61f4a868](https://git.kernel.org/stable/c/9fd9c9bbb05417f468a11fb6d145d7ff61f4a868)
- [https://git.kernel.org/stable/c/d48ceb6e1a6915c7bac4f902554a1047365cdff2](https://git.kernel.org/stable/c/d48ceb6e1a6915c7bac4f902554a1047365cdff2)
- [https://git.kernel.org/stable/c/d6a1779129d936bc1fbab80181165da544eab736](https://git.kernel.org/stable/c/d6a1779129d936bc1fbab80181165da544eab736)
- [https://git.kernel.org/stable/c/0543813753ef5cfbd6fa96694f7acf783fa01af7](https://git.kernel.org/stable/c/0543813753ef5cfbd6fa96694f7acf783fa01af7)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
