{"api_version":"1","generated_at":"2026-06-05T05:13:20+00:00","cve":"CVE-2023-53989","urls":{"html":"https://cve.report/CVE-2023-53989","api":"https://cve.report/api/cve/CVE-2023-53989.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2023-53989","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2023-53989"},"summary":{"title":"arm64: mm: fix VA-range sanity check","description":"In the Linux kernel, the following vulnerability has been resolved:\n\narm64: mm: fix VA-range sanity check\n\nBoth create_mapping_noalloc() and update_mapping_prot() sanity-check\ntheir 'virt' parameter, but the check itself doesn't make much sense.\nThe condition used today appears to be a historical accident.\n\nThe sanity-check condition:\n\n\tif ((virt >= PAGE_END) && (virt < VMALLOC_START)) {\n\t\t[ ... warning here ... ]\n\t\treturn;\n\t}\n\n... can only be true for the KASAN shadow region or the module region,\nand there's no reason to exclude these specifically for creating and\nupdateing mappings.\n\nWhen arm64 support was first upstreamed in commit:\n\n  c1cc1552616d0f35 (\"arm64: MMU initialisation\")\n\n... the condition was:\n\n\tif (virt < VMALLOC_START) {\n\t\t[ ... warning here ... ]\n\t\treturn;\n\t}\n\nAt the time, VMALLOC_START was the lowest kernel address, and this was\nchecking whether 'virt' would be translated via TTBR1.\n\nSubsequently in commit:\n\n  14c127c957c1c607 (\"arm64: mm: Flip kernel VA space\")\n\n... the condition was changed to:\n\n\tif ((virt >= VA_START) && (virt < VMALLOC_START)) {\n\t\t[ ... warning here ... ]\n\t\treturn;\n\t}\n\nThis appear to have been a thinko. The commit moved the linear map to\nthe bottom of the kernel address space, with VMALLOC_START being at the\nhalfway point. The old condition would warn for changes to the linear\nmap below this, and at the time VA_START was the end of the linear map.\n\nSubsequently we cleaned up the naming of VA_START in commit:\n\n  77ad4ce69321abbe (\"arm64: memory: rename VA_START to PAGE_END\")\n\n... keeping the erroneous condition as:\n\n\tif ((virt >= PAGE_END) && (virt < VMALLOC_START)) {\n\t\t[ ... warning here ... ]\n\t\treturn;\n\t}\n\nCorrect the condition to check against the start of the TTBR1 address\nspace, which is currently PAGE_OFFSET. This simplifies the logic, and\nmore clearly matches the \"outside kernel range\" message in the warning.","state":"PUBLISHED","assigner":"Linux","published_at":"2025-12-24 11:15:51","updated_at":"2026-06-01 17:16:25"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/ab9b4008092c86dc12497af155a0901cc1156999","name":"https://git.kernel.org/stable/c/ab9b4008092c86dc12497af155a0901cc1156999","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c7a9e967cc9615a1dabc5e0e6fdbe88a172d5a5b","name":"https://git.kernel.org/stable/c/c7a9e967cc9615a1dabc5e0e6fdbe88a172d5a5b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b03c7fcc5ed854d0e1b27e9abf12428bfa751a37","name":"https://git.kernel.org/stable/c/b03c7fcc5ed854d0e1b27e9abf12428bfa751a37","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/621619f626cbe702ddbdc54117f3868b8ebd8129","name":"https://git.kernel.org/stable/c/621619f626cbe702ddbdc54117f3868b8ebd8129","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/32020fc2a8373d3de35ae6d029d5969a42651e7a","name":"https://git.kernel.org/stable/c/32020fc2a8373d3de35ae6d029d5969a42651e7a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9d8d3df71516ec3236d8d93ff029d251377ba4b1","name":"https://git.kernel.org/stable/c/9d8d3df71516ec3236d8d93ff029d251377ba4b1","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53989","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53989","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 14c127c957c1c6070647c171e72f06e0db275ebf 9d8d3df71516ec3236d8d93ff029d251377ba4b1 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 14c127c957c1c6070647c171e72f06e0db275ebf 32020fc2a8373d3de35ae6d029d5969a42651e7a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 14c127c957c1c6070647c171e72f06e0db275ebf 621619f626cbe702ddbdc54117f3868b8ebd8129 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 14c127c957c1c6070647c171e72f06e0db275ebf c7a9e967cc9615a1dabc5e0e6fdbe88a172d5a5b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 14c127c957c1c6070647c171e72f06e0db275ebf b03c7fcc5ed854d0e1b27e9abf12428bfa751a37 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 14c127c957c1c6070647c171e72f06e0db275ebf ab9b4008092c86dc12497af155a0901cc1156999 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.4","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.4 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.4.251 5.4.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.10.188 5.10.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.15.150 5.15.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.1.175 6.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.4.7 6.4.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.5 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2023","cve_id":"53989","cve":"CVE-2023-53989","epss":"0.000510000","percentile":"0.163290000","score_date":"2026-06-04","updated_at":"2026-06-05 00:02:15"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["arch/arm64/mm/mmu.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"9d8d3df71516ec3236d8d93ff029d251377ba4b1","status":"affected","version":"14c127c957c1c6070647c171e72f06e0db275ebf","versionType":"git"},{"lessThan":"32020fc2a8373d3de35ae6d029d5969a42651e7a","status":"affected","version":"14c127c957c1c6070647c171e72f06e0db275ebf","versionType":"git"},{"lessThan":"621619f626cbe702ddbdc54117f3868b8ebd8129","status":"affected","version":"14c127c957c1c6070647c171e72f06e0db275ebf","versionType":"git"},{"lessThan":"c7a9e967cc9615a1dabc5e0e6fdbe88a172d5a5b","status":"affected","version":"14c127c957c1c6070647c171e72f06e0db275ebf","versionType":"git"},{"lessThan":"b03c7fcc5ed854d0e1b27e9abf12428bfa751a37","status":"affected","version":"14c127c957c1c6070647c171e72f06e0db275ebf","versionType":"git"},{"lessThan":"ab9b4008092c86dc12497af155a0901cc1156999","status":"affected","version":"14c127c957c1c6070647c171e72f06e0db275ebf","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["arch/arm64/mm/mmu.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.4"},{"lessThan":"5.4","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"5.4.*","status":"unaffected","version":"5.4.251","versionType":"semver"},{"lessThanOrEqual":"5.10.*","status":"unaffected","version":"5.10.188","versionType":"semver"},{"lessThanOrEqual":"5.15.*","status":"unaffected","version":"5.15.150","versionType":"semver"},{"lessThanOrEqual":"6.1.*","status":"unaffected","version":"6.1.175","versionType":"semver"},{"lessThanOrEqual":"6.4.*","status":"unaffected","version":"6.4.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"6.5","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"5.4.251","versionStartIncluding":"5.4","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"5.10.188","versionStartIncluding":"5.4","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"5.15.150","versionStartIncluding":"5.4","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.1.175","versionStartIncluding":"5.4","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.4.7","versionStartIncluding":"5.4","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.5","versionStartIncluding":"5.4","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\narm64: mm: fix VA-range sanity check\n\nBoth create_mapping_noalloc() and update_mapping_prot() sanity-check\ntheir 'virt' parameter, but the check itself doesn't make much sense.\nThe condition used today appears to be a historical accident.\n\nThe sanity-check condition:\n\n\tif ((virt >= PAGE_END) && (virt < VMALLOC_START)) {\n\t\t[ ... warning here ... ]\n\t\treturn;\n\t}\n\n... can only be true for the KASAN shadow region or the module region,\nand there's no reason to exclude these specifically for creating and\nupdateing mappings.\n\nWhen arm64 support was first upstreamed in commit:\n\n  c1cc1552616d0f35 (\"arm64: MMU initialisation\")\n\n... the condition was:\n\n\tif (virt < VMALLOC_START) {\n\t\t[ ... warning here ... ]\n\t\treturn;\n\t}\n\nAt the time, VMALLOC_START was the lowest kernel address, and this was\nchecking whether 'virt' would be translated via TTBR1.\n\nSubsequently in commit:\n\n  14c127c957c1c607 (\"arm64: mm: Flip kernel VA space\")\n\n... the condition was changed to:\n\n\tif ((virt >= VA_START) && (virt < VMALLOC_START)) {\n\t\t[ ... warning here ... ]\n\t\treturn;\n\t}\n\nThis appear to have been a thinko. The commit moved the linear map to\nthe bottom of the kernel address space, with VMALLOC_START being at the\nhalfway point. The old condition would warn for changes to the linear\nmap below this, and at the time VA_START was the end of the linear map.\n\nSubsequently we cleaned up the naming of VA_START in commit:\n\n  77ad4ce69321abbe (\"arm64: memory: rename VA_START to PAGE_END\")\n\n... keeping the erroneous condition as:\n\n\tif ((virt >= PAGE_END) && (virt < VMALLOC_START)) {\n\t\t[ ... warning here ... ]\n\t\treturn;\n\t}\n\nCorrect the condition to check against the start of the TTBR1 address\nspace, which is currently PAGE_OFFSET. This simplifies the logic, and\nmore clearly matches the \"outside kernel range\" message in the warning."}],"providerMetadata":{"dateUpdated":"2026-06-01T16:04:24.944Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/9d8d3df71516ec3236d8d93ff029d251377ba4b1"},{"url":"https://git.kernel.org/stable/c/32020fc2a8373d3de35ae6d029d5969a42651e7a"},{"url":"https://git.kernel.org/stable/c/621619f626cbe702ddbdc54117f3868b8ebd8129"},{"url":"https://git.kernel.org/stable/c/c7a9e967cc9615a1dabc5e0e6fdbe88a172d5a5b"},{"url":"https://git.kernel.org/stable/c/b03c7fcc5ed854d0e1b27e9abf12428bfa751a37"},{"url":"https://git.kernel.org/stable/c/ab9b4008092c86dc12497af155a0901cc1156999"}],"title":"arm64: mm: fix VA-range sanity check","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2023-53989","datePublished":"2025-12-24T10:55:28.461Z","dateReserved":"2025-12-24T10:53:46.175Z","dateUpdated":"2026-06-01T16:04:24.944Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2025-12-24 11:15:51","lastModifiedDate":"2026-06-01 17:16:25","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2023","CveId":"53989","Ordinal":"1","Title":"arm64: mm: fix VA-range sanity check","CVE":"CVE-2023-53989","Year":"2023"},"notes":[{"CveYear":"2023","CveId":"53989","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\narm64: mm: fix VA-range sanity check\n\nBoth create_mapping_noalloc() and update_mapping_prot() sanity-check\ntheir 'virt' parameter, but the check itself doesn't make much sense.\nThe condition used today appears to be a historical accident.\n\nThe sanity-check condition:\n\n\tif ((virt >= PAGE_END) && (virt < VMALLOC_START)) {\n\t\t[ ... warning here ... ]\n\t\treturn;\n\t}\n\n... can only be true for the KASAN shadow region or the module region,\nand there's no reason to exclude these specifically for creating and\nupdateing mappings.\n\nWhen arm64 support was first upstreamed in commit:\n\n  c1cc1552616d0f35 (\"arm64: MMU initialisation\")\n\n... the condition was:\n\n\tif (virt < VMALLOC_START) {\n\t\t[ ... warning here ... ]\n\t\treturn;\n\t}\n\nAt the time, VMALLOC_START was the lowest kernel address, and this was\nchecking whether 'virt' would be translated via TTBR1.\n\nSubsequently in commit:\n\n  14c127c957c1c607 (\"arm64: mm: Flip kernel VA space\")\n\n... the condition was changed to:\n\n\tif ((virt >= VA_START) && (virt < VMALLOC_START)) {\n\t\t[ ... warning here ... ]\n\t\treturn;\n\t}\n\nThis appear to have been a thinko. The commit moved the linear map to\nthe bottom of the kernel address space, with VMALLOC_START being at the\nhalfway point. The old condition would warn for changes to the linear\nmap below this, and at the time VA_START was the end of the linear map.\n\nSubsequently we cleaned up the naming of VA_START in commit:\n\n  77ad4ce69321abbe (\"arm64: memory: rename VA_START to PAGE_END\")\n\n... keeping the erroneous condition as:\n\n\tif ((virt >= PAGE_END) && (virt < VMALLOC_START)) {\n\t\t[ ... warning here ... ]\n\t\treturn;\n\t}\n\nCorrect the condition to check against the start of the TTBR1 address\nspace, which is currently PAGE_OFFSET. This simplifies the logic, and\nmore clearly matches the \"outside kernel range\" message in the warning.","Type":"Description","Title":"arm64: mm: fix VA-range sanity check"}]}}}