Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-46147 medium CVSS 5.5

Vulnerability in Linux kernel (CVE-2026-46147)

Summary

Vulnerability in Linux kernel (CVE-2026-46147). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

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

KVM: arm64: Fix pin leak and publication ordering in __pkvm_init_vcpu()

Two bugs exist in the vCPU initialisation path:

  1. If a check fails after hyp_pin_shared_mem() succeeds, the cleanup
    path jumps to 'unlock' without calling unpin_host_vcpu() or
    unpin_host_sve_state(), permanently leaking pin references on the
    host vCPU and SVE state pages.

    Extract a register_hyp_vcpu() helper that performs the checks and
    the store. When register_hyp_vcpu() returns an error, call
    unpin_host_vcpu() and unpin_host_sve_state() inline before falling
    through to the existing 'unlock' label.

  2. register_hyp_vcpu() publishes the new vCPU pointer into
    'hyp_vm->vcpus[]' with a bare store, allowing a concurrent caller
    of pkvm_load_hyp_vcpu() to observe a partially initialised vCPU
    object.

    Ensure the store uses smp_store_release() and the load uses
    smp_load_acquire(). While 'vm_table_lock' currently serialises the
    store and the load, these barriers ensure the reader sees the fully
    initialised 'hyp_vcpu' object even if there were a lockless path or
    if the lock's own ordering guarantees were insufficient for nested
    object initialization.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-46147 has been found in Linux kernel.
Risk of unauthorized operations or information disclosure. CVSS score: 5.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2026-46147" on the vendor's site.

CVE-2026-46147 (Linux kernel) — CWE-401 / CVSS v3 5.5
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-401) exists in Linux kernel.

📍 Affected scope

Check the vendor advisory for the affected versions of Linux kernel.

🔥 Severity

Severity: Medium (CVSS 5.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Linux kernel を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details