Linux Kernel up to 7.1.7 KVM PCI kvm_zpci_set_airq aibv/aisb null pointer dereference

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 0.37- |
Summary
A vulnerability classified as very critical has been found in Linux Kernel up to 6.1.182/6.6.150/6.12.102/6.18.43/7.1.7. The affected element is the function kvm_zpci_set_airq of the component KVM PCI. Performing a manipulation of the argument aibv/aisb results in null pointer dereference.
This vulnerability was named CVE-2026-80684. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as very critical, was found in Linux Kernel up to 6.1.182/6.6.150/6.12.102/6.18.43/7.1.7. This affects the function kvm_zpci_set_airq of the component KVM PCI. The manipulation of the argument aibv/aisb with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: KVM: s390: pci: Fix NULL dereference on AIBV allocation failure The airq_iv_create() can return NULL on failure, but the return value was never checked. If it fails, zdev->aibv will be NULL and fail when dereferenced in kvm_zpci_set_airq(). Add a NULL check and free the previously allocated AISB bit and zdev->aisb on failure.
The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-80684 since 08/26/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/28/2026).
Upgrading to version 6.1.183, 6.6.151, 6.12.103, 6.18.44 or 7.1.8 eliminates this vulnerability. Applying the patch 96099486b63985801c9c6ef22505e9aa635b2d20/0a95abe964400771ad82b027d7b84a0d183cd0db/df947d85e164a50a29d43a96e814f69ab1d0f7ed/e137d082325bbcae780087b57501d38585e625d9/d1a103dc9016c25e7423ce5841a5cc2df76d59f3/8bf09b9b7d3232806df95f409581f8a9fd99a3fa is able to eliminate this problem.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 6.1.182
- 6.6.150
- 6.12.102
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 7.1.0
- 7.1.1
- 7.1.2
- 7.1.3
- 7.1.4
- 7.1.5
- 7.1.6
- 7.1.7
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.9VulDB Meta Temp Score: 9.5
VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.1.183/6.6.151/6.12.103/6.18.44/7.1.8
Patch: 96099486b63985801c9c6ef22505e9aa635b2d20/0a95abe964400771ad82b027d7b84a0d183cd0db/df947d85e164a50a29d43a96e814f69ab1d0f7ed/e137d082325bbcae780087b57501d38585e625d9/d1a103dc9016c25e7423ce5841a5cc2df76d59f3/8bf09b9b7d3232806df95f409581f8a9fd99a3fa
Timeline
08/26/2026 CVE reserved08/28/2026 Advisory disclosed
08/28/2026 VulDB entry created
08/28/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-80684 (🔒)
GCVE (CVE): GCVE-0-2026-80684
GCVE (VulDB): GCVE-100-396633
Entry
Created: 08/28/2026 10:57Changes: 08/28/2026 10:57 (60)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.