CVE-2026-80684: KVM: s390: pci: Fix NULL dereference on AIBV allocation failure
Noroxi assessment
Priority: Monitor (action score 37/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0a95abe964400771ad82b027d7b84a0d183cd0db, 8bf09b9b7d3232806df95f409581f8a9fd99a3fa, 96099486b63985801c9c6ef22505e9aa635b2d20; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0a95abe964400771ad82b027d7b84a0d183cd0db, 8bf09b9b7d3232806df95f409581f8a9fd99a3fa, 96099486b63985801c9c6ef22505e9aa635b2d20; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 28, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
37
Monitor
Low priority for now.
- CVSS
- 37 / 40 · 9.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.0affected
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before 96099486b63985801c9c6ef22505e9aa635b2d20affected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before 0a95abe964400771ad82b027d7b84a0d183cd0dbaffected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before df947d85e164a50a29d43a96e814f69ab1d0f7edaffected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before e137d082325bbcae780087b57501d38585e625d9affected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before d1a103dc9016c25e7423ce5841a5cc2df76d59f3affected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before 8bf09b9b7d3232806df95f409581f8a9fd99a3faaffected · git
- before 6.0not affected · semver
- 6.1.183 and later · up to and including 6.1.*not affected · semver
- 6.6.151 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80681Aug 28, 2026 · vxlan: re-fetch eth header after route_shortcircuit()39Monitor
- ← EarlierCVE-2026-80683Aug 28, 2026 · Bluetooth: SCO: give the socket its own sco_conn reference35Monitor
- Later →CVE-2026-80691Aug 28, 2026 · scsi: target: iblock: Fix wrong PR ops NULL check for PREEMPT/RELEASE30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0a95abe964400771ad82b027d7b84a0d183cd0db | Vendor (CNA) |
| Linux Linux | 8bf09b9b7d3232806df95f409581f8a9fd99a3fa | Vendor (CNA) |
| Linux Linux | 96099486b63985801c9c6ef22505e9aa635b2d20 | Vendor (CNA) |
| Linux Linux | d1a103dc9016c25e7423ce5841a5cc2df76d59f3 | Vendor (CNA) |
| Linux Linux | df947d85e164a50a29d43a96e814f69ab1d0f7ed | Vendor (CNA) |
| Linux Linux | e137d082325bbcae780087b57501d38585e625d9 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0945 · Aug 31, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/8bf09b9b7d3232806df95f409581f8a9fd99a3fa
- git.kernel.org/stable/c/96099486b63985801c9c6ef22505e9aa635b2d20
- git.kernel.org/stable/c/d1a103dc9016c25e7423ce5841a5cc2df76d59f3
- git.kernel.org/stable/c/df947d85e164a50a29d43a96e814f69ab1d0f7ed
- git.kernel.org/stable/c/e137d082325bbcae780087b57501d38585e625d9
Vendor advisories and official records. Exploit/PoC links are deliberately left out.