Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved:

Revert "drm/amd: Check if ASPM is enabled from PCIe subsystem"

This reverts commit 7294863a6f01248d72b61d38478978d638641bee.

This commit was erroneously applied again after commit 0ab5d711ec74
("drm/amd: Refactor amdgpu_aspm to be evaluated per device")
removed it, leading to very hard to debug crashes, when used with a system with two
AMD GPUs of which only one supports ASPM.

(cherry picked from commit 97a9689300eb2b393ba5efc17c8e5db835917080)

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

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.

📍 Affected scope

Check the vendor advisory for the affected versions of 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'Kernel' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Kernel を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply 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 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

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"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details