← Back
CVE-2025-71066
high
CVSS 7.8
Vulnerability in Kernel (CVE-2025-71066)
Summary
vulnerability in Kernel (CVE-2025-71066). Successful exploitation can lead to full system takeover. Exploitable via ``ets_qdisc_dequeue``. Mitigation: upgrade to `5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-71066** has been found in Kernel.
Attackers can target a specific entry point like ``ets_qdisc_dequeue`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade Kernel to **5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3** or later.
If unsure, ask your IT team or search "Kernel CVE-2025-71066" on the vendor's site.
CVE-2025-71066 (Kernel) — CWE-362 / CVSS v3 7.8
Attack vector: local / no user interaction
Attack surface: `ets_qdisc_dequeue` / `ets_qdisc_change`
Patched: `5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3` — 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-362) exists in Kernel. Attackers reach the vulnerable code path via ``ets_qdisc_dequeue`` without authentication.
📍 Affected scope
Kernel — . Attack surface: `ets_qdisc_dequeue` / `ets_qdisc_change`.
🔥 Severity
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3**.
🛡️ 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 'Kernel' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Kernel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `Kernel` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade Kernel to 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3ステージング環境で 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Linux
Kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.248"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.198"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.160"},{"fixed":"6.6.120"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.12.64"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.18.3"}]}]
References
- advisory https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/71xxx/CVE-2025-71066.json
- package https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- web https://git.kernel.org/stable/c/062d5d544e564473450d72e6af83077c2b2ff7c3
- web https://git.kernel.org/stable/c/06bfb66a7c8b45e3fed01351a4b087410ae5ef39
- web https://git.kernel.org/stable/c/45466141da3c98a0c5fa88be0bc14b4b6a4bd75c
- web https://git.kernel.org/stable/c/9987cda315c08f63a02423fa2f9a1f6602c861a0
- web https://git.kernel.org/stable/c/a75d617a4ef08682f5cfaadc01d5141c87e019c9
- web https://git.kernel.org/stable/c/c7f6e7cc14df72b997258216e99d897d2df0dbbd
- web https://git.kernel.org/stable/c/ce052b9402e461a9aded599f5b47e76bc727f7de
- web https://nvd.nist.gov/vuln/detail/CVE-2025-71066
- web https://github.com/advisories/GHSA-m4cc-c4jq-h2wr