Skip to main content
VulnerabilityPublished Updated

CVE-2026-68258: Linux kernel · Improper Input Validation

Affects Linux kernelSource CVE Database V5

0

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

Data as of 26 Oct 2026, 14:05 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 2% 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 fd1691ec62701c982ea32e749678988c67fd4c21, cc10a5839756982504ee8568fc1e1625962ab7f8, 1956aa246c65c5895589664ccb37d0710aa8d304 +2
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 10 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 to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 42c6c48214b726c30918e8dc80e2168607d13ae4, < fd1691ec62701c982ea32e749678988c67fd4c21
Fixed in
  • fd1691ec62701c982ea32e749678988c67fd4c21
LinuxLinuxAffected
  • ≥ 42c6c48214b726c30918e8dc80e2168607d13ae4, < cc10a5839756982504ee8568fc1e1625962ab7f8
Fixed in
  • cc10a5839756982504ee8568fc1e1625962ab7f8
LinuxLinuxAffected
  • ≥ 42c6c48214b726c30918e8dc80e2168607d13ae4, < 1956aa246c65c5895589664ccb37d0710aa8d304
Fixed in
  • 1956aa246c65c5895589664ccb37d0710aa8d304
LinuxLinuxAffected
  • ≥ 42c6c48214b726c30918e8dc80e2168607d13ae4, < 47ea05f246bebc81c7796f56265cffd812cf0601
Fixed in
  • 47ea05f246bebc81c7796f56265cffd812cf0601
LinuxLinuxAffected
  • ≥ 42c6c48214b726c30918e8dc80e2168607d13ae4, < 2b817c0dfc653bf33d0e0ab8155ff7807a617487
Fixed in
  • 2b817c0dfc653bf33d0e0ab8155ff7807a617487
LinuxLinuxAffected
  • =5.18
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size We weren't checking whether the values provided in the private data in kfd CRIU restore were within bounds. For queue type, add a KFD_QUEUE_TYPE_MAX and ensure the provided type is less than it. For mqd_size, add new function mqd_size_from_queue_type and confirm that the provided mqd_size matches expectations. (cherry picked from commit f19d8086f6644083c913d70bfdeee20e1b6f46a5)

References

Community reviews

Loading reviews…