Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-23410Published 2026-04-01

CVE-2026-23410 — Linux

high

As of 2026-08-05, CVE-2026-23410 is a HIGH-severity vulnerability in Linux, CVSS v3.1 7.8, EPSS 0.1% (2.9th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-23410, 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 2.9% 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 2.9% of all scored CVEs) · Priority 4/10 · Published 2026-04-01

Last updated:

What is CVE-2026-23410?

In the Linux kernel, the following vulnerability has been resolved: apparmor: fix race on rawdata dereference There is a race condition that leads to a use-after-free situation: because the rawdata inodes are not refcounted, an attacker can start open()ing one of the rawdata files, and at the same time remove the last reference to this rawdata (by removing the corresponding profile, for example), which frees its struct aa_loaddata; as a result, when seq_rawdata_open() is reached, i_private is a dangling pointer and freed memory is accessed. The rawdata inodes weren't refcounted to avoid a circular refcount and were supposed to be held by the profile rawdata reference. However during profile removal there is a window where the vfs and profile destruction race, resulting in the use after free. Fix this by moving to a double refcount scheme. Where the profile refcount on rawdata is used to break the circular dependency. Allowing for freeing of the rawdata once all inode references to the rawdata are put.

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 2.9% 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-23410 being exploited?

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

Affected products and versions

How to fix CVE-2026-23410

No vendor patch reference has been recorded for CVE-2026-23410 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-23410

1 tracked threat in the Threadlinqs corpus references CVE-2026-23410, 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.