CVE Watchtower

CVE-2026-46333Linux Linux Kernel Improper Privilege Management

NVDCVSS scored by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Vulnerability Summary

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.
Severity Level
HIGH(7.1)
Published Date
May 15, 2026
Last Modified
Nov 10, 2026
PoC
Available(Metasploit)
Exploitation Status
Public exploit available
EPSS Score (30-Day)
4.30%Probability
Root Weakness (CWE)
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control.
CVSS v3.1 Base Metrics — Score 7.1 (HIGH)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Attack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone

Affected & Patched Versions

Affected Versions
  • Linux Linux Kernel >= 3.16.52 and < 3.17
  • Linux Linux Kernel >= 4.4.40 and < 4.5
  • Linux Linux Kernel >= 4.8.16 and < 4.9
  • Linux Linux Kernel >= 4.9.1 and < 5.10.256
  • Linux Linux Kernel >= 5.11 and < 5.15.207
  • Linux Linux Kernel >= 5.16 and < 6.1.173
  • Linux Linux Kernel >= 6.2 and < 6.6.139
  • Linux Linux Kernel >= 6.7 and < 6.12.89
  • Linux Linux Kernel >= 6.13 and < 6.18.31
  • Linux Linux Kernel >= 6.19 and < 7.0.8
  • Linux Linux Kernel
  • Debian Debian Linux
Patched Versions
  • Linux Linux Kernel 3.17
  • Linux Linux Kernel 4.5
  • Linux Linux Kernel 4.9
  • Linux Linux Kernel 5.10.256
  • Linux Linux Kernel 5.15.207
  • Linux Linux Kernel 6.1.173
  • Linux Linux Kernel 6.6.139
  • Linux Linux Kernel 6.12.89
  • Linux Linux Kernel 6.18.31
  • Linux Linux Kernel 7.0.8

What to do

Prioritize this fix. Exploit code is public, so attacks can follow quickly.

  1. Check whether you run Linux Linux Kernel and which version.
  2. Update to a patched version listed above, then confirm the new version.
  3. Review logs and exposed services for signs of earlier compromise.

Timeline

  • May 15, 2026Published
  • Nov 10, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Linux Linux Kernel CVEsYou are reading CVE-2026-46333. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

External References

Data last checked: Nov 18, 2026 22:09 UTC