CVE Enrichment

CVSS
7.1 HIGH
EPSS
0.51%
EPSS Percentile
41.94%
CISA KEV
Not listed

Description

In the Linux kernel, the following vulnerability has been resolved: ptrace: slightly saner 'get_dumpable()' logic The 'dumpability' of a task is fundamentally about the memory image of the task - the concept comes from whether it can core dump or not - and makes no sense when you don't have an associated mm. And almost all users do in fact use it only for the case where the task has a mm pointer. But we have one odd special case: ptrace_may_access() uses 'dumpable' to check various other things entirely independently of the MM (typically explicitly using flags like PTRACE_MODE_READ_FSCREDS). Including for threads that no longer have a VM (and maybe never did, like most kernel threads). It's not what this flag was designed for, but it is what it is. The ptrace code does check that the uid/gid matches, so you do have to be uid-0 to see kernel thread details, but this means that the traditional "drop capabilities" model doesn't make any difference for this all. Make it all make a *bit* more sense by saying that if you don't have a MM pointer, we'll use a cached "last dumpability" flag if the thread ever had a MM (it will be zero for kernel threads since it is never set), and require a proper CAP_SYS_PTRACE capability to override.

Technical Details

CVSS Version
3.1
CNA / NVD Source
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Published
15-May-2026 21:16
Last Modified
15-Oct-2026 09:19
EPSS Date
2026-10-20
CWE
CWE-269

CVSS Vector

CVSS:3.1 AV:L / AC:L / PR:L / UI:N / S:U / C:H / I:H / A:N

Affected Products / Versions

References

Last enrichment sync: 21-Oct-2026 07:28
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.

Reported Context (1)

CVE (9)

MITRE ATT&CK (8)

Vendors (1)

Products (10)

Tools (5)

Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.