Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-23411Published 2026-04-01

CVE-2026-23411 — Linux

high

As of 2026-08-05, CVE-2026-23411 is a HIGH-severity vulnerability in Linux, CVSS v3.1 7.8, EPSS 0.1% (3.2th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-23411, most recently “Linux Kernel LPE Surge: Copy Fail (CVE-2026-31431), Dirty Frag/Fragnesia (CVE-2026-43284/CVE-2026-43500/CVE-2026-46300), and CrackArmor AppArmor Flaws vs. Defense-in-Depth Mitigations”.

CVSS v3.1
7.8/10High
EPSS
0.1%Higher than 3.2% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
4/10Threadlinqs triage score
Published
Updated 2026-08-05
CVSS v3.1 7.8 (HIGH) · EPSS 0.1% (higher than 3.2% of all scored CVEs) · Priority 4/10 · Published 2026-04-01

Last updated:

What is CVE-2026-23411?

In the Linux kernel, the following vulnerability has been resolved: apparmor: fix race between freeing data and fs accessing it AppArmor was putting the reference to i_private data on its end after removing the original entry from the file system. However the inode can aand does live beyond that point and it is possible that some of the fs call back functions will be invoked after the reference has been put, which results in a race between freeing the data and accessing it through the fs. While the rawdata/loaddata is the most likely candidate to fail the race, as it has the fewest references. If properly crafted it might be possible to trigger a race for the other types stored in i_private. Fix this by moving the put of i_private referenced data to the correct place which is during inode eviction.

Its CVSS v3 base vector states that the flaw requires local access to the host, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 207 days ago.

Severity and exploitation probability

CVSS v3.1 base score
7.8 — HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 3.2% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-04-01, last modified 2026-08-05

Is CVE-2026-23411 being exploited?

It currently carries a trending score of 6 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-23411

No vendor patch reference has been recorded for CVE-2026-23411 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-23411

1 tracked threat in the Threadlinqs corpus references CVE-2026-23411, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on .

Other references

Showing 5 of 8 recorded references.