CVE-2026-45957

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

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

rcu: Fix rcu_read_unlock() deadloop due to softirq

Commit 5f5fa7ea89dc ("rcu: Don't use negative nesting depth in __rcu_read_unlock()") removes the recursion-protection code from __rcu_read_unlock(). Therefore, we could invoke the deadloop in raise_softirq_irqoff() with ftrace enabled as follows:

WARNING: CPU: 0 PID: 0 at kernel/trace/trace.c:3021 __ftrace_trace_stack.constprop.0+0x172/0x180 Modules linked in: my_irq_work(O) CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Tainted: G O 6.18.0-rc7-dirty #23 PREEMPT(full) Tainted: [O]=OOT_MODULE Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:__ftrace_trace_stack.constprop.0+0x172/0x180 RSP: 0018:ffffc900000034a8 EFLAGS: 00010002 RAX: 0000000000000000 RBX: 0000000000000004 RCX: 0000000000000000 RDX: 0000000000000003 RSI: ffffffff826d7b87 RDI: ffffffff826e9329 RBP: 0000000000090009 R08: 0000000000000005 R09: ffffffff82afbc4c R10: 0000000000000008 R11: 0000000000011d7a R12: 0000000000000000 R13: ffff888003874100 R14: 0000000000000003 R15: ffff8880038c1054 FS: 0000000000000000(0000) GS:ffff8880fa8ea000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055b31fa7f540 CR3: 00000000078f4005 CR4: 0000000000770ef0 PKRU: 55555554 Call Trace: trace_buffer_unlock_commit_regs+0x6d/0x220 trace_event_buffer_commit+0x5c/0x260 trace_event_raw_event_softirq+0x47/0x80 raise_softirq_irqoff+0x6e/0xa0 rcu_read_unlock_special+0xb1/0x160 unwind_next_frame+0x203/0x9b0 __unwind_start+0x15d/0x1c0 arch_stack_walk+0x62/0xf0 stack_trace_save+0x48/0x70 __ftrace_trace_stack.constprop.0+0x144/0x180 trace_buffer_unlock_commit_regs+0x6d/0x220 trace_event_buffer_commit+0x5c/0x260 trace_event_raw_event_softirq+0x47/0x80 raise_softirq_irqoff+0x6e/0xa0 rcu_read_unlock_special+0xb1/0x160 unwind_next_frame+0x203/0x9b0 __unwind_start+0x15d/0x1c0 arch_stack_walk+0x62/0xf0 stack_trace_save+0x48/0x70 __ftrace_trace_stack.constprop.0+0x144/0x180 trace_buffer_unlock_commit_regs+0x6d/0x220 trace_event_buffer_commit+0x5c/0x260 trace_event_raw_event_softirq+0x47/0x80 raise_softirq_irqoff+0x6e/0xa0 rcu_read_unlock_special+0xb1/0x160 unwind_next_frame+0x203/0x9b0 __unwind_start+0x15d/0x1c0 arch_stack_walk+0x62/0xf0 stack_trace_save+0x48/0x70 __ftrace_trace_stack.constprop.0+0x144/0x180 trace_buffer_unlock_commit_regs+0x6d/0x220 trace_event_buffer_commit+0x5c/0x260 trace_event_raw_event_softirq+0x47/0x80 raise_softirq_irqoff+0x6e/0xa0 rcu_read_unlock_special+0xb1/0x160 __is_insn_slot_addr+0x54/0x70 kernel_text_address+0x48/0xc0 __kernel_text_address+0xd/0x40 unwind_get_return_address+0x1e/0x40 arch_stack_walk+0x9c/0xf0 stack_trace_save+0x48/0x70 __ftrace_trace_stack.constprop.0+0x144/0x180 trace_buffer_unlock_commit_regs+0x6d/0x220 trace_event_buffer_commit+0x5c/0x260 trace_event_raw_event_softirq+0x47/0x80 __raise_softirq_irqoff+0x61/0x80 __flush_smp_call_function_queue+0x115/0x420 __sysvec_call_function_single+0x17/0xb0 sysvec_call_function_single+0x8c/0xc0

Commit b41642c87716 ("rcu: Fix rcu_read_unlock() deadloop due to IRQ work") fixed the infinite loop in rcu_read_unlock_special() for IRQ work by setting a flag before calling irq_work_queue_on(). We fix this issue by setting the same flag before calling raise_softirq_irqoff() and rename the flag to defer_qs_pending for more common.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (5)

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

rcu: Fix rcu_read_unlock() deadloop due to softirq - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d41e37f26b3157b3f1d10223863519a943aa239b
generic

rcu: Fix rcu_read_unlock() deadloop due to softirq - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c2932e16d8c354404b17123e64daa8e33191e145
generic

rcu: Fix rcu_read_unlock() deadloop due to softirq - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/979c708e6c9d7fc461daef2dad8b45f22e23464c
generic

rcu: Fix rcu_read_unlock() deadloop due to softirq - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4a4a6e12c9c829be3f74b7206fa8640fc4e1c566
generic

rcu: Fix rcu_read_unlock() deadloop due to softirq - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-45957(1)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-07-12ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1057.58~22.04.1) @ jammy2026-07-12ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-07-12ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-07-12ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-07-12ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-07-12ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-07-12ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-07-12ubuntu

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.

Weakness Classification(1)

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 14× in last 7d / 37× 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 110 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-45957?
CVE-2026-45957 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcureadunlock() deadloop due to softirq Commit 5f5fa7ea89dc ("rcu: Don't use negative nesting depth in rcureadunlock()") removes the recursion-protection code from rcureadunlock(). Therefore, we could invoke the deadloop…
When was CVE-2026-45957 disclosed?
CVE-2026-45957 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45957 actively exploited?
CVE-2026-45957 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-45957?
CVE-2026-45957 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-45957?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45957, 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-45957

Explore →

Is Your Infrastructure Affected by CVE-2026-45957?

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

Start Free Scan →Browse All CVEs