ceph: require the dentry lease record to cover struct ceph_mds_reply_lease
Summary
| CVE | CVE-2026-99307 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-16 10:17:05 UTC |
| Updated | 2026-11-16 10:17:05 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: ceph: require the dentry lease record to cover struct ceph_mds_reply_lease parse_reply_info_lease() reads a 32-bit struct_len off the wire and only checks that many bytes are present, without requiring struct_len to cover sizeof(struct ceph_mds_reply_lease) (10 bytes). A malicious MDS can declare a shorter record and still get the pointer published: the following *p += sizeof(**lease) overshoot is undone by *p = lend, so nothing downstream rejects the reply. ceph_fill_trace() -> update_dentry_lease() then reads 10 bytes through that pointer on any lookup on a mounted CephFS, running past the end of the message front. Require the record to cover the structure, matching the sibling parse_reply_info_dir(). A conforming MDS always encodes the full 10 bytes. BUG: KASAN: slab-out-of-bounds in __update_dentry_lease.constprop.0 (fs/ceph/inode.c:1459) Read of size 4 at addr ffff888026c63d65 by task kworker/0:3/2366 Workqueue: ceph-msgr ceph_con_workfn Call Trace: __update_dentry_lease.constprop.0 (fs/ceph/inode.c:1459) ceph_fill_trace (fs/ceph/inode.c:1474 fs/ceph/inode.c:1823) mds_dispatch (fs/ceph/mds_client.c:4229 fs/ceph/mds_client.c:7225) ceph_con_process_message (net/ceph/messenger.c:1424) ceph_con_v1_try_read (net/ceph/messenger_v1.c:1430) ceph_con_workfn (net/ceph/messenger.c:1576) process_one_work (kernel/workqueue.c:3396) worker_thread (kernel/workqueue.c:3479 kernel/workqueue.c:3560) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) The buggy address is located 357 bytes inside of allocated 360-byte region [ffff888026c63c00, ffff888026c63d68) |
Risk And Classification
EPSS: 0.002090000 probability, percentile 0.110940000 (date 2026-11-16)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 4ac4c23eaa389859f746a6ef31e1c71d880312f4 380bc69a0dbc50549cb196da40409aed69c84cfc git | Not specified |
| CNA | Linux | Linux | affected 4ac4c23eaa389859f746a6ef31e1c71d880312f4 5ab17ed54e8b7ca64a8d167a09d6a2c865ed51cc git | Not specified |
| CNA | Linux | Linux | affected 4ac4c23eaa389859f746a6ef31e1c71d880312f4 058e1c38722a6d5b0181f38fdec03d5da95c3ad1 git | Not specified |
| CNA | Linux | Linux | affected 4ac4c23eaa389859f746a6ef31e1c71d880312f4 7286b2ffe04d4b39b4e9884f714792589d94f316 git | Not specified |
| CNA | Linux | Linux | affected 6.6 | Not specified |
| CNA | Linux | Linux | unaffected 6.6 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.117 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.63 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3.4 7.3.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.4-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/380bc69a0dbc50549cb196da40409aed69c84cfc | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/5ab17ed54e8b7ca64a8d167a09d6a2c865ed51cc | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/058e1c38722a6d5b0181f38fdec03d5da95c3ad1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/7286b2ffe04d4b39b4e9884f714792589d94f316 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.