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".