CVE-2026-99304

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-11-16. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-126210 (ENISA EUVD) · GHSA-gwm4-f7gj-p7vj (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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)

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 16, 2026

Last Modified

November 19, 2026

Advisory Details (4)

Auto-updated Nov 19, 2026
Patch available.
Web page

ceph: fix integer overflow in the snap trace bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f0dbd6b9b05e919ebab668f3479aebbcd2431fce
Web page

ceph: fix integer overflow in the snap trace bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bf8f13872959af1d87e36b7d27096a09fdcf6e47
Web page

ceph: fix integer overflow in the snap trace bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b3bf89767e3ca9506f1c7167cac97c41ec254d42
Web page

ceph: fix integer overflow in the snap trace bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25ae51760b751d170e29425b7851ee577e2cd5ba

Vendor Advisories for CVE-2026-99304(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.12.117 (fixes >=2.6.34)—osv

These rows come from OSV. Multiple rows for the same upstream release have been deduplicated.

Data Freshness Timeline

(refreshed 18× in last 7d / 18× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-22 10:32 UTCEchelonGraph re-scored
  2. 2026-11-22 10:32 UTCVendor advisory
  3. 2026-11-22 10:32 UTCGHSA enrichmentGHSA-gwm4-f7gj-p7vj · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-11-21 11:51 UTCEchelonGraph re-scored
  6. 2026-11-21 11:51 UTCGHSA enrichmentGHSA-gwm4-f7gj-p7vj · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-11-20 13:12 UTCEchelonGraph re-scored
  9. 2026-11-20 13:12 UTCVendor advisory
  10. 2026-11-20 13:12 UTCGHSA enrichmentGHSA-gwm4-f7gj-p7vj · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-11-19 14:29 UTCEchelonGraph re-scored
  13. 2026-11-19 14:29 UTCGHSA enrichmentGHSA-gwm4-f7gj-p7vj
  14. 2026-11-19 14:26 UTCOSV refresh
  15. 2026-11-19 13:58 UTCEchelonGraph re-scoredFirst assessed: 9.8 CRITICAL
  16. 2026-11-19 13:58 UTCGHSA enrichmentGHSA-gwm4-f7gj-p7vj
  17. 2026-11-19 13:57 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  18. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-11-17 19:43 UTCEchelonGraph re-scored
  20. 2026-11-17 19:43 UTCGHSA enrichmentGHSA-gwm4-f7gj-p7vj
  21. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-11-16 16:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  23. 2026-11-16 11:02 UTCENISA EUVD ID recordedEUVD-2026-126210 · Source: ENISA EUVD
  24. 2026-11-16 10:09 UTCEchelonGraph re-scored
  25. 2026-11-16 10:04 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-99304?
CVE-2026-99304 is a critical-severity vulnerability; its CVE record was published on November 16, 2026. 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…
When was the CVE record for CVE-2026-99304 published?
The CVE record for CVE-2026-99304 was published on November 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 19, 2026; the record at its source may have been updated since.
Is CVE-2026-99304 actively exploited?
CVE-2026-99304 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-99304?
CVE-2026-99304 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-99304?
A fix for CVE-2026-99304 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-99304 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-99304

Explore →

Is Your Infrastructure Affected by CVE-2026-99304?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.