Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0

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

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% 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
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in a0d87beb2660a5098b2b0ecdc1e96810a9074ea9, 1218c6dcec80f886372635e82f3229d5babc37d3, 426ffae6ecc7ec77d32bf8be065c21a1b881b084
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 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 Linux kernel to a0d87beb2660a5098b2b0ecdc1e96810a9074ea9, 1218c6dcec80f886372635e82f3229d5babc37d3 or 426ffae6ecc7ec77d32bf8be065c21a1b881b084.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 3a9822d7bd623be9000cef8101ecf8479fa53f2c, < a0d87beb2660a5098b2b0ecdc1e96810a9074ea9
Fixed in
  • a0d87beb2660a5098b2b0ecdc1e96810a9074ea9
LinuxLinuxAffected
  • ≥ 3a9822d7bd623be9000cef8101ecf8479fa53f2c, < 1218c6dcec80f886372635e82f3229d5babc37d3
Fixed in
  • 1218c6dcec80f886372635e82f3229d5babc37d3
LinuxLinuxAffected
  • ≥ 3a9822d7bd623be9000cef8101ecf8479fa53f2c, < 426ffae6ecc7ec77d32bf8be065c21a1b881b084
Fixed in
  • 426ffae6ecc7ec77d32bf8be065c21a1b881b084
LinuxLinuxAffected
  • =5.18
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: clamp v9 CRIU control stack checkpoint copy to BO size CRIU checkpoint copies the MQD control stack using cp_hqd_cntl_stack_size from hardware without bounding it to the allocated BO region. If the HW field is larger than the queue's control stack allocation, memcpy reads past the BO into adjacent GTT memory and can leak kernel data to userspace. Store the page-aligned control stack BO size in mqd_manager and clamp checkpoint copies and reported checkpoint sizes to min(cp_hqd_cntl_stack_size, mm->ctl_stack_size). Apply the same bound for multi-XCC v9.4.3 checkpoint layout. (cherry picked from commit 6c2abd0ec09e86c6323010673766f76050e28aa3)

References

Community reviews

Loading reviews…