Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-24834 critical CVSS 9.3

Vulnerability in github.com/kata-containers/kata-containers/src/runtime (CVE-2026-24834)

Summary

Vulnerability in github.com/kata-containers/kata-containers/src/runtime (CVE-2026-24834). Successful exploitation can lead to full system takeover. Exploitable via ND_REGION_PAGEMAP. Mitigation: upgrade to 0.0.0-20260219090056-6a672503973b or later.

Original description

The description as published by the source.

Summary

An issue in Kata with Cloud Hypervisor allows a user of the container to modify the file system used by the Guest micro VM ultimately achieving arbitrary code execution as root in said VM. The current understinding is this doesn’t impact the security of the Host or of other containers / VMs running on that Host (note that arm64 QEMU lacks NVDIMM read-only support: It is believed that until the upstream QEMU gains this capability, a guest write could reach the image file).

Details

Linux virtio-pmem
The virtio-pmem probe path always registers the region as a generic pagemap that supports asynchronous flushes, but it never marks the region as read-only. Only the ND_REGION_PAGEMAP and ND_REGION_ASYNC bits are set before the region is created, so nd_region->ro always stays cleared and the block device is left writable.

Later, pmem_attach_disk() wires the region into the block layer with full read/write semantics – the block device operations call pmem_do_write() which performs cache-flushed memcpy operations directly into the host-provided shared memory window. nvdimm_check_and_set_ro() would set the disk read-only if the region had been flagged as such, but because virtio_pmem never sets that flag, the helper becomes a no-op.

Cloud-Hypervisor virtio_pmem
discard_writes=on causes the file backing the virtio-pmem device to be opened read-only and mapped with MAP_PRIVATE rather than MAP_SHARED. That combination means the guest can mo…

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-24834 has been found in github.com/kata-containers/kata-containers/src/runtime.
Attackers can target a specific entry point like ND_REGION_PAGEMAP over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.3/10.
What to do: upgrade github.com/kata-containers/kata-containers/src/runtime to 0.0.0-20260219090056-6a672503973b or later.
If unsure, ask your IT team or search "github.com/kata-containers/kata-containers/src/runtime CVE-2026-24834" on the vendor's site.

CVE-2026-24834 (github.com/kata-containers/kata-containers/src/runtime) — CWE-281 / CVSS v3 9.3
Attack vector: local / unauthenticated / no user interaction
Attack surface: ND_REGION_PAGEMAP / ND_REGION_ASYNC / virtio_pmem / MAP_PRIVATE
Patched: 0.0.0-20260219090056-6a672503973b — apply immediately
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-281) exists in github.com/kata-containers/kata-containers/src/runtime. Attackers reach the vulnerable code path via ND_REGION_PAGEMAP without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/kata-containers/kata-containers/src/runtime. Attack surface: ND_REGION_PAGEMAP / ND_REGION_ASYNC / virtio_pmem / MAP_PRIVATE.

🔥 Severity

Severity: Critical (CVSS 9.3/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 0.0.0-20260219090056-6a672503973b.

🛡️ 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. Run grep -r 'github.com/kata-containers/kata-containers/src/runtime' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    grep -r 'github.com/kata-containers/kata-containers/src/runtime' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/kata-containers/kata-containers/src/runtime を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/kata-containers/kata-containers/src/runtime to 0.0.0-20260219090056-6a672503973b

    ステージング環境で 0.0.0-20260219090056-6a672503973b に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

go github.com/kata-containers/kata-containers/src/runtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.0-20260219090056-6a672503973b"}]}]

References

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