CVE-2026-80891: KVM: s390: pci: Validate AIBV and AISB before pinning guest pages
Noroxi assessment
Priority: Monitor (action score 0/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.21% (FIRST EPSS).
- Fixed version: Linux Linux 15df7700dd99f8a37f5c6ed2dcf1e33009cdba47, 3a1c64220ede4ac9ef9a3e76f008ff60a34f4c48, 868d32ac72cba21c5c6d8a66a814b7c25a3a5c01.
Low priority for now. Upgrade to Linux Linux 15df7700dd99f8a37f5c6ed2dcf1e33009cdba47, 3a1c64220ede4ac9ef9a3e76f008ff60a34f4c48, 868d32ac72cba21c5c6d8a66a814b7c25a3a5c01 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: Validate AIBV and AISB before pinning guest pages The AIBV holds one bit per MSI-X vector for a given function. The size of the bit vector is derived from the NOI and the AIBVO. If the size of the AIBV exceeds a single page boundary, then reject the request as we cannot safely pin the guest AIBV. Similarly reject the request if the AISB address is not 8-byte aligned as the architecture requires doubleword alignment for the summary bit address. Since the AISBO can address up to 64 bits, the size of the AISB can only be 8 bytes for the function. This also ensures the AISB doesn't exceed a single page boundary.
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Is your version affected? Check itNoroxi 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 3a1c64220ede4ac9ef9a3e76f008ff60a34f4c48affected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before f00ef8efd41440129ccd88f4a1ebebf8d61d297faffected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before 15df7700dd99f8a37f5c6ed2dcf1e33009cdba47affected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before b878ba7e28144c9a857bc847d31f3c45413450acaffected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before fbfe683f8b1ae7e40b56bdd6daf5bd671bc3a528affected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before 868d32ac72cba21c5c6d8a66a814b7c25a3a5c01affected · 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-80886Sep 4, 2026 · serial: msm: Disable DMA for kernel console UART0Monitor
- ← EarlierCVE-2026-80889Sep 4, 2026 · can: isotp: fix timer drain order, wakeup handling and tx_gen ordering0Monitor
- Later →CVE-2026-80894Sep 4, 2026 · iommufd: Fix wrong hwpt passed to iommufd_auto_response_faults on replace0Monitor
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 | 15df7700dd99f8a37f5c6ed2dcf1e33009cdba47 | Vendor (CNA) |
| Linux Linux | 3a1c64220ede4ac9ef9a3e76f008ff60a34f4c48 | Vendor (CNA) |
| Linux Linux | 868d32ac72cba21c5c6d8a66a814b7c25a3a5c01 | Vendor (CNA) |
| Linux Linux | b878ba7e28144c9a857bc847d31f3c45413450ac | Vendor (CNA) |
| Linux Linux | f00ef8efd41440129ccd88f4a1ebebf8d61d297f | Vendor (CNA) |
| Linux Linux | fbfe683f8b1ae7e40b56bdd6daf5bd671bc3a528 | Vendor (CNA) |
| 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).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3a1c64220ede4ac9ef9a3e76f008ff60a34f4c48
- git.kernel.org/stable/c/868d32ac72cba21c5c6d8a66a814b7c25a3a5c01
- git.kernel.org/stable/c/b878ba7e28144c9a857bc847d31f3c45413450ac
- git.kernel.org/stable/c/f00ef8efd41440129ccd88f4a1ebebf8d61d297f
- git.kernel.org/stable/c/fbfe683f8b1ae7e40b56bdd6daf5bd671bc3a528
Vendor advisories and official records. Exploit/PoC links are deliberately left out.