← Back
CVE-2026-23264
medium
CVSS 5.5
Vulnerability in Kernel (CVE-2026-23264)
Summary
vulnerability in Kernel (CVE-2026-23264). Risk of unauthorized operations or information disclosure. Exploitable via ``amdgpu_aspm``. Mitigation: upgrade to `6.1.163, 6.6.124, 6.12.70, 6.18.10` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-23264** has been found in Kernel.
Attackers can target a specific entry point like ``amdgpu_aspm`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.5/10.
What to do: upgrade Kernel to **6.1.163, 6.6.124, 6.12.70, 6.18.10** or later.
If unsure, ask your IT team or search "Kernel CVE-2026-23264" on the vendor's site.
CVE-2026-23264 (Kernel) — CVSS v3 5.5
Attack vector: local / no user interaction
Attack surface: `amdgpu_aspm`
Patched: `6.1.163, 6.6.124, 6.12.70, 6.18.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. Attackers reach the vulnerable code path via ``amdgpu_aspm`` without authentication.
📍 Affected scope
Kernel — . Attack surface: `amdgpu_aspm`.
🔥 Severity
Severity: Medium (CVSS 5.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.1.163, 6.6.124, 6.12.70, 6.18.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.163, 6.6.124, 6.12.70, 6.18.10ステージング環境で 6.1.163, 6.6.124, 6.12.70, 6.18.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":"5.18.0"},{"fixed":"6.1.163"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.124"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.70"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.10"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-23264
- advisory https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23264.json
- package https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- web https://git.kernel.org/stable/c/243b467dea1735fed904c2e54d248a46fa417a2d
- web https://git.kernel.org/stable/c/5b794951541e84d2968980a68dd1ac38420f75f3
- web https://git.kernel.org/stable/c/5f645222eb30c91135119e12eccfd1b8ea88140e
- web https://git.kernel.org/stable/c/d2bddc2da2b3ba5d738877c476bf97932dba32e8
- web https://git.kernel.org/stable/c/f02c9052aaa031ef3c2285d86a155d4263180ddd
- web https://github.com/advisories/GHSA-pqp4-5r3j-578m