CVE-2026-52968: KVM: s390: pci: fix GAIT table indexing due to double-scaling pointer arithmetic

Published Jun 24, 2026
·
Updated

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

KVM: s390: pci: fix GAIT table indexing due to double-scaling pointer arithmetic

kvms390pciaifenable(), kvms390pciaifdisable(), and aenhostforward() index the GAIT by manually multiplying the index with sizeof(struct zpcigaite).

Since aift->gait is already a struct zpcigaite pointer, this double-scales the offset, accessing element aisb16 instead of aisb.

This causes out-of-bounds accesses when aisb >= 32 (with ZPCINRDEVICES=512)

Fix by removing the erroneous sizeof multiplication.

Affected Software

10 affected componentsFixes available
Linux Linux kernel (KVM s390)
Microsoft azl3 kernel 6.6.139.1-1<6.6.143.1-1
6.6.143.1-1
Linux Linux kernel>=6.0<6.1.175
Linux Linux kernel>=6.2<6.6.141
Linux Linux kernel>=6.7<6.12.91
Linux Linux kernel>=6.13<6.18.33
Linux Linux kernel>=6.19<7.0.10
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.143.1-1
  2. Compensating control

    Apply the Linux kernel fix for “KVM: s390: pci: fix GAIT table indexing due to double-scaling pointer arithmetic” by removing the erroneous sizeof multiplication that double-scales the GAIT table offset (so the GAIT element index is not accessed as aisb*16 instead of aisb), which prevents out-of-bounds accesses when aisb >= 32 (e.g., with ZPCI_NR_DEVICES=512).

Event History

Jun 24, 2026
CVE Published
via MITRE·04:28 PM
Data Sourced
via MITRE·04:28 PM
DescriptionSeverity
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 27, 2026
Data Sourced
via Microsoft·08:11 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:11 AM
Affected Software
Updated
via Microsoft·08:11 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2026-52968?

CVE-2026-52968 has a risk score of 40, indicating a significant vulnerability.

2

How do I fix CVE-2026-52968?

To fix CVE-2026-52968, ensure that you update your Linux kernel to a version where the vulnerability has been patched.

3

What components are affected by CVE-2026-52968?

CVE-2026-52968 affects the KVM (Kernel-based Virtual Machine) component within the Linux kernel on s390 architecture.

4

What are the potential consequences of exploiting CVE-2026-52968?

Exploitation of CVE-2026-52968 could lead to improper indexing in the GAIT table, potentially leading to unexpected behavior in KVM operations.

5

When was CVE-2026-52968 published?

CVE-2026-52968 was published on June 24, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203