CVE-2023-53341

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> of/fdt: run soc memory setup when early_init_dt_scan_memory fails<br /> <br /> If memory has been found early_init_dt_scan_memory now returns 1. If<br /> it hasn&amp;#39;t found any memory it will return 0, allowing other memory<br /> setup mechanisms to carry on.<br /> <br /> Previously early_init_dt_scan_memory always returned 0 without<br /> distinguishing between any kind of memory setup being done or not. Any<br /> code path after the early_init_dt_scan memory call in the ramips<br /> plat_mem_setup code wouldn&amp;#39;t be executed anymore. Making<br /> early_init_dt_scan_memory the only way to initialize the memory.<br /> <br /> Some boards, including my mt7621 based Cudy X6 board, depend on memory<br /> initialization being done via the soc_info.mem_detect function<br /> pointer. Those wouldn&amp;#39;t be able to obtain memory and panic the kernel<br /> during early bootup with the message "early_init_dt_alloc_memory_arch:<br /> Failed to allocate 12416 bytes align=0x40".