← Back
CVE-2026-23397
high
CVSS 7.1
Out-of-Bounds Read in Kernel (CVE-2026-23397)
Summary
vulnerability in Kernel (CVE-2026-23397). Confidential information can be exposed externally. 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-23397** has been found in Kernel.
Confidential information can be exposed externally. CVSS score: 7.1/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-23397" on the vendor's site.
CVE-2026-23397 (Kernel) — CWE-125 / CVSS v3 7.1
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
**out-of-bounds read** (CWE-125) exists in Kernel.
📍 Affected scope
Kernel — .
🔥 Severity
Severity: High (CVSS 7.1/10). Confidential information can be exposed externally
🔧 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":"2.6.31"},{"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-23397.json
- package https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- web https://git.kernel.org/stable/c/224f4678812e1a7bc8341bcb666773a0aec5ea6f
- web https://git.kernel.org/stable/c/3932620c04c2938c93c0890c225960d3d34ba355
- web https://git.kernel.org/stable/c/4c6aa008b913e808c4f4d3cde36cb1d9bb5967c6
- web https://git.kernel.org/stable/c/aa0574182c46963c3cdb8cde46ec93aca21100d8
- web https://git.kernel.org/stable/c/dbdfaae9609629a9569362e3b8f33d0a20fd783c
- web https://git.kernel.org/stable/c/ec8bf0571b142f29dc0b68ae2ac3952f7a464b38
- web https://nvd.nist.gov/vuln/detail/CVE-2026-23397
- web https://git.kernel.org/stable/c/3c11b5c2436a3a5b450612ab160e3a525b28cfb5
- web https://git.kernel.org/stable/c/e9cf17b91e733fec725ebcc0b3098bc5ccd505e0
- 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-3rcm-5vqm-53w6