GHSA-8RMH-4R43-9CJ7
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In 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[].
{
"affected": [],
"aliases": [
"CVE-2026-93119"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:06Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: ljca: bound bank_num in ljca_enumerate_gpio()\n\nljca_enumerate_gpio() reads desc-\u003ebank_num from the device and loops\nvalid_pin[i] = get_unaligned_le32(...) for i \u003c bank_num. valid_pin[]\nholds only LJCA_MAX_GPIO_NUM / 32 = 2 entries.\n\nTwo checks run before the loop. The reply length must match\nstruct_size(desc, bank_desc, bank_num). The product\npins_per_bank * bank_num must not exceed LJCA_MAX_GPIO_NUM. Neither one\nbounds bank_num against the size of valid_pin[]. The reply is capped at\nLJCA_MAX_PAYLOAD_SIZE (60) bytes, so the struct_size check limits\nbank_num to 9. A device that reports bank_num 9 with pins_per_bank 7\nstill passes both checks. gpio_num is 63 and the reply is 56 bytes. The\nloop then writes nine u32 into the two entry array and overruns\nvalid_pin[] on the stack.\n\nA broken or malicious LJCA device can therefore overflow the stack.\nReject a bank_num that does not fit valid_pin[].",
"id": "GHSA-8rmh-4r43-9cj7",
"modified": "2026-09-17T18:32:11Z",
"published": "2026-09-17T18:32:11Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93119"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0069593170a3d177de793c9a0b36989c4f069111"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9c4bc8f7426aa001387800bf0140bfc5087a6de3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/aed958c4f784a29cf42abb3e54af51a16bddde46"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/dd9483726d0f16c1a56879c3edb65128259a4e2b"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.