Out-of-Bounds Read in Kernel (CVE-2026-23269)
Summary
Vulnerability in Kernel (CVE-2026-23269). Confidential information can be exposed externally. Mitigation: upgrade to 6.6.130, 6.12.77, 6.18.18, 6.19.8 or later.
Original description
The description as published by the source.
In the Linux kernel, the following vulnerability has been resolved:
apparmor: validate DFA start states are in bounds in unpack_pdb
Start states are read from untrusted data and used as indexes into the
DFA state tables. The aa_dfa_next() function call in unpack_pdb() will
access dfa->tables[YYTD_ID_BASE][start], and if the start state exceeds
the number of states in the DFA, this results in an out-of-bound read.
==================================================================
BUG: KASAN: slab-out-of-bounds in aa_dfa_next+0x2a1/0x360
Read of size 4 at addr ffff88811956fb90 by task su/1097
...
Reject policies with out-of-bounds start states during unpacking
to prevent the issue.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-23269 has been found in Kernel.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: upgrade Kernel to 6.6.130, 6.12.77, 6.18.18, 6.19.8 or later.
If unsure, ask your IT team or search "Kernel CVE-2026-23269" on the vendor's site.
CVE-2026-23269 (Kernel) — CWE-125 / CVSS v3 7.1
Attack vector: local / no user interaction
Patched: 6.6.130, 6.12.77, 6.18.18, 6.19.8 — 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.
Out-of-bounds read (CWE-125) exists in Kernel.
Check the vendor advisory for the affected versions of Kernel.
Severity: High (CVSS 7.1/10). Confidential information can be exposed externally.
Update to 6.6.130, 6.12.77, 6.18.18, 6.19.8.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
grep -r 'Kernel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Kernelを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Kernel to 6.6.130, 6.12.77, 6.18.18, 6.19.8ステージング環境で 6.6.130, 6.12.77, 6.18.18, 6.19.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- BellSoft Alpaquita BELL-CVE-2026-23269 linux-lts Fixed in: 6.1.170-r0
- Debian DEBIAN-CVE-2026-23269 linux Fixed in: 5.10.251-1
- Ubuntu UBUNTU-CVE-2026-23269 linux
References
- advisory github.com
- advisory nvd.nist.gov
- package git.kernel.org
- web git.kernel.org
- web git.kernel.org
- web git.kernel.org
- web git.kernel.org
- web git.kernel.org
- web qualys.com
- web git.kernel.org
- web git.kernel.org
- web git.kernel.org
- web github.com