BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-89775High confidence

KVM: arm64: Handle negative S1 walk levels in VNCR TLB size evaluation

Linux · Linux

9.3CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.23% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

17 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 13 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 10 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 10 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.2.6-1Debian Security Tracker ↗Source updated 10 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.2.6-1Debian Security Tracker ↗Source updated 10 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 9 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 9 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fde-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 9 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidia-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 9 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 9 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 9 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 9 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 9 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 9 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracle-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 9 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 9 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 9 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 9 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-89775 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: KVM: arm64: Handle negative S1 walk levels in VNCR TLB size evaluation
309 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • kernel-64k-debug-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-debug-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-debug-devel-matched-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-devel-matched-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-devel-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
Summary
A flaw was found in the Linux kernel's Kernel-based Virtual Machine (KVM) for arm64 systems. This issue arises when the system's Memory Management Unit (MMU) is inactive, causing an internal calculation for memory translation buffers (TLB) to misinterpret a negative value. This leads to an incorrect determination of the memory region size for invalidation, resulting in an incomplete cleanup of these buffers. Such an incomplete invalidation could lead to unexpected memory behavior within the virtualized environment.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
CVE-2026-89775 · CSAF 2.0 · revision 4 · interimSUSE Product Security TeamCVE-2026-89775
353 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle negative S1 walk levels in VNCR TLB size evaluation Computing the effects of a TLB invalidation involves looking at the size of the mapping cached by the TLB. For S1 mappings such as VNCR, this is deducted from the combination of the base granule size and the mapping level. However, this implies that the S1 MMU is *on*. When the MMU is off, we indicate this with the level being set to a "creative" value of -127 (S1_MMU_DISABLED). This ends-up being misinterpreted by pgshift_level_to_ttl() as it doesn't handle negative levels at all (the level is immediately cast to a u8 and only the bottom two bits considered), leading to an invalidation size of 0. Not helpful. Tidy-up pgshift_level_to_ttl() to handle these negative levels, and ttl_to_size() to always return SZ_1G when no valid TTL is present. This allows the removal of open-coded checks for similar situations. Note that the check for a negative value not explicitely checking for S1_MMU_DISABLED is deliberate, so that actual negative levels introduced with LVA2 and D128 can take the same path if we ever support them.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-80296

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle negative S1 walk levels in VNCR TLB size evaluation Computing the effects of a TLB invalidation involves looking at the size of the mapping cached by the TLB. For S1 mappings such as VNCR, this is deducted from the combination of the base granule size and the mapping level. However, this implies that the S1 MMU is *on*. When the MMU is off, we indicate this with the level being set to a "creative" value of -127 (S1_MMU_DISABLED). This ends-up being misinterpreted by pgshift_level_to_ttl() as it doesn't handle negative levels at all (the level is immediately cast to a u8 and only the bottom two bits considered), leading to an invalidation size of 0. Not helpful. Tidy-up pgshift_level_to_ttl() to handle these negative levels, and ttl_to_size() to always return SZ_1G when no valid TTL is present. This allows the removal of open-coded checks for similar situations. Note that the check for a negative value not explicitely checking for S1_MMU_DISABLED is deliberate, so that actual negative levels introduced with LVA2 and D128 can take the same path if we ever support them.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
9.3 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle negative S1 walk levels in VNCR TLB size evaluation Computing the effects of a TLB invalidation involves looking at the size of the mapping cached by the TLB. For S1 mappings such as VNCR, this is deducted from the combination of the base granule size and the mapping level. However, this implies that the S1 MMU is *on*. When the MMU is off, we indicate this with the level being set to a "creative" value of -127 (S1_MMU_DISABLED). This ends-up being misinterpreted by pgshift_level_to_ttl() as it doesn't handle negative levels at all (the level is immediately cast to a u8 and only the bottom two bits considered), leading to an invalidation size of 0. Not helpful. Tidy-up pgshift_level_to_ttl() to handle these negative levels, and ttl_to_size() to always return SZ_1G when no valid TTL is present. This allows the removal of open-coded checks for similar situations. Note that the check for a negative value not explicitely checking for S1_MMU_DISABLED is deliberate, so that actual negative levels introduced with LVA2 and D128 can take the same path if we ever support them.

