Not ratedCVE-2026-80870

    Linux Kernel: security vulnerability (CVE-2026-80870)

    Published Last modified Sources: HKCERT, Ubuntu, SUSE, BSI, EUVD, CVE.org

    Share

    What is affected, what to do

    Update Linux Kernel to version 6.1.178, Linux Kernel to version 6.6.145, Linux Kernel to version 6.12.97.

    Affected
    • Linux Kernel lt 5.18..6.1.178
    • Linux Kernel lt 6.2..6.6.145
    • Linux Kernel lt 6.7..6.12.97
    • Linux Kernel lt 6.13..6.18.40
    • Linux Kernel lt 6.19..7.1.5
    Fixed in
    • Linux Kernel 6.1.178
    • Linux Kernel 6.6.145
    • Linux Kernel 6.12.97
    • Linux Kernel 6.18.40
    • Linux Kernel 7.1.5
    • Linux Kernel 7.2

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    —

    XIEM Effective CVSS

    No value is available for this vulnerability.

    0.0

    CVSS v3

    Severity Not rated on the scale from 0 to 10.

    Source: HKCERT, Ubuntu, SUSE, BSI, EUVD, CVE.org

    0.2 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 12.0

    Show all metrics
    Severity
    Not rated
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    25.00 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    0.0
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.2 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    12.0
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    In the Linux kernel, the following vulnerability has been resolved:

    drm/amdkfd: Validate CRIU-restored IDs before idr_alloc

    The KFD CRIU restore flow restores previously saved object IDs from userspace.

    For event restore:

    kfd_criu_restore_event() -> create_signal_event() / create_other_event() -> allocate_event_notification_slot() -> idr_alloc(..., *restore_id, *restore_id + 1, ...)

    For BO restore:

    criu_restore_memory_of_gpu() -> idr_alloc(..., bo_priv->idr_handle, ...)

    In both cases, the restored ID comes from userspace-provided CRIU data.

    idr_alloc() expects the ID range values to fit within signed int limits. If a restored ID is larger than INT_MAX, it can trigger a WARN in the IDR layer.

    A kernel WARN is undesirable because it prints a warning trace and may cause a panic or reboot on systems with panic_on_warn enabled.

    Smatch reported these paths as allowing unchecked userspace values to reach idr_alloc().

    Add INT_MAX validation before using restored IDs in:

    • kfd_criu_restore_event()
    • criu_restore_memory_of_gpu()

    If the restored ID is invalid, return -EINVAL.

    This prevents invalid restore data from reaching the IDR layer and avoids WARN-triggering paths, while keeping valid restore behavior unchanged.

    Source: HKCERT (CC BY 3.0 HK) · HKCERT rating: medium, Ubuntu Security Notices, suse_csaf, BSI WID Portal, BSI CSAF, ENISA EUVD, cvelistv5, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    LinuxLinux
    • 6.7 – < 6.12.97
    • 6.19 – < 7.1.5
    • 5.18 – < 6.1.178
    • 6.2 – < 6.6.145
    • —
    • 6.13 – < 6.18.40
    • 6.12.97
    • 7.1.5
    • 6.1.178
    • 6.6.145
    • 7.2
    • 6.18.40
    Red HatOpenShift
    • Container Platform
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxubuntulinuxnoble
    Linuxubuntulinuxresolute
    Linuxubuntulinux-awsnoble
    Linuxubuntulinux-awsresolute
    Linuxubuntulinux-aws-6.8jammy
    Linuxubuntulinux-aws-7.0noble
    Linuxubuntulinux-aws-fipsnoble
    Linuxubuntulinux-azurenoble
    Linuxubuntulinux-azureresolute
    Linuxubuntulinux-azure-6.8jammy
    Linuxubuntulinux-azure-7.0noble
    Linuxubuntulinux-azure-fdenoble
    Linuxubuntulinux-azure-fderesolute
    Linuxubuntulinux-azure-fde-6.8jammy
    Linuxubuntulinux-azure-fde-7.0noble
    Linuxubuntulinux-azure-fipsnoble
    Linuxubuntulinux-fipsnoble
    Linuxubuntulinux-gcpnoble
    Linuxubuntulinux-gcpresolute
    Linuxubuntulinux-gcp-6.8jammy
    Linuxubuntulinux-gcp-7.0noble
    Linuxubuntulinux-gcp-fipsnoble
    Linuxubuntulinux-gkenoble
    Linuxubuntulinux-gkeresolute

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. ReceivedLinux

      Description added or changed

      Show 8 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Validate CRIU-restored IDs before idr_alloc The KFD CRIU restore flow restores previously saved object IDs from userspace. For event restore: kfd_criu_restore_event() -> create_signal_event() / create_other_event() -> allocate_event_notification_slot() -> idr_alloc(..., *restore_id, *restore_id + 1, ...) For BO restore: criu_restore_memory_of_gpu() -> idr_alloc(..., bo_priv->idr_handle, ...) In both cases, the restored ID comes from userspace-provided CRIU data. idr_alloc() expects the ID range values to fit within signed int limits. If a restored ID is larger than INT_MAX, it can trigger a WARN in the IDR layer. A kernel WARN is undesirable because it prints a warning trace and may cause a panic or reboot on systems with panic_on_warn enabled. Smatch reported these paths as allowing unchecked userspace values to reach idr_alloc(). Add INT_MAX validation before using restored IDs in: - kfd_criu_restore_event() - criu_restore_memory_of_gpu() If the restored ID is invalid, return -EINVAL. This prevents invalid restore data from reaching the IDR layer and avoids WARN-triggering paths, while keeping valid restore behavior unchanged.
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80870.json">CVE-2026-80870</a>
      Referenceadded
      —
      https://git.kernel.org/stable/c/085ea93bda71fee600cc12a17026598eb10dd1f9
      Referenceadded
      —
      https://git.kernel.org/stable/c/543ed0f61d56501cc585162da600bbedd7c08c0f
      Referenceadded
      —
      https://git.kernel.org/stable/c/85043dd49c2f51a37b22618168e3ae59ab92f0d6
      Referenceadded
      —
      https://git.kernel.org/stable/c/89a75e3349c4fae28cbedc711bc924cbc6293da2
      Referenceadded
      —
      https://git.kernel.org/stable/c/cb6311f25a096621ac7ffd91b50d1bb1cfb63a96
      Referenceadded
      —
      https://git.kernel.org/stable/c/f8687018f24037056692c1e93c7d96cc72889d5b

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-80870
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-80870"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-80870.svg?lang=en" alt="CVE-2026-80870 – NEOSEC Intel" height="20"></a>