{"api_version":"1","generated_at":"2026-09-16T16:13:56+00:00","cve":"CVE-2026-90042","urls":{"html":"https://cve.report/CVE-2026-90042","api":"https://cve.report/api/cve/CVE-2026-90042.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-90042","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-90042"},"summary":{"title":"ceph: properly decrypt filenames in vmalloc() buffers","description":"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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-16 11:17:17","updated_at":"2026-09-16 15:18:26"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","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","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":9.8,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","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","data":{"baseScore":9.8,"baseSeverity":"CRITICAL","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/110747ff535e3d98ac17d68dbd056bb6ef000e23","name":"https://git.kernel.org/stable/c/110747ff535e3d98ac17d68dbd056bb6ef000e23","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/3b467c68803d7c7e82678289e598afd44faa6101","name":"https://git.kernel.org/stable/c/3b467c68803d7c7e82678289e598afd44faa6101","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e939fc6a7bd969a58a150b7f188c1047138403e3","name":"https://git.kernel.org/stable/c/e939fc6a7bd969a58a150b7f188c1047138403e3","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-90042","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90042","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 457117f077c6749d1e28469eae91fb69c9806768 110747ff535e3d98ac17d68dbd056bb6ef000e23 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 457117f077c6749d1e28469eae91fb69c9806768 3b467c68803d7c7e82678289e598afd44faa6101 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 457117f077c6749d1e28469eae91fb69c9806768 e939fc6a7bd969a58a150b7f188c1047138403e3 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.6","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.51 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.5 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/ceph/crypto.c","fs/ceph/mds_client.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"110747ff535e3d98ac17d68dbd056bb6ef000e23","status":"affected","version":"457117f077c6749d1e28469eae91fb69c9806768","versionType":"git"},{"lessThan":"3b467c68803d7c7e82678289e598afd44faa6101","status":"affected","version":"457117f077c6749d1e28469eae91fb69c9806768","versionType":"git"},{"lessThan":"e939fc6a7bd969a58a150b7f188c1047138403e3","status":"affected","version":"457117f077c6749d1e28469eae91fb69c9806768","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/ceph/crypto.c","fs/ceph/mds_client.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.6"},{"lessThan":"6.6","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.51","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.51","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.5","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"6.6","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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."}],"metrics":[{"cvssV3_1":{"baseScore":9.8,"baseSeverity":"CRITICAL","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:N - ceph_fname_to_usr() runs while parsing CEPH_MSG_CLIENT_REPLY on the kernel CephFS client TCP session (mds_dispatch → handle_reply → parse_reply_info_readdir/fill_trace); a malicious or compromised MDS delivers the kvmalloc'd filename buffers that are passed into fscrypt.\nAC:L - The MDS fully controls hdr.front_len (up to CEPH_MSG_MAX_FRONT_LEN, 16MB). kvmalloc() of that size skips costly kmalloc reclaim and falls back to vmalloc deterministically, so sg_init_one() on the message names does not depend on incidental fragmentation or a race.\nPR:N - The attacker is the remote MDS peer on an already-connected kernel CephFS client and needs no Linux UID, capability, or init-namespace root on the victim, matching other MDS-driven client CVEs such as CVE-2026-89651.\nUI:N - Once encrypted CephFS is mounted with keys loaded (standard in Rook/Kubernetes/OpenStack, including NFS re-export LOOKUPNAME), readdir and lookup replies are processed automatically in the ceph-msgr path with no further victim mount or interactive step at exploit time.\nS:U - Wrong-page scatterlist crypto and any resulting kernel memory corruption stay inside the victim host's CephFS client and do not cross a VM, IOMMU, or sandbox security boundary.\nC:H - fname_decrypt() builds src_sg with sg_set_buf()/virt_to_page() on the vmalloc MDS buffer, so skcipher decryption reads unintended kernel pages as ciphertext; that memory-corruption read is High per kernel UAF/wrong-page guidance.\nI:H - parse_reply_info_readdir() decrypts filenames in place, so dst_sg also aliases the vmalloc message; crypto_skcipher_decrypt() then writes plaintext through virt_to_page() of a non-linear address, a wrong-page kernel write scored High.\nA:H - Passing vmalloc addresses into the scatterlist crypto API oopses or panics, especially on non-x86 where virt_to_page() of a non-linear address faults in scatterwalk, and a malicious MDS can repeat this on every encrypted readdir reply."}]}],"providerMetadata":{"dateUpdated":"2026-09-16T14:41:54.935Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/110747ff535e3d98ac17d68dbd056bb6ef000e23"},{"url":"https://git.kernel.org/stable/c/3b467c68803d7c7e82678289e598afd44faa6101"},{"url":"https://git.kernel.org/stable/c/e939fc6a7bd969a58a150b7f188c1047138403e3"}],"title":"ceph: properly decrypt filenames in vmalloc() buffers","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-90042","datePublished":"2026-09-16T10:33:40.210Z","dateReserved":"2026-09-11T19:38:34.783Z","dateUpdated":"2026-09-16T14:41:54.935Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-16 11:17:17","lastModifiedDate":"2026-09-16 15:18:26","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":9.8,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":3.9,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"90042","Ordinal":"1","Title":"ceph: properly decrypt filenames in vmalloc() buffers","CVE":"CVE-2026-90042","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"90042","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"ceph: properly decrypt filenames in vmalloc() buffers"}]}}}