arm64: mm: fix VA-range sanity check
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 14c127c957c1c6070647c171e72f06e0db275ebf · < ab9b4008092c86dc12497af155a0901cc1156999| No fix yet |
| Linux Linux |
|
|
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")
From the CVE record · Linux
The Linux kernel’s arm64 memory-mapping functions use an incorrect check for virtual addresses, potentially rejecting mappings in the KASAN shadow or module regions. The input does not describe an attacker action or specify network access, authentication, or user-interaction conditions.
Engineers running the Linux kernel on arm64 should check their deployments; affected versions are not specified.