VulnerabilityPublished 26 Oct 2026

CVE-2026-99099: Linux kernel · x86/CPU/AMD: Fix AMD TLBI Erratum #1718

Source GCVE Database

Authoritative record:CVE-2026-99099· Medium

Not known to be exploited · fixed in e3e6779f77ab6f0a1aa80e24868d2d89f31053fe : update Linux kernel when convenient.

Data as of 26 Oct 2026, 16:31 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in e3e6779f77ab6f0a1aa80e24868d2d89f31053fe, 098d80b04d0fe02889c332d061db968f070b83a6, 87db7795cbaaf636ae22ae031f4906db7bb77803

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-rmrm-rhgq-8f8q

What to do

Upgrade Linux kernel to e3e6779f77ab6f0a1aa80e24868d2d89f31053fe, 098d80b04d0fe02889c332d061db968f070b83a6 or 87db7795cbaaf636ae22ae031f4906db7bb77803.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 82378c6c2f435dba66145609de16bf44a9de6303, < e3e6779f77ab6f0a1aa80e24868d2d89f31053fe	Fixed in e3e6779f77ab6f0a1aa80e24868d2d89f31053fe
LinuxLinux	Affected ≥ 82378c6c2f435dba66145609de16bf44a9de6303, < 098d80b04d0fe02889c332d061db968f070b83a6	Fixed in 098d80b04d0fe02889c332d061db968f070b83a6
LinuxLinux	Affected ≥ 82378c6c2f435dba66145609de16bf44a9de6303, < 87db7795cbaaf636ae22ae031f4906db7bb77803	Fixed in 87db7795cbaaf636ae22ae031f4906db7bb77803
LinuxLinux	Affected =6.15	Fixed in–

AI-suggested

A software workaround is implemented in the Linux kernel to detect and mitigate the erratum when a microcode fix is not available. Users should ensure their Linux kernel is updated to a version that includes this fix. If a microcode update is available from AMD, applying it is recommended for hardware-level remediation.

Description

A vulnerability in the Linux kernel related to AMD processors' TLB invalidation has been addressed. The issue involves the processor potentially failing to invalidate a TLB entry when executing an INVLPGB/TLBSYNC instruction pair. A software workaround is applied when a microcode fix is not available to mitigate this erratum.

References

Community reviews

Loading reviews…