Unknown

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 tee_dyn_shm_alloc_helper() tee_dyn_shm_alloc_helper() derives nr_pages from a caller-supplied size and passes it to alloc_pages_exact() without checking it. For size == 0 nr_pages is 0, and alloc_pages_exact(0) calls get_order(0), which is documented as undefined and returns BITS_PER_LONG - PAGE_SHIFT. The page allocator then trips its order > MAX_PAGE_ORDER warning and fails the allocation; on a panic_on_warn kernel that ends the boot. This can be triggered by TEE_IOC_SHM_ALLOC with struct tee_ioctl_shm_alloc_data where size is 0. Reject a zero page count, as register_shm_helper() already does for the register path.

Published Oct 26, 2026 · Updated Oct 26, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

No scoring signals.

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ cf4441503e20a0c0a36e0a98dcf57de3d3844c91 and < e5dc7af9c3a5373ee7a84959126e7dfa9e4ad50d≥ cf4441503e20a0c0a36e0a98dcf57de3d3844c91 and < 65cb86860a80ffc6af897d53f5bd4b1733bca0ec≥ cf4441503e20a0c0a36e0a98dcf57de3d3844c91 and < c2a97703359e25ec7ef8b2b0ef32fb3982add90a≥ cf4441503e20a0c0a36e0a98dcf57de3d3844c91 and < b7f925fd5226deb953c8dcdc9677d3fcc2717c00version 6.10	Vulnerable	CVE Program (cve.org) e CISA ADP

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 26, 2026
Affected products added · linux/linux
Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 26, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 26, 2026 · Alertas do Telegram
CVE published
Oct 26, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 26, 2026 – Oct 26, 2026
1× Official description updated · Oct 26, 2026 – Oct 26, 2026

References

4 on the record

git.kernel.org/stable/c/e5dc7af9c3a5373ee7a84959126e7dfa9e4ad50d
NIST National Vulnerability Database
git.kernel.org/stable/c/b7f925fd5226deb953c8dcdc9677d3fcc2717c00
NIST National Vulnerability Database
git.kernel.org/stable/c/65cb86860a80ffc6af897d53f5bd4b1733bca0ec
NIST National Vulnerability Database
git.kernel.org/stable/c/c2a97703359e25ec7ef8b2b0ef32fb3982add90a
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 1d
Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 1d
Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 1d
Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 1d
Unknown CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 1d
Unknown CVE-2026-99099 x86/CPU/AMD: Fix AMD TLBI Erratum #1718 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-99097 is "tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.