CVE-2026-99304 ceph: fix integer overflow in the snap trace bounds check
linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
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)
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-16. A forecast for this CVE across the internet, not for your own systems.
- Published
- Assigned by
- Linux (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Fix and patched versions
- Linux Linux: fixed in 6.12.117
- Linux Linux: fixed in 6.18.63
- Linux Linux: fixed in 7.3.4
- Linux Linux: fixed in 7.4-rc1
- Debian: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-99304 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99304?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99304?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-99304 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 2.6.34 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.12 | 6.12.117 |
| Linux | 6.18 | 6.18.63 |
| Linux | 7.3 | 7.3.4 |
| Linux | later releases | 7.4-rc1 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 14 | linux | no fix listed | DEBIAN-CVE-2026-99304 |
| Debian | 13 | linux | 6.12.117-1 | DEBIAN-CVE-2026-99304 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-99304 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-99304 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-99304 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 57 more | no fix listed | UBUNTU-CVE-2026-99304 |
| Ubuntu | 24.04:LTS | linux, linux-aws, linux-gcp and 50 more | no fix listed | UBUNTU-CVE-2026-99304 |
| Ubuntu | 26.04:LTS | linux, linux-aws, linux-gcp and 12 more | no fix listed | UBUNTU-CVE-2026-99304 |
| Ubuntu | 26.10 | linux, linux-aws, linux-gcp and 6 more | no fix listed | UBUNTU-CVE-2026-99304 |
| Ubuntu | Nvidia-BlueField:22.04:LTS, Nvidia-BlueField:24.04:LTS | linux-bluefield | no fix listed | UBUNTU-CVE-2026-99304 |
| Ubuntu | Pro:14.04:LTS | linux, linux-aws, linux-azure and 1 more | no fix listed | UBUNTU-CVE-2026-99304 |
| Ubuntu | Pro:16.04:LTS | linux, linux-aws, linux-gcp and 5 more | no fix listed | UBUNTU-CVE-2026-99304 |
| Ubuntu | Pro:18.04:LTS | linux, linux-aws, linux-kvm and 10 more | no fix listed | UBUNTU-CVE-2026-99304 |
| Ubuntu | Pro:20.04:LTS | linux, linux-aws, linux-gcp and 19 more | no fix listed | UBUNTU-CVE-2026-99304 |
| 4 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.