Linux Kernel up to 6.12.76/6.18.17/6.19.7/7.0-rc3 apparmor aa_dfa_next out-of-bounds

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Linux Kernel up to 6.12.76/6.18.17/6.19.7/7.0-rc3. The affected element is the function aa_dfa_next of the component apparmor. This manipulation causes out-of-bounds.
This vulnerability is tracked as CVE-2026-23269. No exploit exists.
You should upgrade the affected component.
Details
A vulnerability classified as problematic was found in Linux Kernel up to 6.12.76/6.18.17/6.19.7/7.0-rc3. Affected by this vulnerability is the function aa_dfa_next of the component apparmor. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality. The summary by CVE is:
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.
The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-23269 since 01/13/2026. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 303009 (Linux Distros Unpatched Vulnerability : CVE-2026-23269), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 6.12.77, 6.18.18, 6.19.8 or 7.0-rc4 eliminates this vulnerability. Applying the patch 15c3eb8916e7db01cb246d04a1fe6f0fdc065b0c/0baadb0eece2c4d939db10d3c323b4652ac79a58/3bb7db43e32190c973d4019037cedb7895920184/9063d7e2615f4a7ab321de6b520e23d370e58816 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (303009), EUVD (EUVD-2026-12912) and CERT Bund (WID-SEC-2026-0790). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Open Source Linux Kernel
Product
Type
Vendor
Name
Version
- 6.12.0
- 6.12.1
- 6.12.2
- 6.12.3
- 6.12.4
- 6.12.5
- 6.12.6
- 6.12.7
- 6.12.8
- 6.12.9
- 6.12.10
- 6.12.11
- 6.12.12
- 6.12.13
- 6.12.14
- 6.12.15
- 6.12.16
- 6.12.17
- 6.12.18
- 6.12.19
- 6.12.20
- 6.12.21
- 6.12.22
- 6.12.23
- 6.12.24
- 6.12.25
- 6.12.26
- 6.12.27
- 6.12.28
- 6.12.29
- 6.12.30
- 6.12.31
- 6.12.32
- 6.12.33
- 6.12.34
- 6.12.35
- 6.12.36
- 6.12.37
- 6.12.38
- 6.12.39
- 6.12.40
- 6.12.41
- 6.12.42
- 6.12.43
- 6.12.44
- 6.12.45
- 6.12.46
- 6.12.47
- 6.12.48
- 6.12.49
- 6.12.50
- 6.12.51
- 6.12.52
- 6.12.53
- 6.12.54
- 6.12.55
- 6.12.56
- 6.12.57
- 6.12.58
- 6.12.59
- 6.12.60
- 6.12.61
- 6.12.62
- 6.12.63
- 6.12.64
- 6.12.65
- 6.12.66
- 6.12.67
- 6.12.68
- 6.12.69
- 6.12.70
- 6.12.71
- 6.12.72
- 6.12.73
- 6.12.74
- 6.12.75
- 6.12.76
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.19.0
- 6.19.1
- 6.19.2
- 6.19.3
- 6.19.4
- 6.19.5
- 6.19.6
- 6.19.7
- 7.0-rc1
- 7.0-rc2
- 7.0-rc3
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.1
CNA Vector (Linux): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 303009
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-23269
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.12.77/6.18.18/6.19.8/7.0-rc4
Patch: 15c3eb8916e7db01cb246d04a1fe6f0fdc065b0c/0baadb0eece2c4d939db10d3c323b4652ac79a58/3bb7db43e32190c973d4019037cedb7895920184/9063d7e2615f4a7ab321de6b520e23d370e58816
Timeline
01/13/2026 CVE reserved03/18/2026 Advisory disclosed
03/18/2026 VulDB entry created
06/01/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CNA: Linux
CVE: CVE-2026-23269 (🔒)
GCVE (CVE): GCVE-0-2026-23269
GCVE (VulDB): GCVE-100-351577
EUVD: 🔒
CERT Bund: WID-SEC-2026-0790 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 03/18/2026 19:51Updated: 06/01/2026 00:36
Changes: 03/18/2026 19:51 (59), 03/18/2026 20:40 (1), 03/19/2026 18:17 (2), 03/19/2026 22:10 (7), 03/24/2026 18:55 (1), 06/01/2026 00:36 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.