CVE-2026-23113

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory (severity: MODERATE) published 2026-02-14. NVD baseline CVSS 5.5; 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-6115 (ENISA EUVD) · GHSA-ccr5-8c2w-j2f4 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop

Currently this is checked before running the pending work. Normally this is quite fine, as work items either end up blocking (which will create a new worker for other items), or they complete fairly quickly. But syzbot reports an issue where io-wq takes seemingly forever to exit, and with a bit of debugging, this turns out to be because it queues a bunch of big (2GB - 4096b) reads with a /dev/msr* file. Since this file type doesn't support ->read_iter(), loop_rw_iter() ends up handling them. Each read returns 16MB of data read, which takes 20 (!!) seconds. With a bunch of these pending, processing the whole chain can take a long time. Easily longer than the syzbot uninterruptible sleep timeout of 140 seconds. This then triggers a complaint off the io-wq exit path:

INFO: task syz.4.135:6326 blocked for more than 143 seconds. Not tainted syzkaller #0 Blocked by coredump. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz.4.135 state:D stack:26824 pid:6326 tgid:6324 ppid:5957 task_flags:0x400548 flags:0x00080000 Call Trace: context_switch kernel/sched/core.c:5256 [inline] __schedule+0x1139/0x6150 kernel/sched/core.c:6863 __schedule_loop kernel/sched/core.c:6945 [inline] schedule+0xe7/0x3a0 kernel/sched/core.c:6960 schedule_timeout+0x257/0x290 kernel/time/sleep_timeout.c:75 do_wait_for_common kernel/sched/completion.c:100 [inline] __wait_for_common+0x2fc/0x4e0 kernel/sched/completion.c:121 io_wq_exit_workers io_uring/io-wq.c:1328 [inline] io_wq_put_and_exit+0x271/0x8a0 io_uring/io-wq.c:1356 io_uring_clean_tctx+0x10d/0x190 io_uring/tctx.c:203 io_uring_cancel_generic+0x69c/0x9a0 io_uring/cancel.c:651 io_uring_files_cancel include/linux/io_uring.h:19 [inline] do_exit+0x2ce/0x2bd0 kernel/exit.c:911 do_group_exit+0xd3/0x2a0 kernel/exit.c:1112 get_signal+0x2671/0x26d0 kernel/signal.c:3034 arch_do_signal_or_restart+0x8f/0x7e0 arch/x86/kernel/signal.c:337 __exit_to_user_mode_loop kernel/entry/common.c:41 [inline] exit_to_user_mode_loop+0x8c/0x540 kernel/entry/common.c:75 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline] syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:159 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:194 [inline] do_syscall_64+0x4ee/0xf80 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fa02738f749 RSP: 002b:00007fa0281ae0e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca RAX: fffffffffffffe00 RBX: 00007fa0275e6098 RCX: 00007fa02738f749 RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007fa0275e6098 RBP: 00007fa0275e6090 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fa0275e6128 R14: 00007fff14e4fcb0 R15: 00007fff14e4fd98

There's really nothing wrong here, outside of processing these reads will take a LONG time. However, we can speed up the exit by checking the IO_WQ_BIT_EXIT inside the io_worker_handle_work() loop, as syzbot will exit the ring after queueing up all of these reads. Then once the first item is processed, io-wq will simply cancel the rest. That should avoid syzbot running into this complaint again.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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 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.1%
EPSS %ILE
3rd
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-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-11-05). 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

February 14, 2026

Last Modified

November 5, 2026

Advisory Details (8)

Auto-updated Jul 17, 2026
Patch available.
Web page

SSA-082556

https://cert-portal.siemens.com/productcert/html/ssa-082556.html
Web page

SSA-019113

https://cert-portal.siemens.com/productcert/html/ssa-019113.html
Web page

io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/85eb83694a91c89d9abe615d717c0053c3efa714
Web page

io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e8ca1078b14142db2ce51cbd18ff9971560046b
Web page

io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10dc959398175736e495f71c771f8641e1ca1907

Vendor Advisories for CVE-2026-23113(2)

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

Patch Availability(29)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-10-15ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1030.30) @ noble2026-10-15ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-10-15ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-10-15ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1019.19~24.04.3+1) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-10-15ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-10-15ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1031.31) @ noble2026-10-15ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-10-15ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.17.0-1018.20~24.04.1) @ noble2026-10-15ubuntu
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-10-15ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-10-15ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1106.104) @ jammy2026-10-15ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-10-15ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.186.196~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-10-15ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-10-15ubuntu
linuxKernel @ 5.15.203 (fixes >=5.12.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
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)
  • every version up to 6.1.170-1~deb11u1: fixed in 6.1.170-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)
  • every version up to 6.12.69-1: fixed in 6.12.69-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (97 versions)
  • every version up to 6.18.8-1: fixed in 6.18.8-1
—

Additional Vendor Advisories

(24)

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 12× in last 7d / 46× 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 99 of 250 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 151 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-23113?
CVE-2026-23113 is a medium-severity vulnerability; its CVE record was published on February 14, 2026. In the Linux kernel, the following vulnerability has been resolved: io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop Currently this is checked before running the pending work. Normally this is quite fine, as work items either end up blocking (which will create a new worker for other…
When was the CVE record for CVE-2026-23113 published?
The CVE record for CVE-2026-23113 was published on February 14, 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 November 5, 2026; the record at its source may have been updated since.
Is CVE-2026-23113 actively exploited?
CVE-2026-23113 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23113?
CVE-2026-23113 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23113?
A fix for CVE-2026-23113 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-23113 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-23113

Explore →

Is Your Infrastructure Affected by CVE-2026-23113?

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

Book a Demo →Browse All CVEs