CVE-2024-36904

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.6% (49th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2024-36255 (ENISA EUVD)Source: ENISA EUVD

7.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.6%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

tcp: Use refcount_inc_not_zero() in tcp_twsk_unique().

Anderson Nascimento reported a use-after-free splat in tcp_twsk_unique() with nice analysis.

Since commit ec94c2696f0b ("tcp/dccp: avoid one atomic operation for timewait hashdance"), inet_twsk_hashdance() sets TIME-WAIT socket's sk_refcnt after putting it into ehash and releasing the bucket lock.

Thus, there is a small race window where other threads could try to reuse the port during connect() and call sock_hold() in tcp_twsk_unique() for the TIME-WAIT socket with zero refcnt.

If that happens, the refcnt taken by tcp_twsk_unique() is overwritten and sock_put() will cause underflow, triggering a real use-after-free somewhere else.

To avoid the use-after-free, we need to use refcount_inc_not_zero() in tcp_twsk_unique() and give up on reusing the port if it returns false.

[0]: refcount_t: addition on 0; use-after-free. WARNING: CPU: 0 PID: 1039313 at lib/refcount.c:25 refcount_warn_saturate+0xe5/0x110 CPU: 0 PID: 1039313 Comm: trigger Not tainted 6.8.6-200.fc39.x86_64 #1 Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023 RIP: 0010:refcount_warn_saturate+0xe5/0x110 Code: 42 8e ff 0f 0b c3 cc cc cc cc 80 3d aa 13 ea 01 00 0f 85 5e ff ff ff 48 c7 c7 f8 8e b7 82 c6 05 96 13 ea 01 01 e8 7b 42 8e ff <0f> 0b c3 cc cc cc cc 48 c7 c7 50 8f b7 82 c6 05 7a 13 ea 01 01 e8 RSP: 0018:ffffc90006b43b60 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff888009bb3ef0 RCX: 0000000000000027 RDX: ffff88807be218c8 RSI: 0000000000000001 RDI: ffff88807be218c0 RBP: 0000000000069d70 R08: 0000000000000000 R09: ffffc90006b439f0 R10: ffffc90006b439e8 R11: 0000000000000003 R12: ffff8880029ede84 R13: 0000000000004e20 R14: ffffffff84356dc0 R15: ffff888009bb3ef0 FS: 00007f62c10926c0(0000) GS:ffff88807be00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020ccb000 CR3: 000000004628c005 CR4: 0000000000f70ef0 PKRU: 55555554 Call Trace: ? refcount_warn_saturate+0xe5/0x110 ? __warn+0x81/0x130 ? refcount_warn_saturate+0xe5/0x110 ? report_bug+0x171/0x1a0 ? refcount_warn_saturate+0xe5/0x110 ? handle_bug+0x3c/0x80 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? refcount_warn_saturate+0xe5/0x110 tcp_twsk_unique+0x186/0x190 __inet_check_established+0x176/0x2d0 __inet_hash_connect+0x74/0x7d0 ? __pfx___inet_check_established+0x10/0x10 tcp_v4_connect+0x278/0x530 __inet_stream_connect+0x10f/0x3d0 inet_stream_connect+0x3a/0x60 __sys_connect+0xa8/0xd0 __x64_sys_connect+0x18/0x20 do_syscall_64+0x83/0x170 entry_SYSCALL_64_after_hwframe+0x78/0x80 RIP: 0033:0x7f62c11a885d Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a3 45 0c 00 f7 d8 64 89 01 48 RSP: 002b:00007f62c1091e58 EFLAGS: 00000296 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 0000000020ccb004 RCX: 00007f62c11a885d RDX: 0000000000000010 RSI: 0000000020ccb000 RDI: 0000000000000003 RBP: 00007f62c1091e90 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000296 R12: 00007f62c10926c0 R13: ffffffffffffff88 R14: 0000000000000000 R15: 00007ffe237885b0

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.6%
EPSS %ILE
49th
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.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 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 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

May 30, 2024

Last Modified

October 15, 2026

Advisory Details (8)

Auto-updated Aug 4, 2026
Patch available.
Web page

tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1796ca9c6f5bd50554214053af5f47d112818ee3
Web page

tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13ed7cdf079686ccd3618335205700c03f6fb446
Web page

tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/84546cc1aeeb4df3e444b18a4293c9823f974be9
Web page

tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e48faad92be13166184d21506e4e54c79c13adc
Web page

tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/517e32ea0a8c72202d0d8aa8df50a7cd3d6fdefc
Web page

tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/27b0284d8be182a81feb65581ab6a724dfd596e8
Web page

tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d9cf07810c30ef7948879567d10fd1f01121d34

Vendor Advisories for CVE-2024-36904(7)

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

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1065.61) @ jammy2026-10-29ubuntu
ubuntulinux-tools-raspi (6.8.0-1009.10) @ noble2026-10-29ubuntu
ubuntulinux-tools-azure-lts-20.04 (5.4.0.1135.129) @ focal2026-10-29ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.118.128~20.04.1) @ focal2026-10-29ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1114.126~18.04.1) @ bionic2026-10-29ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-10-29ubuntu
ubuntulinux-tools-bluefield (5.4.0.1090.86) @ focal2026-10-29ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-40.40) @ noble2026-10-29ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1049 (5.4.0-1049.53) @ focal2026-10-29ubuntu
ubuntulinux-tools-azure (6.8.0-1012.14) @ noble2026-10-29ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1010.10) @ noble2026-10-29ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.118.118) @ jammy2026-10-29ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1060.58) @ jammy2026-10-29ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1010.10) @ noble2026-10-29ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1065.71~20.04.1) @ focal2026-10-29ubuntu
ubuntulinux-tools-oracle-lts-20.04 (5.4.0.1129.122) @ focal2026-10-29ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1070.68) @ jammy2026-10-29ubuntu
ubuntulinux-tools-azure-edge (5.4.0.1135.142~18.04.1) @ bionic2026-10-29ubuntu
redhatkernel-0:4.18.0-477.70.1.el8_82024-09-03redhat
redhatkernel-0:4.18.0-372.119.1.el8_62024-08-21redhat
redhatkernel-0:4.18.0-553.16.1.el8_102024-08-08redhat
redhatkernel-rt-0:4.18.0-553.16.1.rt7.357.el8_102024-08-08redhat
redhatkernel-rt-0:5.14.0-284.75.1.rt14.360.el9_22024-07-24redhat
redhatkernel-0:5.14.0-284.75.1.el9_22024-07-24redhat
redhatkernel-0:5.14.0-427.26.1.el9_42024-07-17redhat
linuxKernel @ 4.19.314 (fixes >=4.16.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

(6 across 5 ecosystems)
Debian:10(2)
PackageVulnerable rangeFix by version rangeDependents
linux4.19.118-1 ... 4.19.98-1~bpo9+1 (46 versions)
  • every version up to 4.19.316-1: fixed in 4.19.316-1
—
linux-5.105.10.136-1~deb10u1 ... 5.10.216-1~deb10u1 (14 versions)
  • every version up to 5.10.218-1~deb10u1: fixed in 5.10.218-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (40 versions)
  • every version up to 5.10.218-1: fixed in 5.10.218-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.94-1~bpo11+1 (23 versions)
  • every version up to 6.1.94-1: fixed in 6.1.94-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.11-1: fixed in 6.8.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.11-1: fixed in 6.8.11-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(18)

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 9× in last 7d / 42× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 96 of 243 refreshes 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 147 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  6. 2026-10-29 16:02 UTCEG score recompute
  7. 2026-10-29 16:02 UTCVendor advisory
  8. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  9. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  10. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  11. 2026-10-25 17:08 UTCEG score recompute
  12. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  13. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-22 08:55 UTCEG score recompute
  17. 2026-10-22 08:55 UTCVendor advisory
  18. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  21. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  22. 2026-10-18 07:12 UTCEG score recompute
  23. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  24. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  25. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
Show 71 more
  1. 2026-10-15 01:46 UTCVendor advisory
  2. 2026-10-15 01:09 UTCEG score recompute
  3. 2026-10-15 01:09 UTCVendor advisory
  4. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-12 17:51 UTCEG score recompute
  7. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  8. 2026-10-11 21:16 UTCEG score recompute
  9. 2026-10-11 16:09 UTCEG score recompute
  10. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  13. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  14. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  16. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  17. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  18. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  19. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-09-30 19:47 UTCEG score recompute
  21. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  22. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-09-27 00:12 UTCOSV refresh
  26. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  27. 2026-09-26 00:23 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  28. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  29. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  30. 2026-09-22 14:46 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  31. 2026-09-21 20:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  32. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  33. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  34. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  35. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  36. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  37. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  38. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  39. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  40. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  41. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  42. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  43. 2026-09-07 09:48 UTCOSV refresh
  44. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  45. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  46. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  47. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  48. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  49. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  50. 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  51. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  52. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  53. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  54. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  55. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  56. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  57. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  58. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  59. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  60. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  61. 2026-08-20 19:31 UTCOSV refresh
  62. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  63. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  64. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  65. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  66. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  67. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  68. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  69. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  70. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  71. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.6% · 45th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-36904?
CVE-2024-36904 is a high-severity vulnerability; its CVE record was published on May 30, 2024. In the Linux kernel, the following vulnerability has been resolved: tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). Anderson Nascimento reported a use-after-free splat in tcp_twsk_unique() with nice analysis. Since commit ec94c2696f0b ("tcp/dccp: avoid one atomic operation for timewait…
When was the CVE record for CVE-2024-36904 published?
The CVE record for CVE-2024-36904 was published on May 30, 2024. 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 15, 2026; the record at its source may have been updated since.
Is CVE-2024-36904 actively exploited?
CVE-2024-36904 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-36904?
CVE-2024-36904 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-36904?
A fix for CVE-2024-36904 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-36904 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-2024-36904

Explore →

Is Your Infrastructure Affected by CVE-2024-36904?

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

Book a Demo →Browse All CVEs