CVE-2026-99097: tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper()
In the Linux kernel, the following vulnerability has been resolved:
tee: shm: reject zero-sized allocations in teedynshmallochelper()
teedynshmallochelper() derives nrpages from a caller-supplied size and passes it to allocpagesexact() without checking it. For size == 0 nrpages is 0, and allocpagesexact(0) calls getorder(0), which is documented as undefined and returns BITSPERLONG - PAGESHIFT. The page allocator then trips its order > MAXPAGEORDER warning and fails the allocation; on a paniconwarn kernel that ends the boot.
This can be triggered by TEEIOCSHMALLOC with struct teeioctlshmallocdata where size is 0.
Reject a zero page count, as registershmhelper() already does for the register path.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
azurelinux/kernelto a version that resolves this vulnerability.Fixed in 0:6.18.57-1.1.azl4 - Upgrade
Upgrade
ubuntu/linux-aws-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.18~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-fde-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1019.19~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.19~24.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-43.43~24.04.1 - Upgrade
Upgrade
ubuntu/linux-oracle-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1016.18~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-43.43.1~24.04.2 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.3.0-10.10 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.3.0-1004.5 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-raspito a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.3.0-10.10.1 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.3.0-10.10.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-43.43 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1017.18 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.0.0-1020.21 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.0.0-1019.19 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1017.19 - Upgrade
Upgrade
ubuntu/linux-gketo a version that resolves this vulnerability.Fixed in 7.0.0-1010.11 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1018.18 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1018.18 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-raspito a version that resolves this vulnerability.Fixed in 7.0.0-1023.23 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.0.0-43.43.1 - Compensating control
In tee_dyn_shm_alloc_helper(), reject a zero page count derived from a caller-supplied size before passing it to alloc_pages_exact(); specifically reject TEE_IOC_SHM_ALLOC requests whose tee_ioctl_shm_alloc_data size is 0.
Event History
Frequently Asked Questions
What condition makes this issue capable of ending the boot process?
A zero-sized shared-memory allocation causes the page allocator to emit an order-greater-than-MAX_PAGE_ORDER warning and fail the allocation. On kernels configured with panic_on_warn, that warning ends the boot.
What temporary mitigation is available if the fix cannot be deployed immediately?
Prevent TEE shared-memory allocation requests with a size of zero from reaching the affected allocation path. The vulnerable request is TEE_IOC_SHM_ALLOC with the size field in struct tee_ioctl_shm_alloc_data set to 0.
Is the shared-memory registration path subject to the same missing check?
The data indicates that register_shm_helper() already rejects a zero page count. The missing validation was in the dynamic shared-memory allocation helper used by the allocation path.