CVE-2026-46333: Linux Kernel privilege escalation (CVSS 7.1)

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.

CVSS 3.1 breakdown

Attack vectorLocal

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityNone

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

Affected products

Debian Linux11.0

Linux Kernel≥ 3.16.52 < 3.17 · ≥ 4.4.40 < 4.5 · ≥ 4.8.16 < 4.9 · ≥ 4.9.1 < 5.10.256

Remediation

Fixed in

Linux Kernel≥ 3.17

Patch & vendor advisories

References

https://access.redhat.com/errata/RHSA-2026:19521Third Party Advisory
https://access.redhat.com/errata/RHSA-2026:19540Third Party Advisory
https://access.redhat.com/errata/RHSA-2026:19568Third Party Advisory
https://access.redhat.com/errata/RHSA-2026:19569Third Party Advisory
https://access.redhat.com/errata/RHSA-2026:19664Third Party Advisory
https://access.redhat.com/errata/RHSA-2026:19666Third Party Advisory
https://access.redhat.com/errata/RHSA-2026:19705Third Party Advisory
https://access.redhat.com/errata/RHSA-2026:19711Third Party Advisory
https://access.redhat.com/errata/RHSA-2026:19875Third Party Advisory
https://access.redhat.com/errata/RHSA-2026:20051Third Party Advisory

and 31 more references

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-46333 being actively exploited?

CVE-2026-46333 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.51%.

How severe is CVE-2026-46333?

CVE-2026-46333 has a CVSS 3.1 base score of 7.1, rated high. EPSS estimates a 0.51% probability of exploitation.

Which products are affected by CVE-2026-46333?

Affected products include Debian Linux, Linux Kernel.

How do I fix CVE-2026-46333?

Upgrade affected software to a fixed version, for example Linux Kernel 3.17 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-46333 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo