cve.bz

CVE-2026-99099 linux linux

7.8 highEPSS 0.1%Fix available

High (7.8) in linux linux. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-99099 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99099?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99099?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-99099 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-99099

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-99099](https://cve.bz/cve/badge/CVE-2026-99099.svg)](https://cve.bz/cve/CVE-2026-99099)

HTML:

<a href="https://cve.bz/cve/CVE-2026-99099"><img src="https://cve.bz/cve/badge/CVE-2026-99099.svg" alt="CVE-2026-99099"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.15 and later

Fixed in

ProductRelease lineFixed in
Linux6.186.18.57
Linux7.27.2.11
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux7.2.11-1DEBIAN-CVE-2026-99099
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-99099
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-99099
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-99099
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2026-99099
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-99099 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-99099 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-99099 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-43.43~24.04.1UBUNTU-CVE-2026-99099 USN-9018-2
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-99099 USN-9020-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 27 moreno fix listedUBUNTU-CVE-2026-99099
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-43.43.1~24.04.2UBUNTU-CVE-2026-99099
Ubuntu26.04:LTSlinux7.0.0-43.43UBUNTU-CVE-2026-99099 USN-9018-1
15 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquitastreamlinux-lts6.18.58-r0BELL-CVE-2026-99099

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as having a Moderate impact for Red Hat because successful exploitation requires local user access and complex timing to trigger the erratum on specific AMD hardware. The issue cannot be exploited remotely and depends on processor-level broadcast invalidation instructions that are not present or enabled in earlier enterprise distributions such as Red Hat Enterprise Linux 7, 8, and 9. On supported platforms utilizing these instructions without platform microcode workarounds, an authenticated local attacker could potentially access stale address translations to cause memory corruption or a denial of service.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-11-02) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to apply updated AMD processor microcode or emit an additional TLBSYNC instruction during kernel TLB invalidation flushes on Zen 5 processors: upgrade to Linux kernel 6.18.57, 7.2.11, 7.3+ (or the fixed Kernel/Kernel Ivos Qualcomm builds), which detect the erratum during Zen 5 initialization to set X86_BUG_TLBI and emit an additional TLBSYNC instruction in __tlbsync() when the bug flag is present, closing stale TLB mapping reuse. Until patched, this is only a concern on Linux systems running on affected AMD Zen 5 hardware supporting INVLPGB without microcode remediation — systems with CPU microcode fix TLBSYNC_SFW_NO and platforms without INVLPGB instruction support are unaffected — so restrict unprivileged local user access and apply updated processor microcode addressing erratum 1718. As a compensating measure, run SELinux in enforcing mode to provide OS containment and constrain post-exploitation actions if stale TLB translation reuse occurs. These controls limit blast radius and contain exploitation, but they do not fix the underlying TLB invalidation hardware erratum — apply the upstream patch to fully remediate.

Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-99099.

References

Check your stackJSON