Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-46333Published 2026-05-15

CVE-2026-46333 — Linux

highPublic exploit6 PoC repos

As of 2026-09-08, CVE-2026-46333 is a HIGH-severity vulnerability in Linux, CVSS v3.1 7.1, EPSS 0.5% (41.2th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-46333, most recently “F5OS / Traffix SDC Information Disclosure (CVE-2026-46333) — Linux Kernel ptrace/pidfd_getfd Race Condition, Public PoC (CHARON)”.

CVSS v3.1
7.1/10High
EPSS
0.5%Higher than 41.2% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
7.2/10Threadlinqs triage score
Published
Updated 2026-09-08
CVSS v3.1 7.1 (HIGH) · EPSS 0.5% (higher than 41.2% of all scored CVEs) · Priority 7.2/10 · Published 2026-05-15

Last updated:

What is CVE-2026-46333?

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.

The record classifies CVE-2026-46333 under weakness class CWE-269. 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. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 166 days ago.

Severity and exploitation probability

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

Is CVE-2026-46333 being exploited?

Weaponised exploit code for CVE-2026-46333 is publicly available. 6 public proof-of-concept repositories are tracked for this identifier. It currently carries a trending score of 23 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-46333

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

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

Sources

Enriched from CVE.org, FIRST EPSS, public proof-of-concept repositories. Last verified by Threadlinqs on .

Other references

Showing 5 of 8 recorded references.