]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
arm64: mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
authorCatalin Marinas <catalin.marinas@arm.com>
Thu, 20 Feb 2025 15:58:01 +0000 (15:58 +0000)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 13 Mar 2025 11:50:47 +0000 (12:50 +0100)
commit4969dcc05bc3fe25eb56ed3015773dd2b6604967
tree87741016cca9cf8f6abc05786cf1c9145f17e97d
parentc4041b6b0a7a3def8cf3f3d6120ff337bc4c40f7
arm64: mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings

PROT_MTE (memory tagging extensions) is not supported on all user mmap()
types for various reasons (memory attributes, backing storage, CoW
handling). The arm64 arch_validate_flags() function checks whether the
VM_MTE_ALLOWED flag has been set for a vma during mmap(), usually by
arch_calc_vm_flag_bits().

Linux prior to 6.13 does not support PROT_MTE hugetlb mappings. This was
added by commit 25c17c4b55de ("hugetlb: arm64: add mte support").
However, earlier kernels inadvertently set VM_MTE_ALLOWED on
(MAP_ANONYMOUS | MAP_HUGETLB) mappings by only checking for
MAP_ANONYMOUS.

Explicitly check MAP_HUGETLB in arch_calc_vm_flag_bits() and avoid
setting VM_MTE_ALLOWED for such mappings.

Fixes: 9f3419315f3c ("arm64: mte: Add PROT_MTE support to mmap() and mprotect()")
Cc: <stable@vger.kernel.org> # 5.10.x-6.12.x
Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
arch/arm64/include/asm/mman.h