CVE-2026-99097: Linux kernel · tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e5dc7af9c3a5373ee7a84959126e7dfa9e4ad50d : patch Linux kernel soon.
Data as of 26 Oct 2026, 15:16 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in e5dc7af9c3a5373ee7a84959126e7dfa9e4ad50d, c2a97703359e25ec7ef8b2b0ef32fb3982add90a, b7f925fd5226deb953c8dcdc9677d3fcc2717c00 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to e5dc7af9c3a5373ee7a84959126e7dfa9e4ad50d, c2a97703359e25ec7ef8b2b0ef32fb3982add90a, b7f925fd5226deb953c8dcdc9677d3fcc2717c00 or 65cb86860a80ffc6af897d53f5bd4b1733bca0ec.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in specific Linux kernel commits. Users should update to a Linux kernel version that includes these fixes. No additional mitigation is required beyond applying the official patch.
Description
A vulnerability in the Linux kernel's tee subsystem allows zero-sized allocations in tee_dyn_shm_alloc_helper(), leading to a kernel allocation failure and potential boot panic on systems with panic_on_warn enabled. This occurs because the function does not check for zero size before calling alloc_pages_exact(), which results in an invalid page order. The issue is triggered via TEE_IOC_SHM_ALLOC with a zero size parameter and has been fixed in specific commits.
References
- git.kernel.org/stable/c/e5dc7af9c3a5373ee7a84959126e7dfa9e4ad50d (opens in a new tab)
- git.kernel.org/stable/c/65cb86860a80ffc6af897d53f5bd4b1733bca0ec (opens in a new tab)
- git.kernel.org/stable/c/c2a97703359e25ec7ef8b2b0ef32fb3982add90a (opens in a new tab)
- git.kernel.org/stable/c/b7f925fd5226deb953c8dcdc9677d3fcc2717c00 (opens in a new tab)