HighCVE-2026-98927

Linux Kernel: security vulnerability (CVE-2026-98927)

Published 23.10.2026Last modified 24.10.2026Sources: CVE.org, BSI

What is affected, what to do

Update Linux Kernel to version 6.12.113, Linux Kernel to version 6.18.56, Linux Kernel to version 7.2.9.

Affected: Linux Kernel lt 6.11..6.12.113
Linux Kernel lt 6.13..6.18.56
Linux Kernel lt 6.19..7.2.9
Fixed in: Linux Kernel 6.12.113
Linux Kernel 6.18.56
Linux Kernel 7.2.9
Linux Kernel 7.3

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

7.0

Priority

XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

Source: Vendor (CNA), CVSS v3

7.0

CVSS v3

Severity High on the scale from 0 to 10.

Source: CVE.org, BSI

0.2 %

EPSS score

Low — model estimates < 1% exploitation likelihood.

Source: FIRST EPSS, percentile 4.5

Show all metrics

Severity: High
Priority (0–325) The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first? Read in glossary: 65.16 Methodology
Exploit maturity An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack. Read in glossary: no public PoC known
XIEM Effective CVSS XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command. Read in glossary: 7.0 Methodology
CVSS v3 CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions. Read in glossary: 7.0
EPSS score The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“. Read in glossary: 0.2 %; Low — model estimates < 1% exploitation likelihood.
EPSS percentile The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking. Read in glossary: 4.5; Low — this CVE sits in the lower 10% of all CVEs scored today.
KEV status The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching. Read in glossary: —
Published: 23.10.2026

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2 NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management. Read in glossary: High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates. Read in glossary: From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001 ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security. Read in glossary: Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

Description

In the Linux kernel, the following vulnerability has been resolved:

KVM: arm64: nv: Fix life cycle of the nested_mmus array

The nested_mmus array holds the shadow page tables that are used when a guest is running a nested context. These structures are allocated on VCPU_INIT for whole guest, which implies that they may have to be relocated as the array grows.

Should a VCPU_INIT occur whilst a vcpu is actively running an L2 and that the allocation requires relocation, that vcpu will still be running with a pointer to the previous structure, which will have been freed.

Fix this by turning the array of structures to an array of pointers, which is now allocated at VM creation, sized to the absolute maximum that KVM can handle.

In turn, each VCPU_INIT contributes S2_MMU_PER_VCPU to the pool. No reallocation is ever performed, and the life cycle of each object is much clearer:

the nested_mmus array is allocated in kvm_init_nested(), and freed in kvm_arch_destroy_vm()
s2_mmu structures are allocated in kvm_vcpu_init_nested(), and freed on kvm_arch_flush_shadow_all()

Finally, the freeing of vcpu->arch.vncr_array is made consistent rather than being done on some failure paths, but not others.

Source: cvelistv5, NVD (NIST), BSI CSAF, BSI WID Portal

Affected products

The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

Affected products
		Affected versions	Fixed in
Linux	Linux	`6.11 – < 6.12.113` `6.13 – < 6.18.56` `—` `6.19 – < 7.2.9`	`6.12.113` `6.18.56` `7.3` `7.2.9`

Vendors and products

Linux Linux

References & sources

git.kernel.orgstable/c/33346f8960c7bb6a3b4e273b5cfe25c5a8be349f
git.kernel.orgstable/c/512c93f4461b9a3735987f48423d438a9cd49e6a
git.kernel.orgstable/c/81e3f065a6485626f816d791dfd5e00ddd12eff5
git.kernel.orgstable/c/ea242bdc29e8a8ff0e2447a64b3841114779f3af

Changes to this CVE

Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

24.10.2026Record modifiedLinux
CVSS V3.1: AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Show the original change
Individual changes of this event as published by NVD
Type Action Before After
CVSS added
—
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Individual changes of this event as published by NVD
Type	Action	Before	After
CVSS	added	—	AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

23.10.2026ReceivedLinux

Description added or changed

New references:

Show 6 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
Description	added	—	In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Fix life cycle of the nested_mmus array The nested_mmus array holds the shadow page tables that are used when a guest is running a nested context. These structures are allocated on VCPU_INIT for whole guest, which implies that they may have to be relocated as the array grows. Should a VCPU_INIT occur whilst a vcpu is actively running an L2 and that the allocation requires relocation, that vcpu will still be running with a pointer to the previous structure, which will have been freed. Fix this by turning the array of structures to an array of pointers, which is now allocated at VM creation, sized to the absolute maximum that KVM can handle. In turn, each VCPU_INIT contributes S2_MMU_PER_VCPU to the pool. No reallocation is ever performed, and the life cycle of each object is much clearer: - the nested_mmus array is allocated in kvm_init_nested(), and freed in kvm_arch_destroy_vm() - s2_mmu structures are allocated in kvm_vcpu_init_nested(), and freed on kvm_arch_flush_shadow_all() Finally, the freeing of vcpu->arch.vncr_array is made consistent rather than being done on some failure paths, but not others.
Affected versions (publisher)	added	—	New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/98xxx/CVE-2026-98927.json">CVE-2026-98927</a>
Reference	added	—	https://git.kernel.org/stable/c/33346f8960c7bb6a3b4e273b5cfe25c5a8be349f
Reference	added	—	https://git.kernel.org/stable/c/512c93f4461b9a3735987f48423d438a9cd49e6a
Reference	added	—	https://git.kernel.org/stable/c/81e3f065a6485626f816d791dfd5e00ddd12eff5
Reference	added	—	https://git.kernel.org/stable/c/ea242bdc29e8a8ff0e2447a64b3841114779f3af

Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Embed badge

Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

<a href="https://intel.neosec.eu/en/cve/CVE-2026-98927"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-98927.svg?lang=en" alt="CVE-2026-98927 – NEOSEC Intel" height="20"></a>