xhci: Fix NULL pointer dereference when reading portli debugfs files
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
xhci: Fix NULL pointer dereference when reading portli debugfs files
Michal reported and debgged a NULL pointer dereference bug in the recently added portli debugfs files
Oops is caused when there are more port registers counted in xhci->max_ports than ports reported by Supported Protocol capabilities. This is possible if max_ports is more than maximum port number, or if there are gaps between ports of different speeds the 'Supported Protocol' capabilities.
In such cases port->rhub will be NULL so we can't reach xhci behind it. Add an explicit NULL check for this case, and print portli in hex without dereferencing port->rhub.
From the CVE record · Linux
The Linux kernel’s xHCI portli debugfs files can trigger a NULL pointer dereference when read. This occurs if the counted port registers exceed the ports reported by Supported Protocol capabilities, or if there are gaps between ports of different speeds. The input does not specify authentication or access requirements for reading the files.
Engineers running Linux kernels with the affected xHCI portli debugfs files should check their versions; no affected versions are specified.