Skip to content
Heist/ feed
Back to feed
MediumFix available

of/fdt: run soc memory setup when early_init_dt_scan_memory fails

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: of/fdt: run soc memory setup when early_init_dt_scan_memory fails If memory has been found early_init_dt_scan_memory now returns 1. If it hasn't found any memory it will return 0, allowing other memory setup mechanisms to carry on. 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't be executed anymore. Making early_init_dt_scan_memory the only way to initialize the memory. 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't be able to obtain memory and panic the kernel during early bootup with the message "early_init_dt_alloc_memory_arch: Failed to allocate 12416 bytes align=0x40".

Products
Kernel
Affected versions
Not specified
Fixed versions
6.0.19, 6.1.5
CVEs
CVE-2023-53341
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 10:33 UTC · Revision 1

Source evidence

of/fdt: run soc memory setup when early_init_dt_scan_memory fails

core-osv · Original source

Published 17 Sept 2025, 14:56 UTC

In the Linux kernel, the following vulnerability has been resolved: of/fdt: run soc memory setup when early_init_dt_scan_memory fails If memory has been found early_init_dt_scan_memory now returns 1. If it hasn't found any memory it will return 0, allowing other memory setup mechanisms to carry on. 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't be executed anymore. Making early_init_dt_scan_memory the only way to initialize the memory. 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't be able to obtain memory and panic the kernel during early bootup with the message "early_init_dt_alloc_memory_arch: Failed to allocate 12416 bytes align=0x40".

osv:CVE-2023-53341

Kernel

Fixed versions: 6.0.19, 6.1.5

Complete source record
{
  "id": "a38a118addfcaf848f75356a825b8b0b5a7a883d433e2e15b6b9e1f23e2aa1d2",
  "url": "https://osv.dev/vulnerability/CVE-2023-53341",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "of/fdt: run soc memory setup when early_init_dt_scan_memory fails",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: of/fdt: run soc memory setup when early_init_dt_scan_memory fails If memory has been found early_init_dt_scan_memory now returns 1. If it hasn't found any memory it will return 0, allowing other memory setup mechanisms to carry on. 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't be executed anymore. Making early_init_dt_scan_memory the only way to initialize the memory. 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't be able to obtain memory and panic the kernel during early bootup with the message \"early_init_dt_alloc_memory_arch: Failed to allocate 12416 bytes align=0x40\".",
    "evidence": "osv:CVE-2023-53341",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.0.19",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.1.5",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "CVE-2023-53341",
      "aliases": [
        "CVE-2023-53341"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "1f012283e9360fb4007308f04cfaeb205e34b684"
                },
                {
                  "fixed": "04836fc5b720dfa32ff781383d84f63019abf9b9"
                },
                {
                  "fixed": "c4849f18185fd4e93b04cd45552f8d68c0240e21"
                },
                {
                  "fixed": "2a12187d5853d9fd5102278cecef7dac7c8ce7ea"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53341.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.17.0"
                },
                {
                  "fixed": "6.0.19"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.1.0"
                },
                {
                  "fixed": "6.1.5"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53341.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:27.984017698Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/04836fc5b720dfa32ff781383d84f63019abf9b9",
        "https://git.kernel.org/stable/c/2a12187d5853d9fd5102278cecef7dac7c8ce7ea",
        "https://git.kernel.org/stable/c/c4849f18185fd4e93b04cd45552f8d68c0240e21",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53341.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2023-53341",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53341.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2023-53341",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 494556,
  "published_at": "2025-09-17T14:56:34.671+00:00"
}