CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic
Noroxi assessment
Priority: Plan (action score 40/100)
- A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
- Because a ready-made attack tool exists, priority is at least “Plan”.
- Probability of exploitation in the next 30 days: 4.2% (FIRST EPSS); higher than 91.1% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 01363cb3fbd0238ffdeb09f53e9039c9edf8a730, 15b828a46f305ae9f05a7c16914b3ce273474205, 2a93a4fac7b6051d3be7cd1b015fe7320cd0404d; azl3 kernel-hwe 6.12.0.0-1 on Azure Linux 3.0 6.12.89.1-1.
Add it to your regular patch cycle. Upgrade to Linux Linux 01363cb3fbd0238ffdeb09f53e9039c9edf8a730, 15b828a46f305ae9f05a7c16914b3ce273474205, 2a93a4fac7b6051d3be7cd1b015fe7320cd0404d; azl3 kernel-hwe 6.12.0.0-1 on Azure Linux 3.0 6.12.89.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2026-06912
- ALSA-2026:19568
- ALSA-2026:19569
- ALSA-2026:19664
- ALSA-2026:19666
- ALSA-2026:A008
- ALSA-2026:A009
- ALSA-2026:A010
- openSUSE-SU-2026:10825-1
- RHSA-2026:19521
- RHSA-2026:19540
- RHSA-2026:19568
- RHSA-2026:19569
- RHSA-2026:19664
- RHSA-2026:19666
- RHSA-2026:19705
- RHSA-2026:19711
- RHSA-2026:19875
- RHSA-2026:20051
- RHSA-2026:20054
- Published
- May 15, 2026
- Updated
- Oct 15, 2026
- EPSS
- 4.2% · 91th percentile
- CWE
- CWE-269
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.2%
- Ready-made attack tool
- 11 / 40 · floor: at least 40
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Weaponized exploit exists
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel4.4.40 and later · before 4.5
- linux linux kernel4.8.16 and later · before 4.9
- linux linux kernel4.9.1 and later · before 5.10.256
- linux linux kernel5.11 and later · before 5.15.207
- linux linux kernel5.16 and later · before 6.1.173
- linux linux kernel3.16.52 and later · before 3.17
- linux linux kernel6.7 and later · before 6.12.89
- linux linux kernel6.13 and later · before 6.18.31
- linux linux kernel6.19 and later · before 7.0.8
- linux linux kernel6.2 and later · before 6.6.139
- linux linux kernel7.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 694a95fa6dae4991f16cda333d897ea063021fed, 4.10, d5b3e840dbf6dd2c0f30b5982b6f5ecd49e46b12, 03eed7afbc09e061f66b448daf7863174c3dc3f3, e45692fa1aea06676449b63ef3c2b6e1e72b7578affected
- 3.16.52 and later · before 3.17affected · semver
- 4.4.40 and later · before 4.5affected · semver
- 4.8.16 and later · before 4.9affected · semver
- 4.9.1 and later · before 4.10affected · semver
- before 4.10not affected · semver
- 5.10.256 and later · up to and including 5.10.*not affected · semver
- 5.15.207 and later · up to and including 5.15.*not affected · semver
- 6.1.173 and later · up to and including 6.1.*not affected · semver
- 6.6.139 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-124.56.5.el10_1 | 6.12.0-124.56.5.el10_1 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43488May 13, 2026 · usb: xhci: Prevent interrupt storm on host controller error (HCE)22Monitor
- ← EarlierCVE-2026-43490May 15, 2026 · ksmbd: validate inherited ACE SID length35Monitor
- Later →CVE-2026-43491May 19, 2026 · net: qrtr: ns: Limit the maximum server registration per node22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 01363cb3fbd0238ffdeb09f53e9039c9edf8a730 | Vendor (CNA) |
| Linux Linux | 15b828a46f305ae9f05a7c16914b3ce273474205 | Vendor (CNA) |
| Linux Linux | 2a93a4fac7b6051d3be7cd1b015fe7320cd0404d | Vendor (CNA) |
| Linux Linux | 3.17 | Vendor (CNA) |
| Linux Linux | 31e62c2ebbfdc3fe3dbdf5e02c92a9dc67087a3a | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 4.9 | Vendor (CNA) |
| Linux Linux | 4709234fd1b95136ceb789f639b1e7ea5de1b181 | Vendor (CNA) |
| Linux Linux | 6e5b51e74a40d377bcd3081dd33fbaa0e1aa7e3d | Vendor (CNA) |
| Linux Linux | 8f907d345bae8f4b3f004c5abc56bf2dfb851ea7 | Vendor (CNA) |
| Linux Linux | 93d4ba49d18e3d7fb41a9927c2d0cca5e9dfefd6 | Vendor (CNA) |
| azl3 kernel-hwe 6.12.0.0-1 on Azure Linux 3.0 | 6.12.89.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 5.14.0-687.10.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-687.10.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-687.10.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-687.10.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-687.10.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-687.10.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-687.10.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-687.10.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-687.10.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-687.10.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-687.10.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-687.10.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.172-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 7.0.9-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-477.143.1.el8_8 · Red Hat:rhel_e4s:8.8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-477.143.1.el8_8 · Red Hat:rhel_e4s:8.8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-477.143.1.el8_8 · Red Hat:rhel_e4s:8.8::baseos | Package registry (OSV) |
+23
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
- Proof-of-concept repository on GitHub ×5
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Metasploit module | post/linux/gather/cve_2026_46333_chageLinux Kernel __ptrace_may_access() Exit Race chage File Disclosurepost | 2026-05-14 |
| Proof-of-concept repository on GitHub | stars:8 | 2026-05-16 |
| Proof-of-concept repository on GitHub | stars:4 | 2026-05-17 |
| Proof-of-concept repository on GitHub | stars:43 | 2026-05-17 |
| Proof-of-concept repository on GitHub | stars:6 | 2026-05-17 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-05 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Metasploit-2 d
- Published
- First PoCsame day
- TodayNov 7, 2026+176 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-269 · Improper Privilege ManagementCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
nvd-secondary
Root cause
To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.
The bug in code
The whole CWE-269 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
kind: ClusterRole
rules:
- apiGroups: ["*"]
resources: ["*"]
verbs: ["*"]Fixed
kind: Role
metadata:
namespace: lodos-system
rules:
- apiGroups: ["apps"]
resources: ["deployments"]
verbs: ["get", "list", "update"]Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- git.kernel.org/stable/c/15b828a46f305ae9f05a7c16914b3ce273474205
- git.kernel.org/stable/c/2a93a4fac7b6051d3be7cd1b015fe7320cd0404d
- git.kernel.org/stable/c/31e62c2ebbfdc3fe3dbdf5e02c92a9dc67087a3a
- git.kernel.org/stable/c/4709234fd1b95136ceb789f639b1e7ea5de1b181
- git.kernel.org/stable/c/6e5b51e74a40d377bcd3081dd33fbaa0e1aa7e3d
- git.kernel.org/stable/c/8f907d345bae8f4b3f004c5abc56bf2dfb851ea7
- git.kernel.org/stable/c/93d4ba49d18e3d7fb41a9927c2d0cca5e9dfefd6
- www.openwall.com/lists/oss-security/2026/05/15/9
- www.openwall.com/lists/oss-security/2026/05/20/14
- www.openwall.com/lists/oss-security/2026/05/20/16
- lists.debian.org/debian-lts-announce/2026/05/msg00032.html
- lists.debian.org/debian-lts-announce/2026/05/msg00035.html
- access.redhat.com/errata/RHSA-2026:19521
- access.redhat.com/errata/RHSA-2026:19540
- access.redhat.com/errata/RHSA-2026:19568
- access.redhat.com/errata/RHSA-2026:19569
- access.redhat.com/errata/RHSA-2026:19664
- access.redhat.com/errata/RHSA-2026:19666
- access.redhat.com/errata/RHSA-2026:19705
Vendor advisories and official records. Exploit/PoC links are deliberately left out.