CVE-2026-53260

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-25. 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
Trending — 4 sources updated this week

Also known asEUVD-2026-39211 (ENISA EUVD) · GHSA-cmhx-q3fp-jhf6 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
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: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req().

syzbot reported a weird reqsk->rsk_refcnt underflow in __inet_csk_reqsk_queue_drop().

The captured reqsk_put() in __inet_csk_reqsk_queue_drop() is called only when it successfully removes reqsk from ehash.

Moreover, reqsk_timer_handler() calls another reqsk_put() after that.

This indicates that the reqsk was missing both refcnts for ehash and the timer itself.

Since all the syzbot reports had PREEMPT_RT enabled, the only possible scenario is that reqsk_queue_hash_req() is preempted after mod_timer() and before refcount_set(), and then the timer triggered after 1s aborts the reqsk due to its listener's close().

Let's wrap mod_timer() and refcount_set() with preempt_disable_nested() and preempt_enable_nested().

Note that inet_ehash_insert() holds the normal spin_lock() (mutex in PREEMPT_RT), so it must be called outside of preempt_disable_nested(), but this is fine.

The lookup path just ignores 0 sk_refcnt entries in ehash and tries to create another reqsk, but this will fail at inet_ehash_insert().

[0]: refcount_t: underflow; use-after-free. WARNING: lib/refcount.c:28 at refcount_warn_saturate+0xb2/0x110 lib/refcount.c:28, CPU#0: ktimers/0/16 Modules linked in: CPU: 0 UID: 0 PID: 16 Comm: ktimers/0 Tainted: G L syzkaller #0 PREEMPT_{RT,(full)} Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 RIP: 0010:refcount_warn_saturate+0xb2/0x110 lib/refcount.c:28 Code: e4 7d d1 0a 67 48 0f b9 3a eb 4a e8 38 3d 23 fd 48 8d 3d e1 7d d1 0a 67 48 0f b9 3a eb 37 e8 25 3d 23 fd 48 8d 3d de 7d d1 0a <67> 48 0f b9 3a eb 24 e8 12 3d 23 fd 48 8d 3d db 7d d1 0a 67 48 0f RSP: 0000:ffffc90000157948 EFLAGS: 00010246 RAX: ffffffff84a1301b RBX: 0000000000000003 RCX: ffff88801ca98000 RDX: 0000000000000100 RSI: 0000000000000000 RDI: ffffffff8f72ae00 RBP: ffffffff99ae3b01 R08: ffff88801ca98000 R09: 0000000000000005 R10: 0000000000000100 R11: 0000000000000004 R12: ffff8880425ef568 R13: ffff8880425ef4f8 R14: ffff8880425ef578 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff888126386000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7b46710e9c CR3: 000000000dbb6000 CR4: 00000000003526f0 Call Trace: __refcount_sub_and_test include/linux/refcount.h:400 [inline] __refcount_dec_and_test include/linux/refcount.h:432 [inline] refcount_dec_and_test include/linux/refcount.h:450 [inline] reqsk_put include/net/request_sock.h:136 [inline] __inet_csk_reqsk_queue_drop+0x3ce/0x440 net/ipv4/inet_connection_sock.c:1007 reqsk_timer_handler+0x651/0xdf0 net/ipv4/inet_connection_sock.c:1137 call_timer_fn+0x192/0x5e0 kernel/time/timer.c:1748 expire_timers kernel/time/timer.c:1799 [inline] __run_timers kernel/time/timer.c:2374 [inline] __run_timer_base+0x6a3/0x9f0 kernel/time/timer.c:2386 run_timer_base kernel/time/timer.c:2395 [inline] run_timer_softirq+0x67/0x170 kernel/time/timer.c:2403 handle_softirqs+0x1de/0x6d0 kernel/softirq.c:622 __do_softirq kernel/softirq.c:656 [inline] run_ktimerd+0x69/0x100 kernel/softirq.c:1151 smpboot_thread_fn+0x541/0xa50 kernel/smpboot.c:160 kthread+0x388/0x470 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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.3% × 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 total (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
21st
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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). 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: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: 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 total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 25, 2026

Last Modified

October 19, 2026

Advisory Details (4)

Auto-updated Oct 27, 2026
Patch available.
Web page

tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/889fc99967007e2493833515a645cb2d800f6742

Vendor Advisories for CVE-2026-53260(1)

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

Patch Availability(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-aws-edge (7.0.0-1010.10~24.04.1) @ noble2026-10-25ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-29.29) @ resolute2026-10-25ubuntu
ubuntulinux-tools-gke-hwe-26.04 (7.0.0-1005.6) @ resolute2026-10-25ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1033.33) @ noble2026-10-25ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1010.10) @ resolute2026-10-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1032.32) @ noble2026-10-25ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-29.29~24.04.2) @ noble2026-10-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-10-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-10-25ubuntu

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.12—
  • every version up to 6.12.100-1~deb12u1: fixed in 6.12.100-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (146 versions)
  • every version up to 7.0.13-1: fixed in 7.0.13-1
—

Weakness Classification(2)

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

All Vendor Advisories

(12)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 28× in last 7d / 80× 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 100 of 582 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. None are among the latest 100 rows. The 482 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53260?
CVE-2026-53260 is a critical-severity vulnerability; its CVE record was published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: tcp: Add preempt{disable,enable}nested() in reqskqueuehash_req(). syzbot reported a weird reqsk->rsk_refcnt underflow in inetcskreqskqueuedrop(). The captured reqskput() in inetcskreqskqueue_drop() is called only when it…
When was the CVE record for CVE-2026-53260 published?
The CVE record for CVE-2026-53260 was published on June 25, 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-53260 actively exploited?
CVE-2026-53260 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53260?
CVE-2026-53260 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-53260?
A fix for CVE-2026-53260 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53260 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-53260

Explore →

Is Your Infrastructure Affected by CVE-2026-53260?

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

Book a Demo →Browse All CVEs