CVE-2026-46333

published 15 May 2026 · updated 17 Nov 2026

ptrace: slightly saner 'get_dumpable()' logic

8.1HighCVSS 7.1EPSS 4%3 public exploits

3 public exploits exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 4%. Fixed in Kernel 6.12.89, Kernel 3.17, Kernel 4.5 and 16 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=6.7 <6.12.89, >=3.16.52 <3.17, >=4.4.40 <4.5, >=4.8.16 <4.9, >=4.9.1 <5.10.256, >=5.11 <5.15.207, >=5.16 <6.1.173, >=6.13 <6.18.31, >=6.19 <7.0.8, >=6.2 <6.6.139, >=4.9.1 <4.10, >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <01363cb3fbd0238ffdeb09f53e9039c9edf8a730, >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <15b828a46f305ae9f05a7c16914b3ce273474205, >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <2a93a4fac7b6051d3be7cd1b015fe7320cd0404d, >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <31e62c2ebbfdc3fe3dbdf5e02c92a9dc67087a3a, >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <4709234fd1b95136ceb789f639b1e7ea5de1b181, >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <6e5b51e74a40d377bcd3081dd33fbaa0e1aa7e3d, >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <8f907d345bae8f4b3f004c5abc56bf2dfb851ea7, >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <93d4ba49d18e3d7fb41a9927c2d0cca5e9dfefd6, =7.1, =03eed7afbc09e061f66b448daf7863174c3dc3f3, =4.10, =694a95fa6dae4991f16cda333d897ea063021fed, =d5b3e840dbf6dd2c0f30b5982b6f5ecd49e46b12, =e45692fa1aea06676449b63ef3c2b6e1e72b75786.12.89, 3.17, 4.5, 4.9, 5.10.256, 5.15.207, 6.1.173, 6.18.31, 7.0.8, 6.6.139, 4.10, 01363cb3fbd0238ffdeb09f53e9039c9edf8a730, 15b828a46f305ae9f05a7c16914b3ce273474205, 2a93a4fac7b6051d3be7cd1b015fe7320cd0404d, 31e62c2ebbfdc3fe3dbdf5e02c92a9dc67087a3a, 4709234fd1b95136ceb789f639b1e7ea5de1b181, 6e5b51e74a40d377bcd3081dd33fbaa0e1aa7e3d, 8f907d345bae8f4b3f004c5abc56bf2dfb851ea7, 93d4ba49d18e3d7fb41a9927c2d0cca5e9dfefd6
debiandebian_linux=11.0
linux-kernel: Kernel>=6.19.0 <7.0.8, >=6.2.0 <6.6.139, >=6.7.0 <6.12.89, >=3.16.52 <3.17, >=4.10.0 <5.10.256, >=4.4.40 <4.5, >=4.8.16 <4.9, >=4.9.1 <4.10, >=5.11.0 <5.15.207, >=5.16.0 <6.1.173, >=6.13.0 <6.18.317.0.8, 6.6.139, 6.12.89, 3.17, 5.10.256, 4.5, 4.9, 4.10, 5.15.207, 6.1.173, 6.18.31

Exploit evidence

3 public sources

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-46333 severity on Zeptric[![CVE-2026-46333](https://zeptric.io/badge/cve/CVE-2026-46333.svg)](https://zeptric.io/cve/CVE-2026-46333)