Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98282

powerpc/iommu: Fix the overflow validation in iommu_tce_check_ioba

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

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-98282, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Received3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected b1af23d836f811137d504d14d4cbdd01929dec34 – < 98d8dcc4ebd10523507d4478e148809a7771a213
    • affected b1af23d836f811137d504d14d4cbdd01929dec34 – < 9fd9c9bbb05417f468a11fb6d145d7ff61f4a868
    • affected b1af23d836f811137d504d14d4cbdd01929dec34 – < 3776bf56e06980e8a12c8c0565d9e6ac44965f03
    • affected b1af23d836f811137d504d14d4cbdd01929dec34 – < d6a1779129d936bc1fbab80181165da544eab736
    • affected b1af23d836f811137d504d14d4cbdd01929dec34 – < d48ceb6e1a6915c7bac4f902554a1047365cdff2
    • affected b1af23d836f811137d504d14d4cbdd01929dec34 – < 0543813753ef5cfbd6fa96694f7acf783fa01af7
    • affected b1af23d836f811137d504d14d4cbdd01929dec34 – < 314091243159f8e3749bc719bb129f423f72fd86
    • affected b1af23d836f811137d504d14d4cbdd01929dec34 – < 0b271f7d7f5ed45bc498a03ce0aa9cfd8402fc71
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98282 badge
[![CVE-2026-98282](https://cveledger.app/badge/CVE-2026-98282.svg)](https://cveledger.app/cve/CVE-2026-98282)

Record last updated .