Linux
ceph: properly decrypt filenames in vmalloc() buffers
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 457117f077c6749d1e28469eae91fb69c9806768, < 23c5cc9652c6ee85617002cb66e1068395045de6
- >= 457117f077c6749d1e28469eae91fb69c9806768, < 93729594af506557a86f8b603be7ac5f3370eeca
- >= 457117f077c6749d1e28469eae91fb69c9806768, < 110747ff535e3d98ac17d68dbd056bb6ef000e23
- >= 457117f077c6749d1e28469eae91fb69c9806768, < 3b467c68803d7c7e82678289e598afd44faa6101
- >= 457117f077c6749d1e28469eae91fb69c9806768, < e939fc6a7bd969a58a150b7f188c1047138403e3
Fixed in 23c5cc9652c6ee85617002cb66e1068395045de6, 93729594af506557a86f8b603be7ac5f3370eeca, 110747ff535e3d98ac17d68dbd056bb6ef000e23, 3b467c68803d7c7e82678289e598afd44faa6101, e939fc6a7bd969a58a150b7f188c1047138403e3
- 6.6
Fixed in 0, 6.6.160, 6.12.111, 6.18.51, 7.2.5, 7.3
Mitigation
Upgrade Linux to 23c5cc9652c6ee85617002cb66e1068395045de6 or 93729594af506557a86f8b603be7ac5f3370eeca or 110747ff535e3d98ac17d68dbd056bb6ef000e23 or 3b467c68803d7c7e82678289e598afd44faa6101 or e939fc6a7bd969a58a150b7f188c1047138403e3 or later.
Upgrade Linux to 0 or 6.6.160 or 6.12.111 or 6.18.51 or 7.2.5 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.