CVE-2026-93119 usb: ljca: bound bank_num in ljca_enumerate_gpio()

Q: Is CVE-2026-93119 being exploited?

There is no known exploitation of CVE-2026-93119 in the wild and no public exploit code.

Not scored Published 17 Sep 2026 Updated 19 Oct 2026

A malicious USB device can trigger a stack buffer overflow in the Linux kernel LJCA driver, potentially leading to code execution or system crash.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Local or same network only
Victim action needed: Not needed
Fix: Available

What is CVE-2026-93119?

CVE-2026-93119 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

In the Linux kernel, the following vulnerability has been resolved:

usb: ljca: bound bank_num in ljca_enumerate_gpio()

ljca_enumerate_gpio() reads desc->bank_num from the device and loops valid_pin[i] = get_unaligned_le32(...) for i < bank_num. valid_pin[] holds only LJCA_MAX_GPIO_NUM / 32 = 2 entries.

Two checks run before the loop. The reply length must match struct_size(desc, bank_desc, bank_num). The product pins_per_bank * bank_num must not exceed LJCA_MAX_GPIO_NUM. Neither one bounds bank_num against the size of valid_pin[]. The reply is capped at LJCA_MAX_PAYLOAD_SIZE (60) bytes, so the struct_size check limits bank_num to 9. A device that reports bank_num 9 with pins_per_bank 7 still passes both checks. gpio_num is 63 and the reply is 56 bytes. The loop then writes nine u32 into the two entry array and overruns valid_pin[] on the stack.

A broken or malicious LJCA device can therefore overflow the stack. Reject a bank_num that does not fit valid_pin[].

Which versions are affected by CVE-2026-93119?

How do I fix CVE-2026-93119?

Apply the vendor's patch.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-93119 being exploited?