CVE-2026-46333
Vulnérabilité élevée dans Linux (Linux)
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.
Gravité et risque d'exploitation
CVE-2026-46333 obtient un score CVSS de 7.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.51 %, ce qui la place devant 41.8 % des CVE référencées.
Que faire ?
- Vérifiez si Linux (versions <8f907d345bae8f4b3f004c5abc56bf2dfb851ea7, <=6.1.*, <=7.0.*, <=6.12.*, 6.1.173, <31e62c2ebbfdc3fe3dbdf5e02c92a9dc67087a3a, <93d4ba49d18e3d7fb41a9927c2d0cca5e9dfefd6, 6.18.31, 0, 4.9.1, 4.8.16, <4.10, d5b3e840dbf6dd2c0f30b5982b6f5ecd49e46b12, e45692fa1aea06676449b63ef3c2b6e1e72b7578, 6.12.89, <2a93a4fac7b6051d3be7cd1b015fe7320cd0404d, 4.4.40, 694a95fa6dae4991f16cda333d897ea063021fed, <=5.10.*, <=6.6.*, 4.10, <01363cb3fbd0238ffdeb09f53e9039c9edf8a730, 5.10.256, <4.5, <15b828a46f305ae9f05a7c16914b3ce273474205, bfedb589252c01fa505ac9f6f2a3d5d68d707ef4, 7.1, <6e5b51e74a40d377bcd3081dd33fbaa0e1aa7e3d, <4.9, <=6.18.*, <4709234fd1b95136ceb789f639b1e7ea5de1b181, 6.6.139, 03eed7afbc09e061f66b448daf7863174c3dc3f3, 7.0.8, <=*, <=5.15.*, 3.16.52, <3.17, 5.15.207) est présent sur votre parc.
- Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
- À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
- Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.
Références
- https://git.kernel.org/stable/c/93d4ba49d18e3d7fb41a9927c2d0cca5e9dfefd6
- https://git.kernel.org/stable/c/15b828a46f305ae9f05a7c16914b3ce273474205
- https://git.kernel.org/stable/c/4709234fd1b95136ceb789f639b1e7ea5de1b181
- https://git.kernel.org/stable/c/8f907d345bae8f4b3f004c5abc56bf2dfb851ea7
- https://git.kernel.org/stable/c/6e5b51e74a40d377bcd3081dd33fbaa0e1aa7e3d
- https://git.kernel.org/stable/c/2a93a4fac7b6051d3be7cd1b015fe7320cd0404d
- https://git.kernel.org/stable/c/01363cb3fbd0238ffdeb09f53e9039c9edf8a730
- https://git.kernel.org/stable/c/31e62c2ebbfdc3fe3dbdf5e02c92a9dc67087a3a
