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

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

Summary

Vulnerability in linux (DEBIAN-CVE-2026-64547). Confidential information can be exposed externally. 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: net: usb: net1080: validate packet_len before pad-byte access in rx_fixup For an even packet_len, net1080_rx_fixup() reads the pad byte at skb->data[packet_len] before the skb->len != packet_len check further down, and packet_len is only bounded against NC_MAX_PACKET. A malicious NetChip 1080 device can send a short frame advertising a large even packet_len (e.g. 0x4000), so the pad-byte read lands past the end of the skb: BUG: KASAN: slab-out-of-bounds in net1080_rx_fixup Read of size 1 at addr ffff8880106c83c6 by task ksoftirqd/0/14 ... net1080_rx_fixup (drivers/net/usb/net1080.c:384) usbnet_bh (drivers/net/usb/usbnet.c:1589) process_one_work (kernel/workqueue.c:3322) bh_worker (kernel/workqueue.c:3708) tasklet_action (kernel/softirq.c:965) handle_softirqs (kernel/softirq.c:622) ... Reject the frame when packet_len >= skb->len before reading.

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-64547 has been found in linux.
Confidential information can be exposed externally.
What to do: upgrade linux to 6.1.180-1 or later.
If unsure, ask your IT team or search "linux DEBIAN-CVE-2026-64547" on the vendor's site.

DEBIAN-CVE-2026-64547 (linux)
Attack vector: adjacent-network / unauthenticated / 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: ?. Confidential information can be exposed externally.

🔧 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"}]}]
Debian:12 linux-6.12
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.100-1~deb12u1"}]}]

References

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