Linux Kernel up to 6.6.129/6.12.76/6.18.17/6.19.7/7.0-rc3 apparmor verify_header memory leak

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.5$0-$5k2.56-

Summaryinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.6.129/6.12.76/6.18.17/6.19.7/7.0-rc3. This issue affects the function verify_header of the component apparmor. Executing a manipulation can lead to memory leak. This vulnerability is tracked as CVE-2026-23403. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 6.6.129/6.12.76/6.18.17/6.19.7/7.0-rc3 and classified as critical. This vulnerability affects the function verify_header of the component apparmor. The manipulation with an unknown input leads to a memory leak vulnerability. The CWE definition for the vulnerability is CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. As an impact it is known to affect availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: apparmor: fix memory leak in verify_header The function sets `*ns = NULL` on every call, leaking the namespace string allocated in previous iterations when multiple profiles are unpacked. This also breaks namespace consistency checking since *ns is always NULL when the comparison is made. Remove the incorrect assignment. The caller (aa_unpack) initializes *ns to NULL once before the loop, which is sufficient.

The advisory is available at git.kernel.org. This vulnerability was named CVE-2026-23403 since 01/13/2026. Technical details are known, but there is no available exploit.

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 663ce34786e759ebcbeb3060685c20bcc886d51a/786e2c2a87d9c505f33321d1fd23a176aa8ddeb1/4f0889f2df1ab99224a5e1ac4e20437eea5fe38e/42fd831abfc15d0643c14688f0522556b347e7e6/e38c55d9f834e5b848bfed0f5c586aaf45acb825 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). Once again VulDB remains the best source for 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.7
VulDB Meta Temp Score: 5.5

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

CVSSv2info

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

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

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
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: 663ce34786e759ebcbeb3060685c20bcc886d51a/786e2c2a87d9c505f33321d1fd23a176aa8ddeb1/4f0889f2df1ab99224a5e1ac4e20437eea5fe38e/42fd831abfc15d0643c14688f0522556b347e7e6/e38c55d9f834e5b848bfed0f5c586aaf45acb825

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-23403 (🔒)
GCVE (CVE): GCVE-0-2026-23403
GCVE (VulDB): GCVE-100-354622
CERT Bund: WID-SEC-2026-0950 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 04/01/2026 11:25
Updated: 04/01/2026 21:59
Changes: 04/01/2026 11:25 (59), 04/01/2026 21:59 (7)
Complete: 🔍
Cache ID: 216:2DB:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to stay up to date on a daily basis?

Enable the mail alert feature now!