CVE-2026-46304

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-08. A secondary CVSS source baseline 7.5; sources differ by 0.0.

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

Also known asEUVD-2026-35169 (ENISA EUVD) · GHSA-jrgh-545x-2m82 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free

nvmet_tcp_release_queue_work() runs on nvmet-wq and can drop the final controller reference through nvmet_cq_put(). If that triggers nvmet_ctrl_free(), the teardown path flushes ctrl->async_event_work on the same nvmet-wq.

Call chain:

nvmet_tcp_schedule_release_queue() kref_put(&queue->kref, nvmet_tcp_release_queue) nvmet_tcp_release_queue() queue_work(nvmet_wq, &queue->release_work) <--- nvmet_wq process_one_work() nvmet_tcp_release_queue_work() nvmet_cq_put(&queue->nvme_cq) nvmet_cq_destroy() nvmet_ctrl_put(cq->ctrl) nvmet_ctrl_free() flush_work(&ctrl->async_event_work) <--- nvmet_wq

Previously Scheduled by :- nvmet_add_async_event queue_work(nvmet_wq, &ctrl->async_event_work);

This trips lockdep with a possible recursive locking warning.

[ 5223.015876] run blktests nvme/003 at 2026-04-07 20:53:55 [ 5223.061801] loop0: detected capacity change from 0 to 2097152 [ 5223.072206] nvmet: adding nsid 1 to subsystem blktests-subsystem-1 [ 5223.088368] nvmet_tcp: enabling port 0 (127.0.0.1:4420) [ 5223.126086] nvmet: Created discovery controller 1 for subsystem nqn.2014-08.org.nvmexpress.discovery for NQN nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349. [ 5223.128453] nvme nvme1: new ctrl: NQN "nqn.2014-08.org.nvmexpress.discovery", addr 127.0.0.1:4420, hostnqn: nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349 [ 5233.199447] nvme nvme1: Removing ctrl: NQN "nqn.2014-08.org.nvmexpress.discovery"

[ 5233.227718] ============================================ [ 5233.231283] WARNING: possible recursive locking detected [ 5233.234696] 7.0.0-rc3nvme+ #20 Tainted: G O N [ 5233.238434] -------------------------------------------- [ 5233.241852] kworker/u192:6/2413 is trying to acquire lock: [ 5233.245429] ffff888111632548 ((wq_completion)nvmet-wq){+.+.}-{0:0}, at: touch_wq_lockdep_map+0x26/0x90 [ 5233.251438] but task is already holding lock: [ 5233.255254] ffff888111632548 ((wq_completion)nvmet-wq){+.+.}-{0:0}, at: process_one_work+0x5cc/0x6e0 [ 5233.261125] other info that might help us debug this: [ 5233.265333] Possible unsafe locking scenario:

[ 5233.269217] CPU0 [ 5233.270795] ---- [ 5233.272436] lock((wq_completion)nvmet-wq); [ 5233.275241] lock((wq_completion)nvmet-wq); [ 5233.278020] * DEADLOCK *

[ 5233.281793] May be due to missing lock nesting notation

[ 5233.286195] 3 locks held by kworker/u192:6/2413: [ 5233.289192] #0: ffff888111632548 ((wq_completion)nvmet-wq){+.+.}-{0:0}, at: process_one_work+0x5cc/0x6e0 [ 5233.294569] #1: ffffc9000e2a7e40 ((work_completion)(&queue->release_work)){+.+.}-{0:0}, at: process_one_work+0x1c5/0x6e0 [ 5233.300128] #2: ffffffff82d7dc40 (rcu_read_lock){....}-{1:3}, at: __flush_work+0x62/0x530 [ 5233.304290] stack backtrace: [ 5233.306520] CPU: 4 UID: 0 PID: 2413 Comm: kworker/u192:6 Tainted: G O N 7.0.0-rc3nvme+ #20 PREEMPT(full) [ 5233.306524] Tainted: [O]=OOT_MODULE, [N]=TEST [ 5233.306525] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014 [ 5233.306527] Workqueue: nvmet-wq nvmet_tcp_release_queue_work [nvmet_tcp] [ 5233.306532] Call Trace: [ 5233.306534] [ 5233.306536] dump_stack_lvl+0x73/0xb0 [ 5233.306552] print_deadlock_bug+0x225/0x2f0 [ 5233.306556] __lock_acquire+0x13f0/0x2290 [ 5233.306563] lock_acquire+0xd0/0x300 [ 5233.306565] ? touch_wq_lockdep_map+0x26/0x90 [ 5233.306571] ? __flush_work+0x20b/0x530 [ 5233.306573] ? touch_wq_lockdep_map+0x26/0x90 [ 5233.306577] touch_wq_lockdep_map+0x3b/0x90 [ 5233.306580] ? touch_wq_lockdep_map+0x26/0x90 [ 52 ---truncated---

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
28th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

June 8, 2026

Last Modified

October 19, 2026

Advisory Details (8)

Auto-updated Jun 14, 2026
Patch available.
Web page

nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a4d7222c0955b221e38bb66d10e6bccb672c8a1
Web page

nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8d66ba89480ff098a58d79003a505f383aa4e920
Web page

nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/781f47d641432c26c19625b2cdd7f40825097592
Web page

nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/551f445a56a11a6457550cddcf39c9ebb8bcacc6

