Vulnerability · Published Mar 18, 2026 · Assigned by Linux
CVE-2026-23269apparmor: validate DFA start states are in bounds in unpack_pdb
High 7.1
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 3% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.164-1 | DEBIAN-CVE-2026-23269 |
| Debian:13 | linux | 6.12.74-2 | DEBIAN-CVE-2026-23269 |
| Debian:14 | linux | 6.19.6-2 | DEBIAN-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux | 5.15.0-173.183 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux | 6.8.0-106.106 | UBUNTU-CVE-2026-23269 |
| Ubuntu:25.10 | linux | 6.17.0-19.19 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1103.110 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1050.53 | UBUNTU-CVE-2026-23269 |
| Ubuntu:25.10 | linux-aws | 6.17.0-1009.9 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1009.9~24.04.2 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1050.53~22.04.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1109.118 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1051.57 | UBUNTU-CVE-2026-23269 |
| Ubuntu:25.10 | linux-azure | 6.17.0-1010.10 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1010.10~24.04.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1051.57~22.04.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1109.118.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1058.65 | UBUNTU-CVE-2026-23269 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1058.65~22.04.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1103.112 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1052.55 | UBUNTU-CVE-2026-23269 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1009.9 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1009.9~24.04.3 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1052.55~22.04.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1099.105 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1048.53 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1086.94 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1035.38 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-19.19~24.04.2 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-106.106~22.04.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1097.100 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1049.49 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1049.49~22.04.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1098.104 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1095.100 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-173.183 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-106.106.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-106.106.1~22.04.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1098.99 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1049.52 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1014.14 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1049.52~22.04.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1049.52.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1055.55 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1020.20 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1044.44 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1017.17 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1100.106 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1047.48 | UBUNTU-CVE-2026-23269 |
| Ubuntu:25.10 | linux-oracle | 6.17.0-1009.9 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1009.9~24.04.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1047.48~22.04.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1097.100 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1050.54 | UBUNTU-CVE-2026-23269 |
| Ubuntu:25.10 | linux-raspi | 6.17.0-1010.10 | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:25.10 | linux-realtime | 6.17.0-1008.9 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:25.10 | linux-riscv | 6.17.0-19.19.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | 6.17.0-19.19.1~24.04.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-106.106~22.04.1 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-23269 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1028.29 | UBUNTU-CVE-2026-23269 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1067.71 | UBUNTU-CVE-2026-23269 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | ad5ff3db53c68c2f12936bc74ea5dfe0af943592 – before f43eea8ae0102ea198da211ef7f5ce83725ecf19ad5ff3db53c68c2f12936bc74ea5dfe0af943592 – before 5487871b2b56c19d26936ed6fdc62652b30941dfad5ff3db53c68c2f12936bc74ea5dfe0af943592 – before 5443c027ec16afa55b1b8a3e7a1ab2ea3c77767aad5ff3db53c68c2f12936bc74ea5dfe0af943592 – before 07cf6320f40ea2ccfad63728cff34ecb309d03daad5ff3db53c68c2f12936bc74ea5dfe0af943592 – before 15c3eb8916e7db01cb246d04a1fe6f0fdc065b0cad5ff3db53c68c2f12936bc74ea5dfe0af943592 – before 0baadb0eece2c4d939db10d3c323b4652ac79a58ad5ff3db53c68c2f12936bc74ea5dfe0af943592 – before 3bb7db43e32190c973d4019037cedb7895920184ad5ff3db53c68c2f12936bc74ea5dfe0af943592 – before 9063d7e2615f4a7ab321de6b520e23d370e58816 |
| Linux | Linux | 3.4 |
References
- https://git.kernel.org/stable/c/f43eea8ae0102ea198da211ef7f5ce83725ecf19
- https://git.kernel.org/stable/c/5487871b2b56c19d26936ed6fdc62652b30941df
- https://git.kernel.org/stable/c/5443c027ec16afa55b1b8a3e7a1ab2ea3c77767a
- https://git.kernel.org/stable/c/07cf6320f40ea2ccfad63728cff34ecb309d03da
- https://git.kernel.org/stable/c/15c3eb8916e7db01cb246d04a1fe6f0fdc065b0c
- https://git.kernel.org/stable/c/0baadb0eece2c4d939db10d3c323b4652ac79a58
- https://git.kernel.org/stable/c/3bb7db43e32190c973d4019037cedb7895920184
- https://git.kernel.org/stable/c/9063d7e2615f4a7ab321de6b520e23d370e58816
- https://www.qualys.com/2026/03/10/crack-armor.txt