CVE-2026-90042

In the Linux kernel, the following vulnerability has been resolved: ceph: properly decrypt filenames in vmalloc() buffers The fscrypt subsystem uses the scatterlist crypto API, inheriting its requirement that any buffers are in the linear mapping region. However, the messenger client uses kvmalloc() to create buffers for messages, which will occasionally place those buffers in the vmalloc() region when physical memory fragmentation doesn't permit a large enough kmalloc(). The various callers of ceph_fname_to_usr() directly pass (slices of) raw messages from the MDS without considering that the messages may be in vmalloc() buffers, resulting in oopses especially on non-x86 platforms (see 'Closes:' for more details and a reproducer). Make ceph_fname_to_usr() explicitly tolerant of vmalloc()-allocated fname->ctext, fname->name, and/or oname->name buffers, using `tname` (which, when non-null, must be a linear address; when null, is briefly allocated as necessary) as a bounce buffer to avoid passing any inappropriate addresses to fscrypt_fname_disk_to_usr(). Additionally change parse_reply_info_readdir() -- the only function to supply its own `tname` -- to follow the new "tname must never come from vmalloc()" rule by passing NULL when the message is not in the linear region. Though this causes a per-dentry kmalloc()+kfree(), this overhead exists only when processing the minority of messages that spill into vmalloc(). My (crude) testing puts this at only about 1 in 8,000 readdir messages. Still, if the overhead proves unreasonable in the future, it is easy enough to mitigate: a future change could allocate a bounce buffer in parse_reply_info_readdir() and use that as `tname` instead.

• https://git.kernel.org/stable/c/110747ff535e3d98ac17d68dbd056bb6ef000e23
• https://git.kernel.org/stable/c/3b467c68803d7c7e82678289e598afd44faa6101
• https://git.kernel.org/stable/c/93729594af506557a86f8b603be7ac5f3370eeca
• https://git.kernel.org/stable/c/e939fc6a7bd969a58a150b7f188c1047138403e3

Published

Sep 16, 2026

Last Modified

Sep 21, 2026

Status

Received

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-90036In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-90037In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-90038In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-90039In the Linux kernel, the following vulnerability has been re…
• CVE-2026-90040In the Linux kernel, the following vulnerability has been re…
• CVE-2026-90041In the Linux kernel, the following vulnerability has been re…8.8
• CVE-2026-90043In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-90044In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-90045In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-90046In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-90047In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-90048In the Linux kernel, the following vulnerability has been re…9.8