Vendor Advisories for CVE-2026-46304(2)

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

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-10-27ubuntu
ubuntuoracle (6.8.0-1005) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1106.104) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-27ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-10-27ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-ibm-edge (6.8.0-1061.62~22.04.1) @ jammy2026-10-27ubuntu
linuxKernel @ 5.10.258 (fixes >=4.10.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)
  • every version up to 5.10.259-1: fixed in 5.10.259-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.88-1~bpo12+1 (21 versions)
  • every version up to 6.12.88-1: fixed in 6.12.88-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (138 versions)
  • every version up to 7.0.7-1: fixed in 7.0.7-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 45× 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.

Showing the most recent 100 of 391 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 291 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:52 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  3. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  4. 2026-11-10 17:30 UTCEchelonGraph re-scored
  5. 2026-11-10 17:30 UTCGHSA enrichmentGHSA-jrgh-545x-2m82 · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  7. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  8. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  9. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  10. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  11. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  12. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  13. 2026-11-03 18:47 UTCEchelonGraph re-scored
  14. 2026-11-03 18:47 UTCVendor advisory
  15. 2026-11-03 18:47 UTCGHSA enrichmentGHSA-jrgh-545x-2m82 · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  17. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  18. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  19. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  20. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  21. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  22. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  23. 2026-10-27 18:44 UTCEchelonGraph re-scored
  24. 2026-10-27 18:44 UTCVendor advisory
  25. 2026-10-27 18:43 UTCGHSA enrichmentGHSA-jrgh-545x-2m82 · GitHub severity HIGH · GitHub CVSS 7.5
Show 75 more
  1. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  2. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  3. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  4. 2026-10-25 14:25 UTCEchelonGraph re-scored
  5. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  6. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  7. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  8. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  9. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  10. 2026-10-19 20:42 UTCEchelonGraph re-scored
  11. 2026-10-19 20:42 UTCVendor advisory
  12. 2026-10-19 20:41 UTCGHSA enrichmentGHSA-jrgh-545x-2m82 · GitHub severity HIGH · GitHub CVSS 7.5
  13. 2026-10-19 20:10 UTCEchelonGraph re-scored
  14. 2026-10-19 20:10 UTCVendor advisory
  15. 2026-10-19 20:09 UTCGHSA enrichmentGHSA-jrgh-545x-2m82 · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-10-18 03:37 UTCEchelonGraph re-scored
  19. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  20. 2026-10-16 17:27 UTCEchelonGraph re-scored
  21. 2026-10-16 17:27 UTCVendor advisory
  22. 2026-10-16 17:26 UTCGHSA enrichmentGHSA-jrgh-545x-2m82 · GitHub severity HIGH · GitHub CVSS 7.5
  23. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-10-16 15:58 UTCEchelonGraph re-scored
  25. 2026-10-16 15:58 UTCVendor advisory
  26. 2026-10-16 15:57 UTCGHSA enrichmentGHSA-jrgh-545x-2m82 · GitHub severity HIGH · GitHub CVSS 7.5
  27. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  28. 2026-10-15 02:31 UTCEchelonGraph re-scored
  29. 2026-10-15 02:31 UTCGHSA enrichmentGHSA-jrgh-545x-2m82 · GitHub severity HIGH · GitHub CVSS 7.5
  30. 2026-10-15 01:35 UTCEchelonGraph re-scored
  31. 2026-10-15 01:34 UTCGHSA enrichmentGHSA-jrgh-545x-2m82 · GitHub severity HIGH · GitHub CVSS 7.5
  32. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  33. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  34. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  35. 2026-10-12 16:03 UTCEchelonGraph re-scored
  36. 2026-10-11 19:45 UTCEchelonGraph re-scored
  37. 2026-10-11 17:00 UTCEchelonGraph re-scored
  38. 2026-10-11 14:25 UTCEchelonGraph re-scored
  39. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  40. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  41. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  42. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  43. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  44. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  45. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  46. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  47. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  48. 2026-10-03 10:39 UTCOSV refresh
  49. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  50. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  51. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  52. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  53. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  54. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  55. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  56. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  57. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  58. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  59. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  60. 2026-09-14 04:49 UTCEchelonGraph re-scored
  61. 2026-09-14 04:49 UTCVendor advisory
  62. 2026-09-14 04:49 UTCGHSA enrichmentGHSA-jrgh-545x-2m82 · GitHub severity HIGH · GitHub CVSS 7.5
  63. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  64. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  65. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  66. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  67. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  68. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  69. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  70. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  71. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  72. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  73. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  74. 2026-08-31 01:54 UTCEchelonGraph re-scored
  75. 2026-08-31 01:54 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-46304?
CVE-2026-46304 is a high-severity vulnerability; its CVE record was published on June 8, 2026. In the Linux kernel, the following vulnerability has been resolved: nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free nvmet_tcp_release_queue_work() runs on nvmet-wq and can drop the final controller reference through nvmet_cq_put(). If that triggers nvmet_ctrl_free(), the teardown path…
When was the CVE record for CVE-2026-46304 published?
The CVE record for CVE-2026-46304 was published on June 8, 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-46304 actively exploited?
CVE-2026-46304 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46304?
CVE-2026-46304 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46304?
A fix for CVE-2026-46304 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46304 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46304

Explore →

Is Your Infrastructure Affected by CVE-2026-46304?

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

Book a Demo →Browse All CVEs