AS-2026-011: Linux Kernel (ssh-keysign-pwn)

2026-05-20

Statement

A vulnerability was found in the Linux kernel that allows a local unprivileged attacker to read root-owned files. The vulnerability arises from a race condition during process termination, enabling a brief window where sensitive data, such as SSH host private keys or /etc/shadow contents, can be disclosed.

• CVE-2026-46333 could lead to unauthorized access to sensitive information on affected certain ASUSTOR Products with Linux kernel versions higher than 5.10 and ADM versions ranging from 4.1 to 5.1. Updates with Linux Kernel Patch will be released as soon as possible.

Affected Products

NOT affected NAS models:

• Drivestor (AS1102T, AS1104T)
• Drivestor Pro (AS3302T, AS3304T)
• AS4002T, AS4004T

Detail

• CVE-2026-46333
  • Severity: Medium
  • CVSS3.1 Base Score: 5.5
  • CVSS3.1 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
  • 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.

Reference

• CVE-2026-46333

Revision