CVE Intelligence
Unknown

CVE-2026-99099 — x86/CPU/AMD: Fix AMD TLBI Erratum #1718

In the Linux kernel, the following vulnerability has been resolved: x86/CPU/AMD: Fix AMD TLBI Erratum #1718 The processor may fail to invalidate a TLB entry while executing an INVLPGB/TLBSYNC instruction pair. Detect the erratum and apply a software workaround when a microcode fix is not present.

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

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
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.

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

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux ≥ 82378c6c2f435dba66145609de16bf44a9de6303 and < e3e6779f77ab6f0a1aa80e24868d2d89f31053fe≥ 82378c6c2f435dba66145609de16bf44a9de6303 and < 098d80b04d0fe02889c332d061db968f070b83a6≥ 82378c6c2f435dba66145609de16bf44a9de6303 and < 87db7795cbaaf636ae22ae031f4906db7bb77803version 6.15 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

3 on the record

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

  • CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 9h
  • CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 9h
  • CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 9h
  • CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 9h
  • CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 9h
  • CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 9h

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-99099 is "x86/CPU/AMD: Fix AMD TLBI Erratum #1718", 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.

Sign in or create an account to comment and suggest corrections.