CVE-2024-46836: usb: gadget: aspeed_udc: validate endpoint index for ast udc
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: aspeed_udc: validate endpoint index for ast udc
We should verify the bound of the array to assure that host
may not manipulate the index to point past endpoint array.
Found by static analysis.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel USB gadget bug in the aspeed_udc driver. A connected USB host may be able to influence an endpoint index beyond the expected endpoint array. Public sources show a kernel fix, but do not provide CVSS, CWE, impact detail, or evidence of active exploitation.
Executive priority
Treat this as targeted kernel maintenance, not an emergency, unless your fleet uses affected USB gadget functionality. Prioritize embedded, appliance, or hardware-management systems first because exposure depends on this specific driver path.
Technical view
CVE-2024-46836 adds endpoint-index bounds validation in Linux kernel usb gadget aspeed_udc. The source says a host may manipulate the index past the endpoint array, and the issue was found by static analysis. Fixed stable commits are referenced, but public source data does not define the impact class or exploitability.
Likely exposure
Exposure is most likely on Linux systems using affected kernels with the aspeed_udc USB gadget path reachable by a USB host. General Linux servers without this driver or gadget role are likely less exposed, but configuration and vendor backports must be checked.
Exploitation context
The bundle marks KEV as false, and no cited source states active exploitation or public exploit availability. The plausible interaction boundary is a USB host talking to the affected gadget driver, but the sources do not prove practical exploitability or impact.
Researcher notes
The public record is sparse: no CVSS, CWE, exploit status, or detailed impact is provided. The key technical fact is missing bounds validation for an endpoint array index in aspeed_udc. Validate distro backports carefully because kernel version strings alone may mislead.
Mitigation direction
Update affected Linux kernels to vendor releases containing the referenced stable fixes.
For Debian LTS systems, review and apply the January 2025 kernel security update if applicable.
If updates are unavailable, request a vendor backport of the endpoint-index validation fix.
Track inclusion of the referenced kernel.org stable commits in maintained kernel branches.
Validation and detection
Identify systems running affected Linux kernel branches listed in the CVE data.
Confirm whether the aspeed_udc USB gadget driver is enabled or present.
Compare distro kernel changelogs against the referenced stable commit fixes.
Check vendor advisories for backported fixes before relying on upstream version numbers.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-46836 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.