← Back
CVE-2026-23391
high
CVSS 7.8
Vulnerability in Kernel (CVE-2026-23391)
Summary
vulnerability in Kernel (CVE-2026-23391). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `6.1.167, 6.6.130, 6.12.78, 6.18.20, 6.19.10` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-23391** 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.78, 6.18.20, 6.19.10** or later.
If unsure, ask your IT team or search "Kernel CVE-2026-23391" on the vendor's site.
CVE-2026-23391 (Kernel) — CVSS v3 7.8
Attack vector: local / no user interaction
Patched: `6.1.167, 6.6.130, 6.12.78, 6.18.20, 6.19.10` — 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.78, 6.18.20, 6.19.10**.
🛡️ 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.78, 6.18.20, 6.19.10ステージング環境で 6.1.167, 6.6.130, 6.12.78, 6.18.20, 6.19.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Linux
Kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"3.4.0"},{"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.78"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.20"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"6.19.10"}]}]
References
- advisory https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23391.json
- package https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- web https://git.kernel.org/stable/c/19a230dec6bb8928e3f96387f9085cf2c79bcef9
- web https://git.kernel.org/stable/c/63b8097cea1923fe82cd598068d0796da8c015ec
- web https://git.kernel.org/stable/c/777d02efe3d630cca4c1b63962cec17c57711325
- web https://git.kernel.org/stable/c/cb549925875fa06dd155e49db4ac2c5044c30f9c
- web https://git.kernel.org/stable/c/d2d0bae0c9a2a17b6990a2966f5cdce0813d6256
- web https://git.kernel.org/stable/c/f62a218a946b19bb59abdd5361da85fa4606b96b
- web https://nvd.nist.gov/vuln/detail/CVE-2026-23391
- web https://git.kernel.org/stable/c/55445134d42b84cb0a272e42c98d233ca65eca83
- web https://git.kernel.org/stable/c/cc57506dd66555899560b9c0f24e813f034e12ec
- web https://cert-portal.siemens.com/productcert/html/ssa-019113.html
- web https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- web https://github.com/advisories/GHSA-qqcv-h6xq-mw7q