{"id":"CVE-2026-90042","aliases":[],"url":"https://o3.security/vulnerability/CVE-2026-90042","summary":"ceph: properly decrypt filenames in vmalloc() buffers","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nceph: properly decrypt filenames in vmalloc() buffers\n\nThe fscrypt subsystem uses the scatterlist crypto API, inheriting its\nrequirement that any buffers are in the linear mapping region. However,\nthe messenger client uses kvmalloc() to create buffers for messages,\nwhich will occasionally place those buffers in the vmalloc() region when\nphysical memory fragmentation doesn't permit a large enough kmalloc().\nThe various callers of ceph_fname_to_usr() directly pass (slices of) raw\nmessages from the MDS without considering that the messages may be in\nvmalloc() buffers, resulting in oopses especially on non-x86 platforms\n(see 'Closes:' for more details and a reproducer).\n\nMake ceph_fname_to_usr() explicitly tolerant of vmalloc()-allocated\nfname->ctext, fname->name, and/or oname->name buffers, using `tname`\n(which, when non-null, must be a linear address; when null, is briefly\nallocated as necessary) as a bounce buffer to avoid passing any\ninappropriate addresses to fscrypt_fname_disk_to_usr().\n\nAdditionally change parse_reply_info_readdir() -- the only function to\nsupply its own `tname` -- to follow the new \"tname must never come from\nvmalloc()\" rule by passing NULL when the message is not in the linear\nregion. Though this causes a per-dentry kmalloc()+kfree(), this overhead\nexists only when processing the minority of messages that spill into\nvmalloc(). My (crude) testing puts this at only about 1 in 8,000 readdir\nmessages. Still, if the overhead proves unreasonable in the future, it\nis easy enough to mitigate: a future change could allocate a bounce\nbuffer in parse_reply_info_readdir() and use that as `tname` instead.","published":"2026-09-16T10:33:40.210Z","modified":"2026-09-17T03:47:27.635873762Z","cvss":{"score":9.8,"severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"},"epss":null,"cisaKev":null,"exploitsKnown":null,"affectedPackages":[{"ecosystem":"Linux","name":"Kernel","fixedVersion":"6.18.51"}],"fix":null,"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/110747ff535e3d98ac17d68dbd056bb6ef000e23"},{"type":"WEB","url":"https://git.kernel.org/stable/c/3b467c68803d7c7e82678289e598afd44faa6101"},{"type":"WEB","url":"https://git.kernel.org/stable/c/e939fc6a7bd969a58a150b7f188c1047138403e3"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90042.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90042"}],"provenance":{"sources":["OSV.dev","FIRST.org (EPSS)"],"lastVerified":"2026-09-17T03:47:27.635873762Z"}}