CVE-2026-45957

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

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, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-32241 (ENISA EUVD) · GHSA-hmgm-22hx-5rp9 (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
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.1%CVSS: 7.1Exploit: None knownExposed services: Not assessed

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.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.1%
EPSS %ILE
2nd
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.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

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

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

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 27, 2026

Last Modified

October 30, 2026

Advisory Details (5)

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

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
Web page

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
Web page

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
Web page

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
Web page

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(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-10-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-10-30ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-134.134.1~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-10-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-10-30ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-10-30ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-10-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-30ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-10-30ubuntu
linuxKernel @ 6.6.128 (fixes >=5.8.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (104 versions)
  • every version up to 6.18.14-1: fixed in 6.18.14-1
—

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 / 44× 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 278 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 178 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-45957?
CVE-2026-45957 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-45957 published?
The CVE record for CVE-2026-45957 was published on May 27, 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 30, 2026; the record at its source may have been updated since.
Is CVE-2026-45957 actively exploited?
CVE-2026-45957 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-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?
A fix for CVE-2026-45957 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45957 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-45957

Explore →

Is Your Infrastructure Affected by CVE-2026-45957?

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

Book a Demo →Browse All CVEs