CVE-2026-90042ceph: properly decrypt filenames in vmalloc() buffers
- 9.8CriticalCVSS base score
- 0.50%Exploitation in 30 daysEPSS · top 56% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 35 days later
· 35 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.50% · top 56% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected 457117f077c6749d1e28469eae91fb69c9806768 – < 23c5cc9652c6ee85617002cb66e1068395045de6
- affected 457117f077c6749d1e28469eae91fb69c9806768 – < 93729594af506557a86f8b603be7ac5f3370eeca
- affected 457117f077c6749d1e28469eae91fb69c9806768 – < 110747ff535e3d98ac17d68dbd056bb6ef000e23
- affected 457117f077c6749d1e28469eae91fb69c9806768 – < 3b467c68803d7c7e82678289e598afd44faa6101
- affected 457117f077c6749d1e28469eae91fb69c9806768 – < e939fc6a7bd969a58a150b7f188c1047138403e3
- affected 6.6
- unaffected < 6.6
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.51 – ≤ 6.18.*
- unaffected 7.2.5 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/23c5cc9652c6ee85617002cb66e1068395045de6 (opens in a new tab)
- https://git.kernel.org/stable/c/93729594af506557a86f8b603be7ac5f3370eeca (opens in a new tab)
- https://git.kernel.org/stable/c/110747ff535e3d98ac17d68dbd056bb6ef000e23 (opens in a new tab)
- https://git.kernel.org/stable/c/3b467c68803d7c7e82678289e598afd44faa6101 (opens in a new tab)
- https://git.kernel.org/stable/c/e939fc6a7bd969a58a150b7f188c1047138403e3 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-80650 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90042)Record last updated .