CVE-2026-93119Hinoki check available

Kernel stack corruption via unchecked GPIO bank count

Published Sep 17, 2026 · Updated Sep 17, 2026

Stack overflow in the LJCA USB driver in Linux 6.7 allows physically proximate attackers to corrupt kernel memory via device replies. In ljca_enumerate_gpio(), the device-supplied bank_num controls writes into the two-entry valid_pin stack array without an array-capacity check, despite reply-length and total-pin validation. Exploitation requires a malicious LJCA device reaching the affected driver; the disclosed result is stack corruption, without demonstrated code execution or a specified crash outcome.

CVSS severity6.8
Medium
EPSS probability0.20%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Stack overflow in the LJCA USB driver in Linux 6.7 allows physically proximate attackers to corrupt kernel memory via device replies. In ljca_enumerate_gpio(), the device-supplied bank_num controls writes into the two-entry valid_pin stack array without an array-capacity check, despite reply-length and total-pin validation. Exploitation requires a malicious LJCA device reaching the affected driver; the disclosed result is stack corruption, without demonstrated code execution or a specified crash outcome.

The record

CVE
CVE-2026-93119
Published
Sep 17, 2026
Updated
Sep 17, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 17, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.7
  2. Affected versionversion=acd6199f195d6de814ac4090ce0864a613b1580e <0069593170a3d177de793c9a0b36989c4f069111
  3. Affected versionversion=acd6199f195d6de814ac4090ce0864a613b1580e <9c4bc8f7426aa001387800bf0140bfc5087a6de3
  4. Affected versionversion=acd6199f195d6de814ac4090ce0864a613b1580e <aed958c4f784a29cf42abb3e54af51a16bddde46
  5. Affected versionversion=acd6199f195d6de814ac4090ce0864a613b1580e <dd9483726d0f16c1a56879c3edb65128259a4e2b

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.7; version=acd6199f195d6de814ac4090ce0864a613b1580e <0069593170a3d177de793c9a0b36989c4f069111; version=acd6199f195d6de814ac4090ce0864a613b1580e <9c4bc8f7426aa001387800bf0140bfc5087a6de3; version=acd6199f195d6de814ac4090ce0864a613b1580e <aed958c4f784a29cf42abb3e54af51a16bddde46; version=acd6199f195d6de814ac4090ce0864a613b1580e <dd9483726d0f16c1a56879c3edb65128259a4e2b

Published CVSS scores

6.8Amazon LinuxCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
5.5SUSECVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started