Answer in brief
CVE-2026-80687 records a Unknown severity vulnerability in iommufd/viommu: Release the igroup lock on the vdevice_size error path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ed42eee797ff3dc889ade63c1dd7c4f430699e23 <294b464b2be7e57872864cb6936e1d9c7294f89d || >=ed42eee797ff3dc889ade63c1dd7c4f430699e23 <ca9e49e1c8931a4e6e743a1f1d2e7f977f774b86 || >=ed42eee797ff3dc889ade63c1dd7c4f430699e23 <339bd11591593ab7ce88136ab7fd01ef3813b724 | 294b464b2be7e57872864cb6936e1d9c7294f89d, ca9e49e1c8931a4e6e743a1f1d2e7f977f774b86, 339bd11591593ab7ce88136ab7fd01ef3813b724 |
| Linux/Linuxgeneric | 6.17 | Not reported |
Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 28, 2026
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.
Quoted source text, attributed separately from HOL analysis.