CVE-2026-23409: apparmor: fix differential encoding verification
Published Apr 1, 2026
·Updated
apparmor: fix differential encoding verification
Affected Software
17 affected componentsFixes available
Linux Linux kernel (AppArmor)
Microsoft azl3 kernel 6.6.0.0-1
Linux Linux kernel>=4.17.1<5.10.253
Linux Linux kernel>=5.11<5.15.203
Linux Linux kernel>=5.16<6.1.169
Linux Linux kernel>=6.2<6.6.130
Linux Linux kernel>=6.7<6.12.77
Linux Linux kernel>=6.13<6.18.18
Linux Linux kernel>=6.19<6.19.8
Linux Linux kernel=4.17
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Linux Linux kernel=7.0-rc6
Linux Linux kernel=7.0-rc7
Remediation
Event History
Apr 1, 2026
CVE Published
via MITRE·08:36 AM
Data Sourced
via MITRE·08:36 AM
Description
Data Sourced
via NVD·09:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 10, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2026-23409?
The severity of CVE-2026-23409 is considered high due to potential exploitability.
2
How do I fix CVE-2026-23409?
You can fix CVE-2026-23409 by updating to the latest version of the Linux kernel that addresses this vulnerability.
3
What systems are affected by CVE-2026-23409?
CVE-2026-23409 affects systems running the Linux kernel with AppArmor enabled.
4
What are the potential impacts of CVE-2026-23409?
The potential impacts of CVE-2026-23409 include the exploitation of differential encoding, leading to unauthorized access or denial of service.
5
Is there a known exploit for CVE-2026-23409?
As of now, there are no publicly disclosed exploits specifically for CVE-2026-23409, but it is crucial to patch this vulnerability to prevent future exploit attempts.