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-97421RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz()

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz() Several corner cases, especially important on 32 bits: - umem->iova is u64, the function argument should pass in u64 or iova will be truncated - Check that the length is not too large for the iova - Check that lengths > 4G don't overflow the GENMASK

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 9 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-97421, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (19 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected a40c20dabdf9045270767c75918feb67f0727c89 – < 3014da7587ce006cd08004fd6b257626b314e0a3
    • affected a40c20dabdf9045270767c75918feb67f0727c89 – < ddccf6cc3861de2fe60986933bead79220e0d797
    • affected a40c20dabdf9045270767c75918feb67f0727c89 – < e9bbb5f5349ef560ff6f0395564f04c3aa664559
    • affected a40c20dabdf9045270767c75918feb67f0727c89 – < ae3cf7d2c4d506c5c91746321644e1a08d989e2a
    • affected a40c20dabdf9045270767c75918feb67f0727c89 – < 5fc5b73109540809b094710fac44da81dd8a3ff8
    • affected a40c20dabdf9045270767c75918feb67f0727c89 – < 09ea6837a0434fb4db99528a5055b6d822135dcf
    • affected 85e40ba1c4a5246b35e91c2ed69d4680426904d7
    • affected 59f07434b297e2268f5d5c567db5b09145245cf1
    • affected 488229b7729d7becf4c39c5e74fb709fb35115c2
    • affected 5.4.73 – < 5.5
    • affected 5.8.17 – < 5.9
    • affected 5.9.2 – < 5.10
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .