Linux Kernel up to 6.6.129/6.12.76/6.18.17/6.19.7/7.0-rc3 apparmor encoding error

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.6.129/6.12.76/6.18.17/6.19.7/7.0-rc3. It has been classified as critical. The impacted element is an unknown function of the component apparmor. This manipulation causes encoding error. This vulnerability is registered as CVE-2026-23409. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.6.129/6.12.76/6.18.17/6.19.7/7.0-rc3. It has been declared as critical. Affected by this vulnerability is an unknown code block of the component apparmor. The manipulation with an unknown input leads to a encoding error vulnerability. The CWE definition for the vulnerability is CWE-172. The product does not properly encode or decode the data, resulting in unexpected values. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: apparmor: fix differential encoding verification Differential encoding allows loops to be created if it is abused. To prevent this the unpack should verify that a diff-encode chain terminates. Unfortunately the differential encode verification had two bugs. 1. it conflated states that had gone through check and already been marked, with states that were currently being checked and marked. This means that loops in the current chain being verified are treated as a chain that has already been verified. 2. the order bailout on already checked states compared current chain check iterators j,k instead of using the outer loop iterator i. Meaning a step backwards in states in the current chain verification was being mistaken for moving to an already verified state. Move to a double mark scheme where already verified states get a different mark, than the current chain being kept. This enables us to also drop the backwards verification check that was the cause of the second error as any already verified state is already marked.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-23409 since 01/13/2026. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/01/2026).

Upgrading to version 6.6.130, 6.12.77, 6.18.18, 6.19.8 or 7.0-rc4 eliminates this vulnerability. Applying the patch f90e3ecd9e1ed69f1a370f866ceed1f104f3ab4a/34fc60b125ed1d4eb002c76b0664bf0619492167/623a9d211bbbb031bb1cbdb38b23487648167f8a/1ff4857fac56ac5a90ee63b24db05fa5e91a45aa/39440b137546a3aa383cfdabc605fb73811b6093 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 vulnerability database at CERT Bund (WID-SEC-2026-0950). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Encoding error
CWE: CWE-172
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.130/6.12.77/6.18.18/6.19.8/7.0-rc4
Patch: f90e3ecd9e1ed69f1a370f866ceed1f104f3ab4a/34fc60b125ed1d4eb002c76b0664bf0619492167/623a9d211bbbb031bb1cbdb38b23487648167f8a/1ff4857fac56ac5a90ee63b24db05fa5e91a45aa/39440b137546a3aa383cfdabc605fb73811b6093

Timelineinfo

01/13/2026 CVE reserved
04/01/2026 +77 days Advisory disclosed
04/01/2026 +0 days VulDB entry created
04/01/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-23409 (🔒)
GCVE (CVE): GCVE-0-2026-23409
GCVE (VulDB): GCVE-100-354625
CERT Bund: WID-SEC-2026-0950 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 04/01/2026 11:26
Updated: 04/01/2026 21:59
Changes: 04/01/2026 11:26 (58), 04/01/2026 21:59 (7)
Complete: 🔍
Cache ID: 216:243:103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!