MediumCVE-2026-23113

    Linux Kernel: security vulnerability (CVE-2026-23113)

    Published Last modified Sources: Ubuntu, Siemens ProductCERT, Debian LTS, Debian, SUSE, BSI, CVE.org, Msrc Update Guide, EUVD

    Share

    What is affected, what to do

    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.

    Update Linux Kernel to version 5.15.203, Linux Kernel to version 6.1.167, Linux Kernel to version 6.6.122.

    Affected
    • Linux Kernel lt 5.12..5.15.203
    • Linux Kernel lt 5.16..6.1.167
    • Linux Kernel lt 6.2..6.6.122
    • Linux Kernel lt 6.7..6.12.68
    • Linux Kernel lt 6.13..6.18.8
    Fixed in
    • Linux Kernel 5.15.203
    • Linux Kernel 6.1.167
    • Linux Kernel 6.6.122
    • Linux Kernel 6.12.68
    • Linux Kernel 6.18.8
    • Linux Kernel 6.19

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    5.5

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    5.5

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: Ubuntu, Siemens ProductCERT, Debian LTS, Debian, SUSE, BSI, CVE.org, Msrc Update Guide, EUVD

    0.1 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 3.7

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    41.77 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    5.5 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    5.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.1 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    3.7
    Low — this CVE sits in the lower 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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: <TASK> 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.

    Source: Ubuntu Security Notices, siemens_advisory, Debian LTS Advisories, Debian Security Advisories, suse_csaf, BSI WID Portal, BSI CSAF, cvelistv5, NVD (NIST), Microsoft Security Update Guide, CVE.org (MITRE), ENISA EUVD

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    LinuxLinux
    • 6.13 – < 6.18.8
    • 6.2 – < 6.6.122
    • —
    • 5.12 – < 5.15.203
    • 5.16 – < 6.1.167
    • 6.7 – < 6.12.68
    • 6.18.8
    • 6.6.122
    • 6.19
    • 5.15.203
    • 6.1.167
    • 6.12.68
    IBMQRadar SIEM
    • <7.5.0 UP15 IF02
    • —
    SiemensSIMATIC S7
    • 1500 TM MFP V1.1.1 GNU/Linux subsystem
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianlinuxbookworm
    Linuxdebianlinux-6.1bullseye
    Linuxlinuxlinux_kernel5.12
    Linuxlinuxlinux_kernel6.19
    Linuxlinuxlinux_kernel—

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedLinux

      Show 16 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://git.kernel.org/stable/c/10dc959398175736e495f71c771f8641e1ca1907
      Referenceadded
      —
      https://git.kernel.org/stable/c/27e47500fac23d15b7dc93ff650bc4844d2581bd
      Referenceadded
      —
      https://git.kernel.org/stable/c/2e8ca1078b14142db2ce51cbd18ff9971560046b
      Referenceadded
      —
      https://git.kernel.org/stable/c/85eb83694a91c89d9abe615d717c0053c3efa714
      Referenceadded
      —
      https://git.kernel.org/stable/c/bdf0bf73006ea8af9327cdb85cfdff4c23a5f966
      Referenceadded
      —
      https://git.kernel.org/stable/c/d05d99573f81a091547b1778b9a50120f5d6c68a
      Referenceremoved
      https://git.kernel.org/stable/c/10dc959398175736e495f71c771f8641e1ca1907
      —
      Referenceremoved
      https://git.kernel.org/stable/c/27e47500fac23d15b7dc93ff650bc4844d2581bd
      —
      Referenceremoved
      https://git.kernel.org/stable/c/2e8ca1078b14142db2ce51cbd18ff9971560046b
      —
      Referenceremoved
      https://git.kernel.org/stable/c/85eb83694a91c89d9abe615d717c0053c3efa714
      —
      Referenceremoved
      https://git.kernel.org/stable/c/bdf0bf73006ea8af9327cdb85cfdff4c23a5f966
      —
      Referenceremoved
      https://git.kernel.org/stable/c/d05d99573f81a091547b1778b9a50120f5d6c68a
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/10dc959398175736e495f71c771f8641e1ca1907 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/2e8ca1078b14142db2ce51cbd18ff9971560046b Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/85eb83694a91c89d9abe615d717c0053c3efa714 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/bdf0bf73006ea8af9327cdb85cfdff4c23a5f966 Types: Patch
      —

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    2. Record modifiedSiemens ADP

      Show 7 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)added
      —
      Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/23xxx/CVE-2026-23113.json">CVE-2026-23113</a>
      Referenceadded
      —
      https://cert-portal.siemens.com/productcert/html/ssa-019113.html
      Referenceadded
      —
      https://cert-portal.siemens.com/productcert/html/ssa-082556.html
      Referenceadded
      —
      https://cert-portal.siemens.com/productcert/html/ssa-457936.html
      Referenceadded
      —
      https://cert-portal.siemens.com/productcert/html/ssa-784472.html
      Referenceremoved
      https://cert-portal.siemens.com/productcert/html/ssa-019113.html
      —
      Referenceremoved
      https://cert-portal.siemens.com/productcert/html/ssa-082556.html
      —

      Source identifier: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-23113
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-23113"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-23113.svg?lang=en" alt="CVE-2026-23113 – NEOSEC Intel" height="20"></a>