Menu

Star on GitHub · 3.2k

CVE-2026-80687

In the Linux kernel, the following vulnerability has been resolved: iommufd/viommu: Release the igroup lock on the vdevice_size error path iommufd_vdevice_alloc_ioctl() takes idev->igroup->lock,…

Published Aug 28, 2026EPSS 0.21%

Overview

CVE-2026-80687 is a known-severity vulnerability. It was published on August 28, 2026.

Technical description

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

iommufd/viommu: Release the igroup lock on the vdevice_size error path

iommufd_vdevice_alloc_ioctl() takes idev->igroup->lock, then validates the

driver's vdevice_size against the core structure size with a WARN_ON_ONCE.

On failure that guard jumps to out_put_idev, below out_unlock_igroup, so it

skips the mutex_unlock(), leaving the igroup lock held and deadlocking the

next vDEVICE operation on that group.

Jump to out_unlock_igroup instead.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-80687?

CVE-2026-80687 is a known-severity vulnerability. It was published on August 28, 2026.

How severe is CVE-2026-80687?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-80687?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-80687?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-80687 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.