PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2a6d0d63d99956a66f6605832f11755d74a41951 · < 44708208c2a4b828a57a2abe7799c9d3962e7eaa| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region()
The rcar_pcie_parse_outbound_ranges() uses the devm_request_mem_region() macro to request a needed resource. A string variable that lives on the stack is then used to store a dynamically computed resource name, which is then passed on as one of the macro arguments. This can lead to undefined behavior.
Depending on the current contents of the memory, the manifestations of errors may vary. One possible output may be as follows:
$ cat /proc/iomem 30000000-37ffffff : 38000000-3fffffff :
Sometimes, garbage may appear after the colon.
In very rare cases, if no NULL-terminator is found in memory, the system might crash because the string iterator will overrun which can lead to access of unmapped memory above the stack.
Thus, fix this by replacing outbound_name with the name of the previously requested resource. With the changes applied, the output will be as follows:
From the CVE record · Linux
The Linux kernel’s PCI rcar-ep code passes a stack-backed resource name to devm_request_mem_region(), which can produce incorrect names in /proc/iomem. In rare cases, a string read can run past the stack and crash the system. The input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the PCI rcar-ep component should check their kernel; affected versions are not specified.