Answer in brief
CVE-2026-46333 records a High severity (CVSS 7.1) vulnerability in ptrace: slightly saner 'get_dumpable()' logic. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Red Hat/openshift/ose-rhel-coreos-9 (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Red Hat/openshift/ose-rhel-coreos-9 (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <93d4ba49d18e3d7fb41a9927c2d0cca5e9dfefd6 || >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <15b828a46f305ae9f05a7c16914b3ce273474205 || >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <4709234fd1b95136ceb789f639b1e7ea5de1b181 || >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <8f907d345bae8f4b3f004c5abc56bf2dfb851ea7 || >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <6e5b51e74a40d377bcd3081dd33fbaa0e1aa7e3d || >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <2a93a4fac7b6051d3be7cd1b015fe7320cd0404d || >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <01363cb3fbd0238ffdeb09f53e9039c9edf8a730 || >=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 <31e62c2ebbfdc3fe3dbdf5e02c92a9dc67087a3a || d5b3e840dbf6dd2c0f30b5982b6f5ecd49e46b12 || 03eed7afbc09e061f66b448daf7863174c3dc3f3 || e45692fa1aea06676449b63ef3c2b6e1e72b7578 || 694a95fa6dae4991f16cda333d897ea063021fed || >=3.16.52 <3.17 || >=4.4.40 <4.5 || >=4.8.16 <4.9 || >=4.9.1 <4.10 | 93d4ba49d18e3d7fb41a9927c2d0cca5e9dfefd6, 15b828a46f305ae9f05a7c16914b3ce273474205, 4709234fd1b95136ceb789f639b1e7ea5de1b181, 8f907d345bae8f4b3f004c5abc56bf2dfb851ea7, 6e5b51e74a40d377bcd3081dd33fbaa0e1aa7e3d, 2a93a4fac7b6051d3be7cd1b015fe7320cd0404d, 01363cb3fbd0238ffdeb09f53e9039c9edf8a730, 31e62c2ebbfdc3fe3dbdf5e02c92a9dc67087a3a, 3.17, 4.5, 4.9, 4.10 |
| Linux/Linuxgeneric | 4.10 | Not reported |
| Red Hat/openshift/ose-rhel-coreos-9generic | * | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.7 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.7 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.7 <* | * |
Published upstream
May 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 30, 2026
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.
Quoted source text, attributed separately from HOL analysis.