PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 24576899c49509c0d533bcf569139f691d8f7af7, Kernel 2c54b9fca1755e80a343ccfde0652dc5ea4744b2, Kernel 2d2da5a4c1b4509f6f7e5a8db015cd420144beb4 and 4 more.
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: $ cat /proc/iomem 30000000-37ffffff : memory2 38000000-3fffffff : memory3 [kwilczynski: commit log]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.8, >=2a6d0d63d99956a66f6605832f11755d74a41951 <24576899c49509c0d533bcf569139f691d8f7af7, >=2a6d0d63d99956a66f6605832f11755d74a41951 <2c54b9fca1755e80a343ccfde0652dc5ea4744b2, >=2a6d0d63d99956a66f6605832f11755d74a41951 <2d2da5a4c1b4509f6f7e5a8db015cd420144beb4, >=2a6d0d63d99956a66f6605832f11755d74a41951 <44708208c2a4b828a57a2abe7799c9d3962e7eaa, >=2a6d0d63d99956a66f6605832f11755d74a41951 <6987e021b64cbb49981d140bb72d9d1466f191c4, >=2a6d0d63d99956a66f6605832f11755d74a41951 <7a47e14c5fb0b6dba7073be7b0119fb8fe864e01, >=2a6d0d63d99956a66f6605832f11755d74a41951 <9ff46b0bfeb6e0724a4ace015aa7a0b887cdb7c1 | 24576899c49509c0d533bcf569139f691d8f7af7, 2c54b9fca1755e80a343ccfde0652dc5ea4744b2, 2d2da5a4c1b4509f6f7e5a8db015cd420144beb4, 44708208c2a4b828a57a2abe7799c9d3962e7eaa, 6987e021b64cbb49981d140bb72d9d1466f191c4, 7a47e14c5fb0b6dba7073be7b0119fb8fe864e01, 9ff46b0bfeb6e0724a4ace015aa7a0b887cdb7c1 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket