{"id":"CVE-2023-53341","state":"PUBLISHED","title":"of/fdt: run soc memory setup when early_init_dt_scan_memory fails","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nof/fdt: run soc memory setup when early_init_dt_scan_memory fails\n\nIf memory has been found early_init_dt_scan_memory now returns 1. If\nit hasn't found any memory it will return 0, allowing other memory\nsetup mechanisms to carry on.\n\nPreviously early_init_dt_scan_memory always returned 0 without\ndistinguishing between any kind of memory setup being done or not. Any\ncode path after the early_init_dt_scan memory call in the ramips\nplat_mem_setup code wouldn't be executed anymore. Making\nearly_init_dt_scan_memory the only way to initialize the memory.\n\nSome boards, including my mt7621 based Cudy X6 board, depend on memory\ninitialization being done via the soc_info.mem_detect function\npointer. Those wouldn't be able to obtain memory and panic the kernel\nduring early bootup with the message \"early_init_dt_alloc_memory_arch:\nFailed to allocate 12416 bytes align=0x40\".","publishedAt":"2025-09-17T14:56:34.671Z","updatedAt":"2026-05-11T19:43:04.514Z","severity":{"score":5.5,"label":"Medium","version":"3.1","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","source":"CISA-ADP"},"assigner":"Linux","products":["Linux Linux"],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"1f012283e9360fb4007308f04cfaeb205e34b684","status":"affected","lessThan":"04836fc5b720dfa32ff781383d84f63019abf9b9","versionType":"git"},{"version":"1f012283e9360fb4007308f04cfaeb205e34b684","status":"affected","lessThan":"c4849f18185fd4e93b04cd45552f8d68c0240e21","versionType":"git"},{"version":"1f012283e9360fb4007308f04cfaeb205e34b684","status":"affected","lessThan":"2a12187d5853d9fd5102278cecef7dac7c8ce7ea","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["arch/mips/ralink/of.c","drivers/of/fdt.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"5.17","status":"affected"},{"version":"0","status":"unaffected","lessThan":"5.17","versionType":"semver"},{"version":"6.0.19","status":"unaffected","lessThanOrEqual":"6.0.*","versionType":"semver"},{"version":"6.1.5","status":"unaffected","lessThanOrEqual":"6.1.*","versionType":"semver"},{"version":"6.2","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["arch/mips/ralink/of.c","drivers/of/fdt.c"]}],"references":["https://git.kernel.org/stable/c/04836fc5b720dfa32ff781383d84f63019abf9b9","https://git.kernel.org/stable/c/c4849f18185fd4e93b04cd45552f8d68c0240e21","https://git.kernel.org/stable/c/2a12187d5853d9fd5102278cecef7dac7c8ce7ea"],"weaknesses":["CWE-908"],"ingestedAt":"2026-10-29T20:06:33.064Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2023/53xxx/CVE-2023-53341.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2023-53341","state":"PUBLISHED","datePublished":"2025-09-17T14:56:34.671Z","dateUpdated":"2026-05-11T19:43:04.514Z","assignerShortName":"Linux","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateReserved":"2025-09-16T16:08:59.565Z"},"containers":{"cna":{"title":"of/fdt: run soc memory setup when early_init_dt_scan_memory fails","descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nof/fdt: run soc memory setup when early_init_dt_scan_memory fails\n\nIf memory has been found early_init_dt_scan_memory now returns 1. If\nit hasn't found any memory it will return 0, allowing other memory\nsetup mechanisms to carry on.\n\nPreviously early_init_dt_scan_memory always returned 0 without\ndistinguishing between any kind of memory setup being done or not. Any\ncode path after the early_init_dt_scan memory call in the ramips\nplat_mem_setup code wouldn't be executed anymore. Making\nearly_init_dt_scan_memory the only way to initialize the memory.\n\nSome boards, including my mt7621 based Cudy X6 board, depend on memory\ninitialization being done via the soc_info.mem_detect function\npointer. Those wouldn't be able to obtain memory and panic the kernel\nduring early bootup with the message \"early_init_dt_alloc_memory_arch:\nFailed to allocate 12416 bytes align=0x40\"."}],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"1f012283e9360fb4007308f04cfaeb205e34b684","status":"affected","lessThan":"04836fc5b720dfa32ff781383d84f63019abf9b9","versionType":"git"},{"version":"1f012283e9360fb4007308f04cfaeb205e34b684","status":"affected","lessThan":"c4849f18185fd4e93b04cd45552f8d68c0240e21","versionType":"git"},{"version":"1f012283e9360fb4007308f04cfaeb205e34b684","status":"affected","lessThan":"2a12187d5853d9fd5102278cecef7dac7c8ce7ea","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["arch/mips/ralink/of.c","drivers/of/fdt.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"5.17","status":"affected"},{"version":"0","status":"unaffected","lessThan":"5.17","versionType":"semver"},{"version":"6.0.19","status":"unaffected","lessThanOrEqual":"6.0.*","versionType":"semver"},{"version":"6.1.5","status":"unaffected","lessThanOrEqual":"6.1.*","versionType":"semver"},{"version":"6.2","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["arch/mips/ralink/of.c","drivers/of/fdt.c"]}],"references":[{"url":"https://git.kernel.org/stable/c/04836fc5b720dfa32ff781383d84f63019abf9b9"},{"url":"https://git.kernel.org/stable/c/c4849f18185fd4e93b04cd45552f8d68c0240e21"},{"url":"https://git.kernel.org/stable/c/2a12187d5853d9fd5102278cecef7dac7c8ce7ea"}],"providerMetadata":{"shortName":"Linux","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateUpdated":"2026-05-11T19:43:04.514Z"},"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.17","versionEndExcluding":"6.0.19"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.17","versionEndExcluding":"6.1.5"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.17","versionEndExcluding":"6.2"}]}]}],"x_generator":{"engine":"bippy-1.2.0"}},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"cvssV3_1":{"scope":"UNCHANGED","version":"3.1","baseScore":5.5,"attackVector":"LOCAL","baseSeverity":"MEDIUM","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","integrityImpact":"NONE","userInteraction":"NONE","attackComplexity":"LOW","availabilityImpact":"HIGH","privilegesRequired":"LOW","confidentialityImpact":"NONE"}},{"other":{"type":"ssvc","content":{"id":"CVE-2023-53341","role":"CISA Coordinator","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"version":"2.0.3","timestamp":"2026-01-14T18:38:45.773957Z"}}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-908","lang":"en","type":"CWE","description":"CWE-908 Use of Uninitialized Resource"}]}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-01-14T18:43:01.930Z"}}]}}}