Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0

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

Data as of 26 Oct 2026, 14:18 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% 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 eb636fbc443149b3501c3f97e26225ddcb314a0f, c38b0d5c661951b5dd082bdf31f8a57a0ce6e540, 5297299c3fa6133275db0be99d69cd759b6cbfe9 +5
CVSS:3.1/AV:A/AC:L/PR:N/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
  • ≥ bdcd81707973cf8aa9305337166f8ee842a050d4, < eb636fbc443149b3501c3f97e26225ddcb314a0f
Fixed in
  • eb636fbc443149b3501c3f97e26225ddcb314a0f
LinuxLinuxAffected
  • ≥ bdcd81707973cf8aa9305337166f8ee842a050d4, < c38b0d5c661951b5dd082bdf31f8a57a0ce6e540
Fixed in
  • c38b0d5c661951b5dd082bdf31f8a57a0ce6e540
LinuxLinuxAffected
  • ≥ bdcd81707973cf8aa9305337166f8ee842a050d4, < 5297299c3fa6133275db0be99d69cd759b6cbfe9
Fixed in
  • 5297299c3fa6133275db0be99d69cd759b6cbfe9
LinuxLinuxAffected
  • ≥ bdcd81707973cf8aa9305337166f8ee842a050d4, < 35196a07603f8c94a4943093bc26d5b5826285f8
Fixed in
  • 35196a07603f8c94a4943093bc26d5b5826285f8
LinuxLinuxAffected
  • ≥ bdcd81707973cf8aa9305337166f8ee842a050d4, < 289edc3c71344b89e6522891147cfb8f61b088bb
Fixed in
  • 289edc3c71344b89e6522891147cfb8f61b088bb
LinuxLinuxAffected
  • ≥ bdcd81707973cf8aa9305337166f8ee842a050d4, < 69ac7ba3a3df6654e7daa82674575a8c4a1a63ea
Fixed in
  • 69ac7ba3a3df6654e7daa82674575a8c4a1a63ea

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: ath6kl: fix OOB read from firmware num_msg in TX complete handler The firmware-controlled num_msg field (u8, 0-255) drives the loop in ath6kl_wmi_tx_complete_event_rx() without validation against the buffer length. This allows out-of-bounds reads of up to 1020 bytes past the WMI event buffer when the firmware sends an inflated num_msg. Add a check that the buffer is large enough to hold the fixed struct and the num_msg variable-length entries.

References

Community reviews

Loading reviews…