usb: xusbatm: don't rely on id table pointer arithmetic
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.189, 6.6.158, 6.12.111, 6.18.53, 7.2.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: usb: xusbatm: don't rely on id table pointer arithmetic The current code is broken when dynamic ID is involved; in such cases usb_device_id parameter of probe lives on the heap and the pointer arithmetic will get an index that is wildly out of bound. xusbatm initialize the USB device IDs dynamically so it can just use driver_info too. Even with conversion, xusbatm still cannot support dynamic IDs, so also set no_dynamic_id.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 733260ff9c45bd4db60f45d17e8560a4a68dff4d · fixed in ee4006c2175e8b50ff5d47a54bff52eb29bb1f0d; From 733260ff9c45bd4db60f45d17e8560a4a68dff4d · fixed in 5086f5639197f321b766cec0dce383492eaf2305; From 733260ff9c45bd4db60f45d17e8560a4a68dff4d · fixed in fad6cab36474758abf55c6419dd79a06a27fcefc; From 733260ff9c45bd4db60f45d17e8560a4a68dff4d · fixed in 8944ef1bfda537aaf329c82e7a5f9faf61340aa9; From 733260ff9c45bd4db60f45d17e8560a4a68dff4d · fixed in f7db611d98b68d15661561d2cefa774208774ccc; From 733260ff9c45bd4db60f45d17e8560a4a68dff4d · fixed in eb6cd6d3d8abeac5d7e8251b898067184afdad8a
- Linux Linux
2.6.16
- KernelLinux
From 2.6.16 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.7