← Back
CVE-2025-68347
high
CVSS 7.8
Vulnerability in Kernel (CVE-2025-68347)
Summary
vulnerability in Kernel (CVE-2025-68347). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `6.1.160, 6.6.120, 6.12.63, 6.17.13, 6.18.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-68347** has been found in Kernel.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade Kernel to **6.1.160, 6.6.120, 6.12.63, 6.17.13, 6.18.2** or later.
If unsure, ask your IT team or search "Kernel CVE-2025-68347" on the vendor's site.
CVE-2025-68347 (Kernel) — CVSS v3 7.8
Attack vector: local / no user interaction
Patched: `6.1.160, 6.6.120, 6.12.63, 6.17.13, 6.18.2` — 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 Kernel.
📍 Affected scope
Kernel — .
🔥 Severity
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **6.1.160, 6.6.120, 6.12.63, 6.17.13, 6.18.2**.
🛡️ 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 6.1.160, 6.6.120, 6.12.63, 6.17.13, 6.18.2ステージング環境で 6.1.160, 6.6.120, 6.12.63, 6.17.13, 6.18.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Linux
Kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.160"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.120"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.63"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.17.13"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.18.0"},{"fixed":"6.18.2"}]}]
References
- advisory https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68347.json
- package https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- web https://git.kernel.org/stable/c/161291bac551821bba98eb4ea84c82338578d1b0
- web https://git.kernel.org/stable/c/16620f0617400746984362c3d6ac547eeae1d35f
- web https://git.kernel.org/stable/c/210d77cca3d0494ed30a5c628b20c1d95fa04fb1
- web https://git.kernel.org/stable/c/6275fd726d53a8ec724f20201cf3bd862711e17b
- web https://git.kernel.org/stable/c/cdda0d06f8650e33255f79839f188bbece44117c
- web https://git.kernel.org/stable/c/ddd32ec66bc4eb6969fe835e4cc1c0706c6348fe
- web https://nvd.nist.gov/vuln/detail/CVE-2025-68347
- web https://github.com/advisories/GHSA-h6xr-332m-px9v