Linux kernel out-of-bounds read in Ceph snap trace bounds check
Affects the Linux kernel Ceph client (fs/ceph) when it processes snap traces from a malicious or compromised metadata server (MDS). The facts name no fixed versions or patch ids.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The Linux kernel's Ceph filesystem client has an integer overflow in its snapshot trace bounds check. A malicious or compromised metadata server can send a crafted snapshot message that makes the kernel read memory past the end of the received message buffer. No action by the client is needed, since the read can happen when the client processes an unsolicited snapshot message, an MDS reply, or a capability import that carries a snapshot trace.
Written by a model
Original description
In the Linux kernel, the following vulnerability has been resolved:
ceph: fix integer overflow in the snap trace bounds check
ceph_update_snap_trace() bounds the two encoded snapid arrays that follow a struct ceph_mds_snap_realm with sizeof(u64) * (num_snaps + num_prior_parent_snaps). Both counts come straight off the wire as __le32, so the addition is evaluated in unsigned int and wraps before sizeof(u64) promotes it to size_t: an MDS sending num_snaps = 1 and num_prior_parent_snaps = 0xffffffff makes the sum zero and the check degenerates to ceph_decode_need(&p, e, 0, bad), which always passes. dup_array() then reads num_snaps * 8 bytes past the end of the message front, which ceph_msg_new2() allocates at exactly front_len bytes. An unsolicited CEPH_MSG_CLIENT_SNAP reaches this from a malicious or compromised MDS with no client-side action, as do the snaptraces carried in an MDS reply and in a cap import.
Compute the length with size_add()/size_mul() so it saturates at SIZE_MAX instead of wrapping, in the style fs/ceph/mdsmap.c already uses for num_export_targets.
BUG: KASAN: slab-out-of-bounds in dup_array (include/linux/unaligned.h:28 fs/ceph/snap.c:500) Read of size 8 at addr ffff8880102a16c8 by task kworker/1:2/129 Workqueue: ceph-msgr ceph_con_workfn Call Trace: dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120) print_report (mm/kasan/report.c:378 mm/kasan/report.c:482) kasan_report (mm/kasan/report.c:595) dup_array (include/linux/unaligned.h:28 fs/ceph/snap.c:500) ceph_update_snap_trace (fs/ceph/snap.c:836) ceph_handle_snap (fs/ceph/snap.c:1155) mds_dispatch (fs/ceph/mds_client.c:7234) 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 0 bytes to the right of allocated 72-byte region [ffff8880102a1680, ffff8880102a16c8)
Who should check
Teams running Linux kernels with the Ceph client (CephFS mounts) that connect to an MDS which could be malicious or compromised.
“ceph_update_snap_trace() bounds the two encoded snapid arrays that follow a struct ceph_mds_snap_realm with sizeof(u64) * (num_snaps + num_prior_parent_snaps).”
What to do
Workaround: The facts name no workaround. Since the trigger is a malicious or compromised MDS, the exposure can be limited by mounting CephFS only from metadata servers that are trusted and secured.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99304 (ceph: fix integer overflow in the snap trace bounds check), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99304 (entry last updated 2026-11-19):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 2.6.34
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Linux kernel Ceph client (fs/ceph) processing snap traces from an MDS (source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bf8f13872959af1d87e36b7d27096a09fdcf6e47)
- The MDS (metadata server) the client talks to is malicious or compromised (source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bf8f13872959af1d87e36b7d27096a09fdcf6e47)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-99304 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99304 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/bf8f13872959af1d87e36b7d27096a09fdcf6e47
- https://git.kernel.org/stable/c/f0dbd6b9b05e919ebab668f3479aebbcd2431fce
- https://git.kernel.org/stable/c/25ae51760b751d170e29425b7851ee577e2cd5ba
- https://git.kernel.org/stable/c/b3bf89767e3ca9506f1c7167cac97c41ec254d42
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bf8f13872959af1d87e36b7d27096a09fdcf6e47
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99304
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99304"}.Affected versions
- Linux LinuxVersion range not reported
- Linux Linux2.6.34
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity9.8/10CVSS 9.8
- No patch5/5No patch listed yet
What would change the score
- Would score about 97 if added to CISA KEV
- Would score about 92 if CISA's SSVC rates exploitation active
- Would score about 57 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now3 days
- Record last updated
- Posted on X by cve.now
Public exploit activity
- EPSS: 0.16%
- Posted on X by cve.now Nov 19
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99304 |
| Record | NVD · CVE-2026-99304 |
| Other links 4 | |
| Link | git.kernel.org · stable/c/bf8f13872959af1d87e36b7d27096a09fdcf6e47 |
| Link | git.kernel.org · stable/c/f0dbd6b9b05e919ebab668f3479aebbcd2431fce |
| Link | git.kernel.org · stable/c/25ae51760b751d170e29425b7851ee577e2cd5ba |
| Link | git.kernel.org · stable/c/b3bf89767e3ca9506f1c7167cac97c41ec254d42 |
Questions about CVE-2026-99304
Is CVE-2026-99304 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The Ceph client checks the bounds of two snapid arrays in a snap trace, but an integer overflow in that check lets a bad length pass. The kernel can then read past the end of the message buffer. Per the CVSS scenario this can also corrupt memory, and the client is blocklisted with MDS requests failing until remount.
Source: git.kernel.org
Which versions are affected by CVE-2026-99304?
Linux: version 2.6.34.
Source: cve.now feed data
Am I affected, and how do I check?
The issue is in the Linux kernel Ceph client (fs/ceph), in ceph_update_snap_trace(), when it handles snap traces from an MDS. It needs a malicious or compromised MDS, and the client needs no action to reach it. The facts list no version ranges. A reader can check whether the running kernel includes the Ceph client and whether it mounts CephFS, for example with uname -r and by looking for ceph mounts.
Source: git.kernel.org
How do I fix CVE-2026-99304?
The facts give no fixed versions or patch ids. Check the kernel vendor or distribution for an update that mentions this CVE and apply it when available.
Source: git.kernel.org
What if there's no patch?
The facts name no workaround. Since the trigger is a malicious or compromised MDS, the exposure can be limited by mounting CephFS only from metadata servers that are trusted and secured.
Source: git.kernel.org
Related
- CVE-2026-99795cxl/features: Ensure that count is set before access to ent[] __counted_by()
- CVE-2026-99794Bluetooth: L2CAP: Reject signalling responses in invalid states
- CVE-2026-99793Bluetooth: L2CAP: Only accept connection responses to outstanding requests
- CVE-2026-99792smb/server: prevent file publication after tree disconnect
- CVE-2026-99791xfs: improve dirent bounds checking in scrub and repair
- CVE-2026-99790NFSD: stop registering with rpcbind after a failure in listener_set
No corrections so far. Something wrong on this page? Report an error.