What

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle negative S1 walk levels in VNCR TLB size evaluation Computing the effects of a TLB invalidation involves looking at the size of the mapping cached by the TLB. For S1 mappings such as VNCR, this is deducted from the combination of the base granule size and the mapping level. However, this implies that the S1 MMU is *on*. When the MMU is off, we indicate this with the level being set to a "creative" value of -127 (S1_MMU_DISABLED). This ends-up being misinterpreted by pgshift_level_to_ttl() as it doesn't handle negative levels at all (the level is immediately cast to a u8 and only the bottom two bits considered), leading to an invalidation size of 0. Not helpful. Tidy-up pgshift_level_to_ttl() to handle these negative levels, and ttl_to_size() to always return SZ_1G when no valid TTL is present. This allows the removal of open-coded checks for similar situations. Note that the check for a negative value not explicitely checking for S1_MMU_DISABLED is deliberate, so that actual negative levels introduced with LVA2 and D128 can take the same path if we ever support them.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle negative S1 walk levels in VNCR TLB size evaluation Computing the effects of a TLB invalidation involves looking at the size of the mapping cached by the TLB. For S1 mappings such as VNCR, this is deducted from the combination of the base granule size and the mapping level. However, this implies that the S1 MMU is *on*. When the MMU is off, we indicate this with the level being set to a "creative" value of -127 (S1_MMU_DISABLED). This ends-up being misinterpreted by pgshift_level_to_ttl() as it doesn't handle negative levels at all (the level is immediately cast to a u8 and only the bottom two bits considered), leading to an invalidation size of 0. Not helpful. Tidy-up pgshift_level_to_ttl() to handle these negative levels, and ttl_to_size() to always return SZ_1G when no valid TTL is present. This allows the removal of open-coded checks for similar situations. Note that the check for a negative value not explicitely checking for S1_MMU_DISABLED is deliberate, so that actual negative levels introduced with LVA2 and D128 can take the same path if we ever support them.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Unauthenticated
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-80296Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle negative S1 walk levels in VNCR TLB size evaluation Computing the effects of a TLB invalidation involves looking at the size of the mapping cached by the TLB. For S1 mappings such as VNCR, this is deducted from the combination of the base granule size and the mapping level. However, this implies that the S1 MMU is *on*. When the MMU is off, we indicate this with the level being set to a "creative" value of -127 (S1_MMU_DISABLED). This ends-up being misinterpreted by pgshift_level_to_ttl() as it doesn't handle negative levels at all (the level is immediately cast to a u8 and only the bottom two bits considered), leading to an invalidation size of 0. Not helpful. Tidy-up pgshift_level_to_ttl() to handle these negative levels, and ttl_to_size() to always return SZ_1G when no valid TTL is present. This allows the removal of open-coded checks for similar situations. Note that the check for a negative value not explicitely checking for S1_MMU_DISABLED is deliberate, so that actual negative levels introduced with LVA2 and D128 can take the same path if we ever support them.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3412Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Speicher zu beschädigen oder offenzulegen, den Kernel oder den Systemzustand zu manipulieren oder Denial-of-Service-Zustände, einschließlich Kernel-Abstürzen, zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260923Security Bulletin 23 Sep 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 23 Sep 2026, published on 23 September 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1254Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2026-74469 Référence CVE CVE-2026-74480 https://www.cve.org/CVERecord?id=CVE-2026-74480 Référence CVE CVE-2026-74581 https://www.cve.org/CVERecord?id=CVE-2026-74581 Référence CVE CVE-2026-74746 https://www.cve.org/CVERecord?id=CVE-2026-74746 Référence CVE CVE-2026-74753 https://www.cve.org/CVERecord?id=CVE-2026-74753 Référence CVE CVE-2026-80522 https://www.cve.org/CVERecord?id=CVE-2026-80522 Référence CVE CVE-2026-80775 https://www.cve.org/CVERecord?id=CVE-2026-80775 Référence CVE CVE-2026-81000 https://www.cve.org/CVERecord?id=CVE-2026-81000 Référence CVE CVE-2026-89480 https://www.cve.org/CVERecord?id=CVE-2026-89480 Référence CVE CVE-2026-89775 https://www.cve.org/CVERecord?id=CVE-2026-89775 Gestion détaillée du document le 02 octobre 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
NBSZ-NKI · Hungarian · cve-2026-89775CVE-2026-89775

A szoftver olyan számítást hajt végre, amely egész szám túlcsordulást vagy áthidalást eredményez, amikor a logika feltételezi, hogy a kapott érték mindig az eredeti értéknél nagyobb lesz. Amikor a számítást erőforrás-gazdálkodásra vagy végrehajtás ellenőrzésre használják más hibákat is okozhat.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Linux: patch: 6.18.51, 7270cc9157f474dfc46750a34c9d7defc686b2eb < be54a70067c7dbe1381157e8a238fa4b16ea9c05, patch: 7.3-rc1, patch: 7.2.5, patch: 0, 6.16, 7270cc9157f474dfc46750a34c9d7defc686b2eb < 1c9fca34b9625a67a7f1a03c8604f3df760c6c49, 7270cc9157f474dfc46750a34c9d7defc686b2eb < 8053393680d4fa3eb962667d2be95dd39f0940e5
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 16 Sept 2026 · Last source change 16 Sept 2026, 17:07 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-16
European sourceENISA EUVD · EUVD-2026-80296
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD received

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel-rt as a component of Red Hat Enterprise Linux 10 · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-matched-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-aarch64-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-x86_64-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 279 more
    After
    Fixed: kernel-64k-debug-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-matched-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-aarch64-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-x86_64-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 279 more
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-89775 to remediation: access.redhat.com/CVE-2026-89775.
    Before
    remediation: access.redhat.com/CVE-2026-89775
    After
    remediation: access.redhat.com/CVE-2026-89775
    Red Hat Product Security ↗
  3. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel as a component of Red Hat Enterprise Linux 10; kernel-64k as a component of Red Hat Enterprise Linux 10; kernel-64k-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-64k-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 46 more
    After
    kernel-rt as a component of Red Hat Enterprise Linux 10 · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-matched-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-aarch64-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-x86_64-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.61.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.61.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.61.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.61.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 279 more
    Red Hat Product Security ↗
  5. BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.
    Before
    no BlackTree article
    After
    1 BlackTree article
    BlackTree editorial ↗
  6. ENISA EUVD mappingEUVD-2026-80296 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-80296"}
    ENISA EUVD ↗
  7. SeveritySeverity changed from Unknown to Critical.
    Before
    Unknown
    After
    Critical
    CNA ↗
  8. CVSS scoreCVSS score changed from not recorded to 9.3 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).
    Before
    not recorded
    After
    9.3 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H)
    CNA ↗
  9. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-80296↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-89775 · cve.blacktree.nl