https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 14:59:23 +0000 https://vulnerability.circl.lu/vuln/cve-2023-53341 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>of/fdt: run soc memory setup when early_init_dt_scan_memory fails</p> <p>If memory has been found early_init_dt_scan_memory now returns 1. If it hasn&#39;t found any memory it will return 0, allowing other memory setup mechanisms to carry on.</p> <p>Previously early_init_dt_scan_memory always returned 0 without distinguishing between any kind of memory setup being done or not. Any code path after the early_init_dt_scan memory call in the ramips plat_mem_setup code wouldn&#39;t be executed anymore. Making early_init_dt_scan_memory the only way to initialize the memory.</p> <p>Some boards, including my mt7621 based Cudy X6 board, depend on memory initialization being done via the soc_info.mem_detect function pointer. Those wouldn&#39;t be able to obtain memory and panic the kernel during early bootup with the message &#34;early_init_dt_alloc_memory_arch: Failed to allocate 12416 bytes align=0x40&#34;.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>of/fdt: run soc memory setup when early_init_dt_scan_memory fails</p> <p>If memory has been found early_init_dt_scan_memory now returns 1. If it hasn&#39;t found any memory it will return 0, allowing other memory setup mechanisms to carry on.</p> <p>Previously early_init_dt_scan_memory always returned 0 without distinguishing between any kind of memory setup being done or not. Any code path after the early_init_dt_scan memory call in the ramips plat_mem_setup code wouldn&#39;t be executed anymore. Making early_init_dt_scan_memory the only way to initialize the memory.</p> <p>Some boards, including my mt7621 based Cudy X6 board, depend on memory initialization being done via the soc_info.mem_detect function pointer. Those wouldn&#39;t be able to obtain memory and panic the kernel during early bootup with the message &#34;early_init_dt_alloc_memory_arch: Failed to allocate 12416 bytes align=0x40&#34;.</p> https://vulnerability.circl.lu/vuln/cve-2023-53341