Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

CVE-2026-99097: tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper()

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Fixed version: Linux Linux 65cb86860a80ffc6af897d53f5bd4b1733bca0ec, b7f925fd5226deb953c8dcdc9677d3fcc2717c00, c2a97703359e25ec7ef8b2b0ef32fb3982add90a.

Low priority for now. Upgrade to Linux Linux 65cb86860a80ffc6af897d53f5bd4b1733bca0ec, b7f925fd5226deb953c8dcdc9677d3fcc2717c00, c2a97703359e25ec7ef8b2b0ef32fb3982add90a or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Oct 26, 2026
Updated
Oct 26, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-99097

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.10affected
    • cf4441503e20a0c0a36e0a98dcf57de3d3844c91 and later · before e5dc7af9c3a5373ee7a84959126e7dfa9e4ad50daffected · git
    • cf4441503e20a0c0a36e0a98dcf57de3d3844c91 and later · before 65cb86860a80ffc6af897d53f5bd4b1733bca0ecaffected · git
    • cf4441503e20a0c0a36e0a98dcf57de3d3844c91 and later · before c2a97703359e25ec7ef8b2b0ef32fb3982add90aaffected · git
    • cf4441503e20a0c0a36e0a98dcf57de3d3844c91 and later · before b7f925fd5226deb953c8dcdc9677d3fcc2717c00affected · git
    • before 6.10not affected · semver
    • 6.12.113 and later · up to and including 6.12.*not affected · semver
    • 6.18.57 and later · up to and including 6.18.*not affected · semver
    • 7.2.11 and later · up to and including 7.2.*not affected · semver
    • 7.3 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.11-17.2.11-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-99095Oct 26, 2026 · drm/vc4: drain the hangcheck timer and works on V3D unbind
    0Monitor
  • ← EarlierCVE-2026-99096Oct 26, 2026 · io_uring/register: don't exempt disabled rings from task restrictions
    0Monitor
  • Later →CVE-2026-99098Oct 26, 2026 · dm-integrity: fix buffer overflow in inline mode with large tag size
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux65cb86860a80ffc6af897d53f5bd4b1733bca0ecVendor (CNA)
Linux Linuxb7f925fd5226deb953c8dcdc9677d3fcc2717c00Vendor (CNA)
Linux Linuxc2a97703359e25ec7ef8b2b0ef32fb3982add90aVendor (CNA)
Linux Linuxe5dc7af9c3a5373ee7a84959126e7dfa9e4ad50dVendor (CNA)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 5, 2026+10 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Exploit maturity— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records