PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-80684 Linux CVE debrief

A critical vulnerability was found in the Linux kernel, specifically in the KVM s390 pci component. The vulnerability arises from a NULL pointer dereference that occurs when the airq_iv_create() function returns NULL, indicating an allocation failure. This NULL value is not checked and leads to a failure when dereferenced in the kvm_zpci_set_airq() function. The vulnerability has a CVSS score of 9.3 and is considered CRITICAL.

Vendor
Linux
Product
Unknown
CVSS
CRITICAL 9.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-28
Original CVE updated
2026-08-29
Advisory published
2026-08-28
Advisory updated
2026-08-29

Who should care

System administrators and security teams responsible for Linux kernel-based systems, especially those using KVM s390 pci components, should be aware of this vulnerability and take immediate action to patch their systems. They should review system configurations and ensure that the KVM s390 pci component is properly secured. Additionally, they should monitor system logs for potential exploitation attempts and prioritize patching this vulnerability due to its critical severity and potential for exploitation.

Technical summary

The vulnerability is caused by a NULL pointer dereference in the kvm_zpci_set_airq() function due to an allocation failure in the airq_iv_create() function. This can lead to a system crash or potential code execution. The vulnerability has a CVSS score of 9.3 and is considered CRITICAL. The affected product is the Linux kernel, specifically the KVM s390 pci component. Defensive impact includes potential system crashes or code execution if the vulnerability is exploited.

Defensive priority

High priority should be given to patching this vulnerability due to its critical severity and potential for exploitation.

Recommended defensive actions

  • Apply the patch provided by the Linux kernel maintainers to fix the NULL dereference vulnerability.
  • Review system configurations and ensure that the KVM s390 pci component is properly secured.
  • Monitor system logs for potential exploitation attempts.
  • Perform a thorough review of system configurations to ensure that the KVM s390 pci component is properly secured.
  • Verify that all necessary patches have been applied to the Linux kernel-based systems.
  • Check for any potential exploitation attempts by reviewing system logs.
  • Track the patch status of Linux kernel-based systems, especially those using KVM s390 pci components.

Evidence notes

Evidence is based on limited details from the CVE and NVD records. Further investigation is required to fully understand the vulnerability's impact and affected systems. The vulnerability arises from a NULL pointer dereference that occurs when the airq_iv_create() function returns NULL, indicating an allocation failure. This NULL value is not checked and leads to a failure when dereferenced in the kvm_zpci_set_airq() function. System administrators and security teams should verify the patch status of Linux kernel-based systems, especially those using KVM s390 pci components. They should also review system configurations and ensure that the KVM s390 pci component is properly secured.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-80684 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-80684

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-80684 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-80684

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/0a95abe964400771ad82b027d7b84a0d183cd0db

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/8bf09b9b7d3232806df95f409581f8a9fd99a3fa

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/96099486b63985801c9c6ef22505e9aa635b2d20

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/d1a103dc9016c25e7423ce5841a5cc2df76d59f3

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/df947d85e164a50a29d43a96e814f69ab1d0f7ed

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/e137d082325bbcae780087b57501d38585e625d9

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.