Описание
In the Linux kernel, the following vulnerability has been resolved:
remoteproc: k3-r5: Fix error handling when power-up failed
By simply bailing out, the driver was violating its rule and internal assumptions that either both or no rproc should be initialized. E.g., this could cause the first core to be available but not the second one, leading to crashes on its shutdown later on while trying to dereference that second instance.
In the Linux kernel, the following vulnerability has been resolved:
remoteproc: k3-r5: Fix error handling when power-up failed
By simply bailing out, the driver was violating its rule and internal assumptions that either both or no rproc should be initialized. E.g., this could cause the first core to be available but not the second one, leading to crashes on its shutdown later on while trying to dereference that second instance.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2024-50176
- https://git.kernel.org/stable/c/7afb5e3aa989c479979faeb18768a67889a7a9c6
- https://git.kernel.org/stable/c/87ab3af7447791d0c619610fd560bd804549e187
- https://git.kernel.org/stable/c/9ab27eb5866ccbf57715cfdba4b03d57776092fb
- https://git.kernel.org/stable/c/afd102bde99d90ef41e043c846ea34b04433eb7b
- https://git.kernel.org/stable/c/fc71c23958931713b5e76f317b76be37189f2516
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Связанные уязвимости
In the Linux kernel, the following vulnerability has been resolved: remoteproc: k3-r5: Fix error handling when power-up failed By simply bailing out, the driver was violating its rule and internal assumptions that either both or no rproc should be initialized. E.g., this could cause the first core to be available but not the second one, leading to crashes on its shutdown later on while trying to dereference that second instance.
In the Linux kernel, the following vulnerability has been resolved: remoteproc: k3-r5: Fix error handling when power-up failed By simply bailing out, the driver was violating its rule and internal assumptions that either both or no rproc should be initialized. E.g., this could cause the first core to be available but not the second one, leading to crashes on its shutdown later on while trying to dereference that second instance.
In the Linux kernel, the following vulnerability has been resolved: remoteproc: k3-r5: Fix error handling when power-up failed By simply bailing out, the driver was violating its rule and internal assumptions that either both or no rproc should be initialized. E.g., this could cause the first core to be available but not the second one, leading to crashes on its shutdown later on while trying to dereference that second instance.
In the Linux kernel, the following vulnerability has been resolved: r ...
Уязвимость компонента remoteproc ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании