← Back
CVE-2026-23253
high
CVSS 7.8
Vulnerability in Kernel (CVE-2026-23253)
Summary
vulnerability in Kernel (CVE-2026-23253). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `6.1.167, 6.6.130, 6.12.77, 6.18.17, 6.19.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-23253** 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.167, 6.6.130, 6.12.77, 6.18.17, 6.19.7** or later.
If unsure, ask your IT team or search "Kernel CVE-2026-23253" on the vendor's site.
CVE-2026-23253 (Kernel) — CVSS v3 7.8
Attack vector: local / no user interaction
Patched: `6.1.167, 6.6.130, 6.12.77, 6.18.17, 6.19.7` — 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.167, 6.6.130, 6.12.77, 6.18.17, 6.19.7**.
🛡️ 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.167, 6.6.130, 6.12.77, 6.18.17, 6.19.7ステージング環境で 6.1.167, 6.6.130, 6.12.77, 6.18.17, 6.19.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Linux
Kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.17"},{"fixed":"6.1.167"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.130"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.77"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.17"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"6.19.7"}]}]
References
- advisory https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23253.json
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-23253
- package https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- patch 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- patch 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- web https://git.kernel.org/stable/c/32eb8e4adc207ef31bc6e5ae56bab940b0176066
- web https://git.kernel.org/stable/c/af050ab44fa1b1897a940d7d756e512232f5e5df
- web https://git.kernel.org/stable/c/bfbc0b5b32a8f28ce284add619bf226716a59bc0
- web https://git.kernel.org/stable/c/cfd94642025e6f71c8f754bdec0800ee95e4f3dd
- web https://git.kernel.org/stable/c/d71781bad59b1c9d60d7068004581f9bf19c0c9d
- web https://git.kernel.org/stable/c/f1e520ca2e83ece6731af6167c9e5e16931ecba0