CVE-2026-23269

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-03-18. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

March 18, 2026

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 4, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available
https://www.qualys.com/2026/03/10/crack-armor.txt
generic

apparmor: validate DFA start states are in bounds in unpack_pdb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f43eea8ae0102ea198da211ef7f5ce83725ecf19
generic

apparmor: validate DFA start states are in bounds in unpack_pdb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9063d7e2615f4a7ab321de6b520e23d370e58816
generic

apparmor: validate DFA start states are in bounds in unpack_pdb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5487871b2b56c19d26936ed6fdc62652b30941df
generic

apparmor: validate DFA start states are in bounds in unpack_pdb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5443c027ec16afa55b1b8a3e7a1ab2ea3c77767a
generic

apparmor: validate DFA start states are in bounds in unpack_pdb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3bb7db43e32190c973d4019037cedb7895920184
generic

apparmor: validate DFA start states are in bounds in unpack_pdb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15c3eb8916e7db01cb246d04a1fe6f0fdc065b0c
generic

apparmor: validate DFA start states are in bounds in unpack_pdb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0baadb0eece2c4d939db10d3c323b4652ac79a58
generic

apparmor: validate DFA start states are in bounds in unpack_pdb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/07cf6320f40ea2ccfad63728cff34ecb309d03da

Vendor Advisories for CVE-2026-23269(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(16)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-06-11ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1017.17) @ noble2026-06-11ubuntu
ubuntulowlatency-4.15 (4.15.0-143) @ xenial2026-06-11ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-06-11ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-06-11ubuntu
ubuntulinux-tools-azure-edge (5.4.0.1161.167~18.04.1) @ bionic2026-06-11ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-06-11ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1096.100) @ jammy2026-06-11ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1139.170) @ focal2026-06-11ubuntu
ubuntulinux-tools-bluefield-5.4 (5.4.0.1116.112) @ focal2026-06-11ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-06-11ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-06-11ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.249.261~16.04.1) @ xenial2026-06-11ubuntu
ubuntulinux-tools-oracle (4.15.0.1153.164~16.04.1) @ xenial2026-06-11ubuntu
linuxKernel @ 5.10.253—osv
linuxKernel @ 6.6.130—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (49 versions)5.10.251-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (47 versions)6.1.164-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.74-2~bpo12+1 (15 versions)6.12.74-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (118 versions)6.19.6-2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(14)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 217 total refreshes for this CVE.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 18:08 UTCOSV refresh
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-25 13:48 UTCEPSS rescore
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 11:15 UTCEG score recompute
  4. 2026-08-16 11:15 UTCVendor advisory
  5. 2026-08-16 11:15 UTCGHSA enrichment
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 19:56 UTCVendor advisory
  9. 2026-08-14 19:56 UTCGHSA enrichment
  10. 2026-08-14 07:24 UTCEG score recompute
  11. 2026-08-14 07:24 UTCVendor advisory
  12. 2026-08-14 07:24 UTCGHSA enrichment
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-12 22:10 UTCEG score recompute
  15. 2026-08-12 22:10 UTCVendor advisory
  16. 2026-08-12 22:10 UTCGHSA enrichment
  17. 2026-08-12 13:50 UTCEPSS rescore
  18. 2026-08-11 21:31 UTCEG score recompute
  19. 2026-08-11 21:31 UTCVendor advisory
  20. 2026-08-11 21:31 UTCGHSA enrichment
  21. 2026-08-11 13:42 UTCEPSS rescore
  22. 2026-08-11 04:36 UTCEG score recompute
  23. 2026-08-11 04:36 UTCVendor advisory
  24. 2026-08-11 04:36 UTCGHSA enrichment
  25. 2026-08-11 00:00 UTCEPSS rescore
  26. 2026-08-10 05:09 UTCVendor advisory
  27. 2026-08-10 05:09 UTCGHSA enrichment
  28. 2026-08-09 18:03 UTCEG score recompute
  29. 2026-08-09 18:03 UTCVendor advisory
  30. 2026-08-09 18:03 UTCGHSA enrichment
  31. 2026-08-09 13:46 UTCEPSS rescore
  32. 2026-08-09 06:58 UTCEG score recompute
  33. 2026-08-09 06:58 UTCVendor advisory
  34. 2026-08-09 06:58 UTCGHSA enrichment
  35. 2026-08-08 16:37 UTCEPSS rescore
  36. 2026-08-08 04:35 UTCVendor advisory
  37. 2026-08-08 04:35 UTCGHSA enrichment
  38. 2026-08-07 17:31 UTCEG score recompute
  39. 2026-08-07 17:31 UTCVendor advisory
  40. 2026-08-07 17:31 UTCGHSA enrichment
  41. 2026-08-06 19:29 UTCEG score recompute
  42. 2026-08-06 19:29 UTCVendor advisory
  43. 2026-08-06 19:29 UTCGHSA enrichment
  44. 2026-08-06 13:46 UTCEPSS rescore
  45. 2026-08-06 01:37 UTCEG score recompute
  46. 2026-08-06 01:37 UTCVendor advisory
  47. 2026-08-06 01:37 UTCGHSA enrichment
  48. 2026-08-05 19:17 UTCEPSS rescore
  49. 2026-08-05 12:44 UTCEG score recompute
  50. 2026-08-05 12:44 UTCVendor advisory
  51. 2026-08-05 12:43 UTCGHSA enrichment
  52. 2026-08-04 15:10 UTCEPSS rescore
  53. 2026-08-04 10:38 UTCEPSS rescore
  54. 2026-08-04 00:48 UTCEG score recompute
  55. 2026-08-04 00:48 UTCVendor advisory
  56. 2026-08-04 00:48 UTCGHSA enrichment
  57. 2026-08-03 10:35 UTCEPSS rescore
  58. 2026-08-02 16:41 UTCEG score recompute
  59. 2026-08-02 16:41 UTCVendor advisory
  60. 2026-08-02 16:41 UTCGHSA enrichment
  61. 2026-08-02 02:26 UTCEPSS rescore
  62. 2026-08-01 04:15 UTCEPSS rescore
  63. 2026-07-30 01:30 UTCEPSS rescore
  64. 2026-07-27 14:13 UTCEPSS rescore
  65. 2026-07-26 14:54 UTCEPSS rescore
  66. 2026-07-26 14:54 UTCEPSS rescore
  67. 2026-07-25 14:17 UTCEPSS rescore
  68. 2026-07-25 14:17 UTCEPSS rescore
  69. 2026-07-24 14:17 UTCEPSS rescore
  70. 2026-07-23 14:18 UTCEPSS rescore
  71. 2026-07-23 14:18 UTCEPSS rescore
  72. 2026-07-23 03:06 UTCEG score recompute
  73. 2026-07-22 14:08 UTCEPSS rescore
  74. 2026-07-21 15:24 UTCEPSS rescore
  75. 2026-07-21 15:24 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-23269?
CVE-2026-23269 is a high vulnerability published on March 18, 2026. 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 aadfanext() function call in unpack_pdb() will access…
When was CVE-2026-23269 disclosed?
CVE-2026-23269 was first published in the National Vulnerability Database on March 18, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23269 actively exploited?
CVE-2026-23269 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-23269?
CVE-2026-23269 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-23269?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23269, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23269

Explore →

Is Your Infrastructure Affected by CVE-2026-23269?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs