← Back
CVE-2026-23293
medium
CVSS 5.5
Vulnerability in Kernel (CVE-2026-23293)
Summary
vulnerability in Kernel (CVE-2026-23293). Risk of unauthorized operations or information disclosure. 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-23293** has been found in Kernel.
Risk of unauthorized operations or information disclosure. CVSS score: 5.5/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-23293" on the vendor's site.
CVE-2026-23293 (Kernel) — CWE-476 / CVSS v3 5.5
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** (CWE-476) exists in Kernel.
📍 Affected scope
Kernel — .
🔥 Severity
Severity: Medium (CVSS 5.5/10). Risk of unauthorized operations or information disclosure
🔧 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":"3.12.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.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-23293.json
- package https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- web https://git.kernel.org/stable/c/168ff39e4758897d2eee4756977d036d52884c7e
- web https://git.kernel.org/stable/c/5f93e6b4d12bd3a4517a6d447ea675f448f21434
- web https://git.kernel.org/stable/c/abcd48ecdeb2e12eccb8339a35534c757782afcd
- web https://git.kernel.org/stable/c/b5190fcd75a1f1785c766a8d1e44d3938e168f45
- web https://git.kernel.org/stable/c/f0373e9317bc904e7bdb123d3106fe4f3cea2fb7
- web https://git.kernel.org/stable/c/fbbd2118982c55fb9b0a753ae0cf7194e77149fb
- web https://nvd.nist.gov/vuln/detail/CVE-2026-23293
- web https://git.kernel.org/stable/c/649e2bb74da54c96cf20729001e283626a2fefa0
- web https://git.kernel.org/stable/c/dc3e62cf3bbf66280a907ec379f373d0c3b8b2bc
- web https://github.com/advisories/GHSA-4mrh-9qq5-26w5