Skip to main content
VulnerabilityPublished Updated

CVE-2026-68350: Linux kernel · wifi: carl9170: fix OOB read from off-by-two in TX status handler

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in fab6ff91d5b8c4af62e2ced42fb357fa3eb9fd59 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
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-11-06.

Patch
Available – fixed in fab6ff91d5b8c4af62e2ced42fb357fa3eb9fd59, e8a862a3da457ddc50633c346dc645d559da09ae, a3f42f1049ad80c65560d2b078ad426c3134f78d +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c, < fab6ff91d5b8c4af62e2ced42fb357fa3eb9fd59
Fixed in
  • fab6ff91d5b8c4af62e2ced42fb357fa3eb9fd59
LinuxLinuxAffected
  • ≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c, < e8a862a3da457ddc50633c346dc645d559da09ae
Fixed in
  • e8a862a3da457ddc50633c346dc645d559da09ae
LinuxLinuxAffected
  • ≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c, < a3f42f1049ad80c65560d2b078ad426c3134f78d
Fixed in
  • a3f42f1049ad80c65560d2b078ad426c3134f78d
LinuxLinuxAffected
  • ≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c, < 73462e8e602047a03e538d971a79ad67a4ba9a5d
Fixed in
  • 73462e8e602047a03e538d971a79ad67a4ba9a5d
LinuxLinuxAffected
  • ≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c, < 423c836f934814b8fdbe53b24a79d021a0ee8454
Fixed in
  • 423c836f934814b8fdbe53b24a79d021a0ee8454
LinuxLinuxAffected
  • ≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c, < 9bf8d8510b7bed20320dead0f8cdcf8e610ec8db
Fixed in
  • 9bf8d8510b7bed20320dead0f8cdcf8e610ec8db

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: carl9170: fix OOB read from off-by-two in TX status handler The bounds check in carl9170_tx_process_status() uses `i > ((cmd->hdr.len / 2) + 1)` which is off by two, allowing 2 extra iterations past valid _tx_status entries when the firmware- controlled hdr.ext exceeds hdr.len/2. Fix by using the correct comparison `i >= (cmd->hdr.len / 2)`.

References

Community reviews

Loading reviews…