CVE-2023-53341: of/fdt: run soc memory setup when early_init_dt_scan_memory fails
In the Linux kernel, the following vulnerability has been resolved:
of/fdt: run soc memory setup when earlyinitdtscanmemory fails
If memory has been found earlyinitdtscanmemory now returns 1. If it hasn't found any memory it will return 0, allowing other memory setup mechanisms to carry on.
Previously earlyinitdtscanmemory always returned 0 without distinguishing between any kind of memory setup being done or not. Any code path after the earlyinitdtscan memory call in the ramips platmemsetup code wouldn't be executed anymore. Making earlyinitdtscanmemory the only way to initialize the memory.
Some boards, including my mt7621 based Cudy X6 board, depend on memory initialization being done via the socinfo.memdetect function pointer. Those wouldn't be able to obtain memory and panic the kernel during early bootup with the message "earlyinitdtallocmemoryarch: Failed to allocate 12416 bytes align=0x40".
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2023-53341?
CVE-2023-53341 has a severity rating of low as it primarily affects memory setup during early initialization.
How do I fix CVE-2023-53341?
To fix CVE-2023-53341, update the Linux kernel to the latest version where this vulnerability has been addressed.
What versions of the Linux kernel are affected by CVE-2023-53341?
CVE-2023-53341 affects several versions of the Linux kernel prior to the fix being implemented.
What does CVE-2023-53341 impact in the Linux kernel?
CVE-2023-53341 impacts the early initialization memory setup process in the Linux kernel.
Is CVE-2023-53341 an exploitation risk?
CVE-2023-53341 does not present a direct remote exploitation risk but could potentially affect system stability.