CVE-2026-53260

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — 3 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.8(high)
EPSS
26.9%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 30, 2026

Advisory Details (2)

Auto-updated Jun 30, 2026
No patch confirmed yet.
generic

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
generic

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

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.

Data Freshness Timeline

(refreshed 100× in last 7d / 134× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 134 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53260?
CVE-2026-53260 is a critical vulnerability 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 CVE-2026-53260 disclosed?
CVE-2026-53260 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53260 actively exploited?
CVE-2026-53260 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53260?
CVE-2026-53260 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-53260?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53260, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs