CVE-2023-53341 (GCVE-0-2023-53341)
Vulnerability from cvelistv5
Published
2025-09-17 14:56
Modified
2025-09-17 14:56
Severity ?
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".
References
Impacted products
Vendor Product Version
Linux Linux Version: 1f012283e9360fb4007308f04cfaeb205e34b684
Version: 1f012283e9360fb4007308f04cfaeb205e34b684
Version: 1f012283e9360fb4007308f04cfaeb205e34b684
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/mips/ralink/of.c",
            "drivers/of/fdt.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "04836fc5b720dfa32ff781383d84f63019abf9b9",
              "status": "affected",
              "version": "1f012283e9360fb4007308f04cfaeb205e34b684",
              "versionType": "git"
            },
            {
              "lessThan": "c4849f18185fd4e93b04cd45552f8d68c0240e21",
              "status": "affected",
              "version": "1f012283e9360fb4007308f04cfaeb205e34b684",
              "versionType": "git"
            },
            {
              "lessThan": "2a12187d5853d9fd5102278cecef7dac7c8ce7ea",
              "status": "affected",
              "version": "1f012283e9360fb4007308f04cfaeb205e34b684",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/mips/ralink/of.c",
            "drivers/of/fdt.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.17"
            },
            {
              "lessThan": "5.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.0.*",
              "status": "unaffected",
              "version": "6.0.19",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.0.19",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.5",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.2",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "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\u0027t 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\u0027t 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\u0027t 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\"."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-09-17T14:56:34.671Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "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"
        }
      ],
      "title": "of/fdt: run soc memory setup when early_init_dt_scan_memory fails",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2023-53341",
    "datePublished": "2025-09-17T14:56:34.671Z",
    "dateReserved": "2025-09-16T16:08:59.565Z",
    "dateUpdated": "2025-09-17T14:56:34.671Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2023-53341\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-09-17T15:15:37.273\",\"lastModified\":\"2025-09-18T13:43:34.310\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"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\u0027t 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\u0027t 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\u0027t 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\\\".\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/04836fc5b720dfa32ff781383d84f63019abf9b9\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/2a12187d5853d9fd5102278cecef7dac7c8ce7ea\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/c4849f18185fd4e93b04cd45552f8d68c0240e21\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.