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: if ((virt >= PAGE_END) && (virt < VMALLOC_START)) { [ ... warning here ... ] return; } ... 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: c1cc1552616d0f35 ("arm64: MMU initialisation") ... the condition was: if (virt < VMALLOC_START) { [ ... warning here ... ] return; } At the time, VMALLOC_START was the lowest kernel address, and this was checking whether 'virt' would be translated via TTBR1. Subsequently in commit: 14c127c957c1c607 ("arm64: mm: Flip kernel VA space") ... the condition was changed to: if ((virt >= VA_START) && (virt < VMALLOC_START)) { [ ... warning here ... ] return; } 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: 77ad4ce69321abbe ("arm64: memory: rename VA_START to PAGE_END") ... keeping the erroneous condition as: if ((virt >= PAGE_END) && (virt < VMALLOC_START)) { [ ... warning here ... ] return; } 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.

• 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

Published

Dec 24, 2025

Last Modified

Jun 17, 2026

Status

Deferred

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2023-53983Anevia Flamingo XL/XS 3.6.20 contains a critical vulnerabili…9.8
• CVE-2023-53984Clevo HotKey Clipboard 2.1.0.6 contains an unquoted service …8.5
• CVE-2023-53985Zstore, now referred to as Zippy CRM, 6.5.4 contains a refle…6.1
• CVE-2023-53986In the Linux kernel, the following vulnerability has been re…8.6
• CVE-2023-53987In the Linux kernel, the following vulnerability has been re…
• CVE-2023-53988In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2023-5399 A CWE-22: Improper Limitation of a Pathname to a Restri…9.8
• CVE-2023-53990In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2023-53991In the Linux kernel, the following vulnerability has been re…
• CVE-2023-53992In the Linux kernel, the following vulnerability has been re…
• CVE-2023-53993In the Linux kernel, the following vulnerability has been re…
• CVE-2023-53994In the Linux kernel, the following vulnerability has been re…