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

Summary

Vulnerability in linux (DEBIAN-CVE-2026-80670). Confidential information can be exposed externally. Mitigation: upgrade to 7.1.5-1 or later.

Original description

The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved: perf tools: Use perf_env__get_cpu_topology() in machine__resolve() machine__resolve() accesses env->cpu[al->cpu].socket_id after checking al->cpu >= 0 and env->cpu != NULL, but without validating al->cpu against env->nr_cpus_avail. Since al->cpu comes from the untrusted perf.data sample, a crafted file with a large CPU index causes an out-of-bounds heap read. Use perf_env__get_cpu_topology() which validates both NULL and bounds. Also bounds-check al->cpu before the cast to struct perf_cpu (int16_t): without this, values like 65536 silently truncate to 0, bypassing the accessor's internal check and returning CPU 0's topology.

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

DEBIAN-CVE-2026-80670 (linux)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 7.1.5-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 7.1.5-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
Identify exposure identify
```
grep -r 'linux' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で linux を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade linux to 7.1.5-1
```
ステージング環境で 7.1.5-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:12 linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Debian:13 linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Debian:14 linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.5-1"}]}]

References

advisory security-tracker.debian.org