This page tracks the Debian fix status. The vulnerability itself is described on the main CVE page. View CVE-2026-74312 →
Categories
DEBIAN-CVE-2026-74312

Vulnerability in linux (DEBIAN-CVE-2026-74312)

Summary

Vulnerability in linux (DEBIAN-CVE-2026-74312). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 6.1.180-1 or later.

Original description

The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved: vhost/vdpa: validate virtqueue index in mmap and fault paths vhost_vdpa_mmap() and vhost_vdpa_fault() use vma->vm_pgoff as a virtqueue index for get_vq_notification(), but they do not validate that the index is smaller than v->nvqs. The ioctl path already performs both a bounds check and array_index_nospec(), but the mmap/fault path only checks that the index fits in u16. This allows an out-of-range queue index to reach driver-specific get_vq_notification() callbacks. Fix this by extracting a unified vhost_vdpa_get_vq_notification() helper that validates the queue index against v->nvqs and applies array_index_nospec() before calling the driver callback. Both the mmap and fault paths use this helper, and the bounds checking is consolidated into a single location. From source inspection, the most defensible impact is out-of-bounds access in the callback path, potentially leading to invalid PFN remaps and crash/DoS.

Source: OSV.dev (Open Source Vulnerabilities) OSV

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 DEBIAN-CVE-2026-74312 has been found in linux.
Successful exploitation can lead to full system takeover.
What to do: upgrade linux to 6.1.180-1 or later.
If unsure, ask your IT team or search "linux DEBIAN-CVE-2026-74312" on the vendor's site.

DEBIAN-CVE-2026-74312 (linux)
Attack vector: local / no user interaction
Patched: 6.1.180-1 — 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 (unclassified) exists in linux.

📍 Affected scope

Check the vendor advisory for the affected versions of linux.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 6.1.180-1.

🛡️ 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 'linux' . 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 'linux' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade linux to 6.1.180-1

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

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

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

Affected packages

Debian:12 linux
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.180-1"}]}]
Debian:13 linux
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.100-1"}]}]
Debian:14 linux
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.5-1"}]}]

References

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