cve.bz

CVE-2026-99017 linux linux

7.0 highEPSS 0.2%Fix available

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

On this page
In the Linux kernel, the following vulnerability has been resolved: riscv: errata: select RISCV_ALTERNATIVE_EARLY for THEAD GHOSTWRITE errata_probe_ghostwrite() only marks the CPU as vulnerable when it is called at the RISCV_ALTERNATIVES_EARLY_BOOT stage, and the mitigation in ghostwrite_enable_mitigation() only takes effect if the vulnerable state was recorded before the boot alternatives are patched. The early boot stage is only executed when CONFIG_RISCV_ALTERNATIVE_EARLY is enabled, which currently is only selected by ERRATA_THEAD_MAE. In a kernel built with ERRATA_THEAD_GHOSTWRITE=y but ERRATA_THEAD_MAE=n, the early alternatives never run, so ghostwrite_state is never set to VULNERABLE: ghostwrite_enable_mitigation() returns false, xtheadvector remains enabled, and sysfs reports "Not affected" on a vulnerable T-Head C9xx CPU. Select RISCV_ALTERNATIVE_EARLY from ERRATA_THEAD_GHOSTWRITE so that the vulnerability is detected in the early boot stage and the default mitigation is applied.

Severity

CVSS 3.1

7.0 high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 6th 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-99017 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99017?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99017?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-99017 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-99017

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-99017](https://cve.bz/cve/badge/CVE-2026-99017.svg)](https://cve.bz/cve/CVE-2026-99017)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

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

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 Moderate impact because exploitation requires local access on specific hardware architectures and depends on an uncommon kernel compile-time configuration. Standard Red Hat Enterprise Linux distributions do not support or distribute kernels for the RISC-V architecture, meaning Red Hat environments are not directly affected by this flaw. On platforms where applicable, bypassing early processor errata discovery prevents runtime mitigation of the Ghostwrite issue, leaving unprivileged local processes capable of corrupting system memory.

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 enable early boot alternatives probing by ensuring CONFIG_RISCV_ALTERNATIVE_EARLY is active in kernel builds supporting T-Head Ghostwrite errata mitigations: upgrade to the fixed Kernel/Kernel Ivos Qualcomm builds, which select RISCV_ALTERNATIVE_EARLY automatically when ERRATA_THEAD_GHOSTWRITE is enabled in Kconfig, closing execution of xtheadvector instruction sequences by an unprivileged local user. Until patched, this is only a concern on RISC-V systems utilizing vulnerable T-Head C9xx processors running kernels configured with CONFIG_ERRATA_THEAD_GHOSTWRITE=y and CONFIG_ERRATA_THEAD_MAE=n — Non-RISC-V architectures and standard Red Hat Enterprise Linux distributions that do not support RISC-V are unaffected — so Restrict untrusted local user access and execution on affected RISC-V hosts, or recompile the kernel with CONFIG_ERRATA_THEAD_MAE=y so early alternatives execute. As a compensating measure, Deploy SELinux in enforcing mode to confine compromised processes to their domain if Ghostwrite memory corruption occurs and Map unprivileged local user sessions to confined SELinux domains to restrict post-exploitation access following hardware memory manipulation. These controls limit blast radius and contain exploitation, but they do not fix the underlying missing early boot errata selection defect — 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-10Not 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-99017.

References

Check your stackJSON