Skip to main content
VulnerabilityPublished Updated

CVE-2026-52968: Linux kernel · Out-of-bounds Read

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High · fixed in e7216651b94e92e5433fb2f54b77864642b4ea48 : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in e7216651b94e92e5433fb2f54b77864642b4ea48, b22a2da8792a7bfe743c1a922e77fa499ddedbe8, a99a25db131ece5e6c0f7632da606de631efe4f2 +3
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 73f91b004321f2510fa79e66035dbbf1870fcf56, < e7216651b94e92e5433fb2f54b77864642b4ea48
Fixed in
  • e7216651b94e92e5433fb2f54b77864642b4ea48
LinuxLinuxAffected
  • ≥ 73f91b004321f2510fa79e66035dbbf1870fcf56, < b22a2da8792a7bfe743c1a922e77fa499ddedbe8
Fixed in
  • b22a2da8792a7bfe743c1a922e77fa499ddedbe8
LinuxLinuxAffected
  • ≥ 73f91b004321f2510fa79e66035dbbf1870fcf56, < a99a25db131ece5e6c0f7632da606de631efe4f2
Fixed in
  • a99a25db131ece5e6c0f7632da606de631efe4f2
LinuxLinuxAffected
  • ≥ 73f91b004321f2510fa79e66035dbbf1870fcf56, < 31a9d9f9942885aae356a1a57c79e82c5b5b0828
Fixed in
  • 31a9d9f9942885aae356a1a57c79e82c5b5b0828
LinuxLinuxAffected
  • ≥ 73f91b004321f2510fa79e66035dbbf1870fcf56, < 16d990a15491cf76cd6eef0846e1b4100e63261a
Fixed in
  • 16d990a15491cf76cd6eef0846e1b4100e63261a
LinuxLinuxAffected
  • ≥ 73f91b004321f2510fa79e66035dbbf1870fcf56, < 11b8ff5b930b351dd1f6f088dce0beb027ac92d0
Fixed in
  • 11b8ff5b930b351dd1f6f088dce0beb027ac92d0

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: s390: pci: fix GAIT table indexing due to double-scaling pointer arithmetic kvm_s390_pci_aif_enable(), kvm_s390_pci_aif_disable(), and aen_host_forward() index the GAIT by manually multiplying the index with sizeof(struct zpci_gaite). Since aift->gait is already a struct zpci_gaite pointer, this double-scales the offset, accessing element aisb*16 instead of aisb. This causes out-of-bounds accesses when aisb >= 32 (with ZPCI_NR_DEVICES=512) Fix by removing the erroneous sizeof multiplication.

References

Community reviews

Loading reviews…