CVE-2026-93119usb: ljca: bound bank_num in ljca_enumerate_gpio()
- —Not scoredno CVSS score yet
- 0.20%Exploitation in 30 daysEPSS · top 90% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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[].
Timeline
ID reserved
By Linux
Published
- 32 days later
· 32 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.20% · top 90% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected acd6199f195d6de814ac4090ce0864a613b1580e – < 0069593170a3d177de793c9a0b36989c4f069111
- affected acd6199f195d6de814ac4090ce0864a613b1580e – < aed958c4f784a29cf42abb3e54af51a16bddde46
- affected acd6199f195d6de814ac4090ce0864a613b1580e – < 9c4bc8f7426aa001387800bf0140bfc5087a6de3
- affected acd6199f195d6de814ac4090ce0864a613b1580e – < dd9483726d0f16c1a56879c3edb65128259a4e2b
- affected 6.7
- unaffected < 6.7
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/0069593170a3d177de793c9a0b36989c4f069111 (opens in a new tab)
- https://git.kernel.org/stable/c/aed958c4f784a29cf42abb3e54af51a16bddde46 (opens in a new tab)
- https://git.kernel.org/stable/c/9c4bc8f7426aa001387800bf0140bfc5087a6de3 (opens in a new tab)
- https://git.kernel.org/stable/c/dd9483726d0f16c1a56879c3edb65128259a4e2b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-82227 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93119)Record last updated .