← Back
CVE-2025-22060
medium
CVSS 4.7
Vulnerability in linux (CVE-2025-22060)
Summary
vulnerability in linux (CVE-2025-22060). Risk of unauthorized operations or information disclosure. Exploitable via ``rx_classifier_drops``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-22060** has been found in linux.
Attackers can target a specific entry point like ``rx_classifier_drops`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "linux CVE-2025-22060" on the vendor's site.
CVE-2025-22060 (linux) — CWE-367 / CVSS v3 4.7
Attack vector: local / no user interaction
Attack surface: `rx_classifier_drops`
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-367) exists in linux. Attackers reach the vulnerable code path via ``rx_classifier_drops`` without authentication.
📍 Affected scope
linux — . Attack surface: `rx_classifier_drops`.
🔥 Severity
Severity: Medium (CVSS 4.7/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'linux' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `linux` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- web https://git.kernel.org/stable/c/46c1e23e34c9d1eaadf37f88216d9d8ce0d0bcee
- web https://git.kernel.org/stable/c/5b0ae1723a7d9574ae1aee7d9cf9757a30069865
- web https://git.kernel.org/stable/c/96844075226b49af25a69a1d084b648ec2d9b08d
- web https://git.kernel.org/stable/c/b3f48a41a00d6d8d9c6fe09ae47dd21c8c1c8b03
- web https://git.kernel.org/stable/c/e3711163d14d02af9005e4cdad30899c565f13fb
- web https://git.kernel.org/stable/c/e64e9b6e86b39db3baa576fd73da73533b54cb2d
- web https://git.kernel.org/stable/c/fcbfb54a0269875cf3cd6a2bff4f85a2e0a0b552
- web https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html
- web https://cert-portal.siemens.com/productcert/html/ssa-019113.html
- web https://nvd.nist.gov/vuln/detail/CVE-2025-22060
- web https://github.com/advisories/GHSA-f5rg-cp58-cwjr