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-89926KVM: s390: Fix length check __import_wp_info()

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Fix length check __import_wp_info() struct kvm_hw_breakpoint::len is a __u64 that is fully controlled by user space. This is then assigned to wp_info->len, which is an int. The bounds check is done on the truncated value while the allocation uses the untruncated one: wp_info->len = bp_data->len; [...] if (wp_info->len < 0 || wp_info->len > MAX_WP_SIZE) return -EINVAL; wp_info->old_data = kmalloc(bp_data->len, GFP_KERNEL_ACCOUNT); Use the validated value for the allocation as intended. Without this fix userspace can trigger >4GB allocations which will fail and result in a WARN due to MAX_PAGE_ORDER.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 44 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (14 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 27291e2165b6de70c476b7b675308113edd69a60 – < 36d62dfb3cac66e6a97fd850a592c2ed56e35ba5
    • affected 27291e2165b6de70c476b7b675308113edd69a60 – < aef540194effd768bed0bd2e6a74fe135a3d7c3a
    • affected 27291e2165b6de70c476b7b675308113edd69a60 – < 71153d3262517e1c02c3a66aa5094f279b2d1454
    • affected 27291e2165b6de70c476b7b675308113edd69a60 – < fec89d327d9b2b669b5bbdac209386c6317c3722
    • affected 27291e2165b6de70c476b7b675308113edd69a60 – < b94ab9caa5d72c78226121cccff5e33f946da900
    • affected 27291e2165b6de70c476b7b675308113edd69a60 – < beb9c55af609c4c7308259d7191688c75a4e3d4a
    • affected 27291e2165b6de70c476b7b675308113edd69a60 – < 3fe801db90bdeefb0bbdda42d832846b53f64f8a
    • affected 27291e2165b6de70c476b7b675308113edd69a60 – < 4c07680a467e2f7697245bcd11691bffb2a6f0ed
  • Linux · Linux

    • affected 3.16
    • unaffected < 3.16
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 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-89926 badge
[![CVE-2026-89926](https://cveledger.app/badge/CVE-2026-89926.svg)](https://cveledger.app/cve/CVE-2026-89926)

Record last updated .