usb: xhci: Fix NULL pointer dereference on certain command aborts
- 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 5.4.291, 5.10.235, 5.15.179, 6.1.129, 6.6.76, and 2 more
- 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: xhci: Fix NULL pointer dereference on certain command aborts If a command is queued to the final usable TRB of a ring segment, the enqueue pointer is advanced to the subsequent link TRB and no further. If the command is later aborted, when the abort completion is handled the dequeue pointer is advanced to the first TRB of the next segment. If no further commands are queued, xhci_handle_stopped_cmd_ring() sees the ring pointers unequal and assumes that there is a pending command, so it calls xhci_mod_cmd_timer() which crashes if cur_cmd was NULL. Don't attempt timer setup if cur_cmd is NULL. The subsequent doorbell ring likely is unnecessary too, but it's harmless. Leave it alone. This is probably Bug 219532, but no confirmation has been received. The issue has been independently reproduced and confirmed fixed using a USB MCU programmed to NAK the Status stage of SET_ADDRESS forever. Everything continued working normally after several prevented crashes.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From c311e391a7efd101250c0e123286709b7e736249 · fixed in fd8bfaeba4a85b14427899adec0efb3954300653; From c311e391a7efd101250c0e123286709b7e736249 · fixed in b44253956407046e5907d4d72c8fa5b93ae94485; From c311e391a7efd101250c0e123286709b7e736249 · fixed in cf30300a216a4f8dce94e11781a866a09d4b50d4; From c311e391a7efd101250c0e123286709b7e736249 · fixed in 4ff18870af793ce2034a6ad746e91d0a3d985b88; From c311e391a7efd101250c0e123286709b7e736249 · fixed in b649f0d5bc256f691c7d234c3986685d54053de1; From c311e391a7efd101250c0e123286709b7e736249 · fixed in ae069cd2ba09a2bd6a87a68c59ef0b7ea39cd641; From c311e391a7efd101250c0e123286709b7e736249 · fixed in 0ce5c0dac768be14afe2426101b568a0f66bfc4d; From c311e391a7efd101250c0e123286709b7e736249 · fixed in 1e0a19912adb68a4b2b74fd77001c96cd83eb073
- Linux Linux
3.16
- KernelLinux
From 3.16.0 · fixed in 5.4.291; From 5.5.0 · fixed in 5.10.235; From 5.11.0 · fixed in 5.15.179; From 5.16.0 · fixed in 6.1.129; From 6.2.0 · fixed in 6.6.76; From 6.7.0 · fixed in 6.12.13; From 6.13.0 · fixed in 6.13.2
References 8
git.kernel.org
- stable/c/fd8bfaeba4a85b14427899adec0efb3954300653
- stable/c/b44253956407046e5907d4d72c8fa5b93ae94485
- stable/c/cf30300a216a4f8dce94e11781a866a09d4b50d4
- stable/c/4ff18870af793ce2034a6ad746e91d0a3d985b88
- stable/c/b649f0d5bc256f691c7d234c3986685d54053de1
- stable/c/ae069cd2ba09a2bd6a87a68c59ef0b7ea39cd641
- stable/c/0ce5c0dac768be14afe2426101b568a0f66bfc4d
- stable/c/1e0a19912adb68a4b2b74fd77001c96cd83eb073