CVE-2023-53989
In the Linux kernel, the following vulnerability has been resolved:
arm64: mm: fix VA-range sanity check
Both create_mapping_noalloc() and update_mapping_prot() sanity-check their 'virt' parameter, but the check itself doesn't make much sense. The condition used today appears to be a historical accident.
The sanity-check condition:
... can only be true for the KASAN shadow region or the module region, and there's no reason to exclude these specifically for creating and updateing mappings.
When arm64 support was first upstreamed in commit:
... the condition was:
At the time, VMALLOC_START was the lowest kernel address, and this was checking whether 'virt' would be translated via TTBR1.
Leer descripción completaMostrar menos
Subsequently in commit:
... the condition was changed to:
This appear to have been a thinko. The commit moved the linear map to the bottom of the kernel address space, with VMALLOC_START being at the halfway point. The old condition would warn for changes to the linear map below this, and at the time VA_START was the end of the linear map.
Subsequently we cleaned up the naming of VA_START in commit:
... keeping the erroneous condition as:
Correct the condition to check against the start of the TTBR1 address space, which is currently PAGE_OFFSET. This simplifies the logic, and more clearly matches the "outside kernel range" message in the warning.
Detalles técnicos trazas, registros y código del informe original
if ((virt >= PAGE_END) && (virt < VMALLOC_START)) {
[ ... warning here ... ]
return;
}
c1cc1552616d0f35 ("arm64: MMU initialisation")
if (virt < VMALLOC_START) {
[ ... warning here ... ]
return;
}
14c127c957c1c607 ("arm64: mm: Flip kernel VA space")
if ((virt >= VA_START) && (virt < VMALLOC_START)) {
[ ... warning here ... ]
return;
}
77ad4ce69321abbe ("arm64: memory: rename VA_START to PAGE_END")
if ((virt >= PAGE_END) && (virt < VMALLOC_START)) {
[ ... warning here ... ]
return;
}CVSS
NVD no ha asignado puntuación CVSS a esta CVE (habitual desde el cambio de política de abril de 2026).
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.21%
- Percentil entre todas las CVEs puntuadas: 10
- Fecha de la puntuación: 6/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
Tecnologías afectadas (1)
⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.
Referencias
- https://git.kernel.org/stable/c/32020fc2a8373d3de35ae6d029d5969a42651e7a
- https://git.kernel.org/stable/c/621619f626cbe702ddbdc54117f3868b8ebd8129
- https://git.kernel.org/stable/c/9d8d3df71516ec3236d8d93ff029d251377ba4b1
- https://git.kernel.org/stable/c/ab9b4008092c86dc12497af155a0901cc1156999
- https://git.kernel.org/stable/c/b03c7fcc5ed854d0e1b27e9abf12428bfa751a37
- https://git.kernel.org/stable/c/c7a9e967cc9615a1dabc5e0e6fdbe88a172d5a5b
JSON original (NVD)
Mostrar
{
"id": "CVE-2023-53989",
"cveTags": [],
"metrics": {},
"affected": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"affectedData": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "14c127c957c1c6070647c171e72f06e0db275ebf",
"lessThan": "9d8d3df71516ec3236d8d93ff029d251377ba4b1",
"versionType": "git"
},
{
"status": "affected",
"version": "14c127c957c1c6070647c171e72f06e0db275ebf",
"lessThan": "32020fc2a8373d3de35ae6d029d5969a42651e7a",
"versionType": "git"
},
{
"status": "affected",
"version": "14c127c957c1c6070647c171e72f06e0db275ebf",
"lessThan": "621619f626cbe702ddbdc54117f3868b8ebd8129",
"versionType": "git"
},
{
"status": "affected",
"version": "14c127c957c1c6070647c171e72f06e0db275ebf",
"lessThan": "c7a9e967cc9615a1dabc5e0e6fdbe88a172d5a5b",
"versionType": "git"
},
{
"status": "affected",
"version": "14c127c957c1c6070647c171e72f06e0db275ebf",
"lessThan": "b03c7fcc5ed854d0e1b27e9abf12428bfa751a37",
"versionType": "git"
},
{
"status": "affected",
"version": "14c127c957c1c6070647c171e72f06e0db275ebf",
"lessThan": "ab9b4008092c86dc12497af155a0901cc1156999",
"versionType": "git"
}
],
"programFiles": [
"arch/arm64/mm/mmu.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "5.4"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "5.4",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "5.4.251",
"versionType": "semver",
"lessThanOrEqual": "5.4.*"
},
{
"status": "unaffected",
"version": "5.10.188",
"versionType": "semver",
"lessThanOrEqual": "5.10.*"
},
{
"status": "unaffected",
"version": "5.15.150",
"versionType": "semver",
"lessThanOrEqual": "5.15.*"
},
{
"status": "unaffected",
"version": "6.1.175",
"versionType": "semver",
"lessThanOrEqual": "6.1.*"
},
{
"status": "unaffected",
"version": "6.4.7",
"versionType": "semver",
"lessThanOrEqual": "6.4.*"
},
{
"status": "unaffected",
"version": "6.5",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"arch/arm64/mm/mmu.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2025-12-24T11:15:51.803",
"references": [
{
"url": "https://git.kernel.org/stable/c/32020fc2a8373d3de35ae6d029d5969a42651e7a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/621619f626cbe702ddbdc54117f3868b8ebd8129",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9d8d3df71516ec3236d8d93ff029d251377ba4b1",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ab9b4008092c86dc12497af155a0901cc1156999",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/b03c7fcc5ed854d0e1b27e9abf12428bfa751a37",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/c7a9e967cc9615a1dabc5e0e6fdbe88a172d5a5b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Deferred",
"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."
}
],
"lastModified": "2026-06-17T06:46:29.700",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}