Security readout for executives and security teams
Plain-English summary
A Linux AppArmor race condition can let a locally authenticated, low-privilege user trigger access to data after it has been freed. Successful exploitation could compromise confidentiality, integrity, and availability, although the supplied sources do not confirm a working public exploit or active attacks.
Executive priority
Treat as a high-priority kernel update for shared, multi-user, and untrusted-workload systems. Internet-only exposure is not indicated because local access is required. Schedule remediation through normal emergency patch governance after confirming vendor packages, with faster handling where low-privilege users or containers can interact with the host's AppArmor interfaces.
Technical view
AppArmor released its reference to inode i_private data after removing the filesystem entry, while the inode and filesystem callbacks could remain active. This creates a use-after-free-style race. The kernel fix defers releasing the referenced data until inode eviction. The supplied CVSS 3.1 score is 7.8 with local, low-privilege access required.
Likely exposure
Exposure is most likely on systems running an affected Linux kernel with AppArmor in use and accessible to local low-privilege users or workloads. The supplied version data lists affected releases from 4.13 through 7.0 but is insufficiently structured to determine every fixed boundary; distribution backports may also change exposure.
Exploitation context
The CVE is not listed in KEV, and the supplied sources provide no evidence of active exploitation or a public proof of concept. Exploitation requires local low-privilege access and winning a timing race. AppArmor rawdata or loaddata is identified as the most likely target, with other i_private data types potentially reachable.
Researcher notes
The vulnerable lifetime transition concerns AppArmor filesystem inode i_private references. The source specifically identifies rawdata and loaddata as likely race candidates and states that crafted conditions might affect other stored types. No CWE is supplied. Exact exploitability, affected distribution packages, namespace constraints, and reliable impact have not been established by the provided evidence.
Mitigation direction
- Install a vendor-supported kernel containing the applicable stable fix or confirmed downstream backport.
- Check the Linux distribution's security advisory for exact package versions and reboot requirements.
- Prioritize multi-user systems and hosts running untrusted or tenant-controlled local workloads.
- Restrict unnecessary local access until remediation where operationally practical.
Validation and detection
- Inventory kernel versions and determine whether AppArmor is enabled or used.
- Compare installed packages with the distribution vendor's CVE advisory and fixed-version guidance.
- Confirm the installed kernel changelog includes the relevant upstream fix or an equivalent backport.
- After updating and rebooting, verify the running kernel matches the remediated package.
- Review kernel logs for AppArmor-related crashes or memory-corruption symptoms without treating absence as proof of safety.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2026-23411 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/a92c5e5086a87d082696245a8607666da3d80554CVE reference, Linux
- https://git.kernel.org/stable/c/667df93769c02ff581c77d2d8f162147e719c557CVE reference, Linux
- https://git.kernel.org/stable/c/3ddb961d2929bbb3204a2bba21b5d8153cd3f7ccCVE reference, Linux
- https://git.kernel.org/stable/c/ae10787d955fb255d381e0d5589451dd72c614b1CVE reference, Linux
- https://git.kernel.org/stable/c/eecce026399917f6efa532c56bc7a3e9dd6ee68bCVE reference, Linux
- https://git.kernel.org/stable/c/13bc2772414d68e94e273dea013181a986948ddfCVE reference, Linux
- https://git.kernel.org/stable/c/2a732ed26fbd048e7925d227af8cf9ea43fb5cc9CVE reference, Linux
- https://git.kernel.org/stable/c/8e135b8aee5a06c52a4347a5a6d51223c6f36ba3CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.