Categories
CVE-2026-102699

[This CNA information record relates to multiple CVEs; the text explains which aspects...

Summary

Vulnerability reported (CVE-2026-102699). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

[This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE.]

  1. XSA-437 (CVE-2023-34321) addressed issues with overflows in
    calculations involved in guests flushing caches through
    GNTTABOP_cache_flush. Unfortunately the fix there introduced a
    calculation which may underflow, resulting in a loop which would - at
    least on 64-bit Arm - take excessively long, and which would likely
    eventually crash the hypervisor.

    This is CVE-2026-102699.

  2. GNTTABOP_cache_flush may be issued on memory mapped from another
    domain using the grant table interface. However there was no
    restriction to disallow the use of invalidate-without-clean against
    read-only grant mappings, which may corrupt the granted memory.

    This is CVE-2026-102702.

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-102699 has been found.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-102699" on the vendor's site.

CVE-2026-102699
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 (unclassified) has been reported.

📍 Affected scope

Check the vendor advisory for the affected versions.

🔥 Severity

Severity: ?. 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・依存マニフェストで影響コンポーネントを特定する。

  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