CVE-2026-46147

Local service interruption via vCPU initialization flaws

Published May 28, 2026 · Updated May 28, 2026

Resource-management and ordering flaws in Linux Kernel before 6.18.30 and 6.19 through 7.0.6 allow local users to interrupt service. In __pkvm_init_vcpu(), error paths after hyp_pin_shared_mem() omit vCPU and SVE page unpins, while a bare pointer store can expose a partly initialized vCPU. Low-privilege local access and arm64 protected KVM vCPU initialization are required; repeated failures can exhaust pinned memory, and concurrent loads can consume incomplete state.

CVSS severity5.5
Medium
EPSS probability0.13%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Resource-management and ordering flaws in Linux Kernel before 6.18.30 and 6.19 through 7.0.6 allow local users to interrupt service. In __pkvm_init_vcpu(), error paths after hyp_pin_shared_mem() omit vCPU and SVE page unpins, while a bare pointer store can expose a partly initialized vCPU. Low-privilege local access and arm64 protected KVM vCPU initialization are required; repeated failures can exhaust pinned memory, and concurrent loads can consume incomplete state.

The record

CVE
CVE-2026-46147
Published
May 28, 2026
Updated
May 28, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
CWE-401, T1499.001
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 28, 2026CVE publishedPublication date reported by the CVE source.
  2. May 28, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <6.18.30
  2. Affected versionversion=0 <7.0.7
  3. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6d69c0ed978f7f0efd053fc98390f25ab77c1aea
  4. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <73b9c1e5da84cd69b1a86e374e450817cd051371
  5. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7d3c27b54253cda91dc4d2c1bfc109c490837ab9

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=0 <6.18.30; version=0 <7.0.7; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6d69c0ed978f7f0efd053fc98390f25ab77c1aea; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <73b9c1e5da84cd69b1a86e374e450817cd051371; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7d3c27b54253cda91dc4d2c1bfc109c490837ab9

Published CVSS scores

4.7Amazon LinuxCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-401Missing Release of Memory after Effective Lifetime
T1499.001OS Exhaustion Flood

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo