MediumCVE-2026-23368

    Linux Kernel: Deadlock (CVE-2026-23368)

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

    Share

    What is affected, what to do

    In the Linux kernel, the following vulnerability has been resolved: net: phy: register phy led_triggers during probe to avoid AB-BA deadlock There is an AB-BA deadlock when both LEDS_TRIGGER_NETDEV and LED_TRIGGER_PHY are enabled: [ 1362.049207] [<8054e4b8>] led_trigger_register+0x5c/0x1fc <-- Trying to get lock "triggers_list_lock" via down_write(&triggers_list_lock); [ 1362.054536] [<80662830>] phy_led_triggers_register+0xd0/0x234 [ 1362.060329] [<8065e200>] phy_attach_direct+0x33c/0x40c [ 1362.065489] [<80651fc4>] phylink_fwnode_phy_connect+0x15c/0x23c [ 1362.071480] [<8066ee18>] mtk_open+0x7c/0xba0 [ 1362.075849] [<806d714c>] __dev_open+0x280/0x2b0 [ 1362.080384] [<806d7668>] __dev_change_flags+0x244/0x24c [ 1362.085598] [<806d7698>] dev_change_flags+0x28/0x78 [ 1362.090528] [<807150e4>] dev_ioctl+0x4c0/0x654 <-- Hold lock "rtnl_mutex" by calling rtnl_lock(); [ 1362.094985] [<80694360>] sock_ioctl+0x2f4/0x4e0 [ 1362.099567] [<802e9c4c>] sys_ioctl+0x32c/0xd8c [ 1362.104022] [<80014504>] syscall_common+0x34/0x58 Here LED_TRIGGER_PHY is registering LED triggers during phy_attach while holding RTNL and then taking triggers_list_lock. [ 1362.191101] [<806c2640>] register_netdevice_notifier+0x60/0x168 <-- Trying to get lock "rtnl_mutex" via rtnl_lock(); [ 1362.197073] [<805504ac>] netdev_trig_activate+0x194/0x1e4 [ 1362.202490] [<8054e28c>] led_trigger_set+0x1d4/0x360 <-- Hold lock "triggers_list_lock" by down_read(&triggers_list_lock); [ 1362.207511] [<8054eb38>] led_trigger_write+0xd8/0x14c [ 1362.212566] [<80381d98>] sysfs_kf_bin_write+0x80/0xbc [ 1362.217688] [<8037fcd8>] kernfs_fop_write_iter+0x17c/0x28c [ 1362.223174] [<802cbd70>] vfs_write+0x21c/0x3c4 [ 1362.227712] [<802cc0c4>] ksys_write+0x78/0x12c [ 1362.232164] [<80014504>] syscall_common+0x34/0x58 Here LEDS_TRIGGER_NETDEV is being enabled on an LED. It first takes triggers_list_lock and then RTNL.

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

    Affected
    • Linux Kernel lt 4.16..5.10.253
    • Linux Kernel lt 5.11..5.15.203
    • Linux Kernel lt 5.16..6.1.167
    • Linux Kernel lt 6.2..6.6.130
    • Linux Kernel lt 6.7..6.12.78
    • Linux Kernel lt 6.13..6.18.17
    • Linux Kernel lt 6.19..6.19.7
    • Linux Kernel lt 6.20..7.0
    Fixed in
    • Linux Kernel 5.10.253
    • Linux Kernel 5.15.203
    • Linux Kernel 6.1.167
    • Linux Kernel 6.6.130
    • Linux Kernel 6.12.78
    • Linux Kernel 6.18.17
    • Linux Kernel 6.19.7
    • Linux Kernel 7.0

    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: Debian LTS, Siemens ProductCERT, Debian, SUSE, Ubuntu, BSI, CVE.org, Msrc Update Guide, EUVD

    0.1 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 1.0

    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
    42.87 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
    1.0
    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: net: phy: register phy led_triggers during probe to avoid AB-BA deadlock There is an AB-BA deadlock when both LEDS_TRIGGER_NETDEV and LED_TRIGGER_PHY are enabled: [ 1362.049207] [<8054e4b8>] led_trigger_register+0x5c/0x1fc <-- Trying to get lock "triggers_list_lock" via down_write(&triggers_list_lock); [ 1362.054536] [<80662830>] phy_led_triggers_register+0xd0/0x234 [ 1362.060329] [<8065e200>] phy_attach_direct+0x33c/0x40c [ 1362.065489] [<80651fc4>] phylink_fwnode_phy_connect+0x15c/0x23c [ 1362.071480] [<8066ee18>] mtk_open+0x7c/0xba0 [ 1362.075849] [<806d714c>] __dev_open+0x280/0x2b0 [ 1362.080384] [<806d7668>] __dev_change_flags+0x244/0x24c [ 1362.085598] [<806d7698>] dev_change_flags+0x28/0x78 [ 1362.090528] [<807150e4>] dev_ioctl+0x4c0/0x654 <-- Hold lock "rtnl_mutex" by calling rtnl_lock(); [ 1362.094985] [<80694360>] sock_ioctl+0x2f4/0x4e0 [ 1362.099567] [<802e9c4c>] sys_ioctl+0x32c/0xd8c [ 1362.104022] [<80014504>] syscall_common+0x34/0x58 Here LED_TRIGGER_PHY is registering LED triggers during phy_attach while holding RTNL and then taking triggers_list_lock. [ 1362.191101] [<806c2640>] register_netdevice_notifier+0x60/0x168 <-- Trying to get lock "rtnl_mutex" via rtnl_lock(); [ 1362.197073] [<805504ac>] netdev_trig_activate+0x194/0x1e4 [ 1362.202490] [<8054e28c>] led_trigger_set+0x1d4/0x360 <-- Hold lock "triggers_list_lock" by down_read(&triggers_list_lock); [ 1362.207511] [<8054eb38>] led_trigger_write+0xd8/0x14c [ 1362.212566] [<80381d98>] sysfs_kf_bin_write+0x80/0xbc [ 1362.217688] [<8037fcd8>] kernfs_fop_write_iter+0x17c/0x28c [ 1362.223174] [<802cbd70>] vfs_write+0x21c/0x3c4 [ 1362.227712] [<802cc0c4>] ksys_write+0x78/0x12c [ 1362.232164] [<80014504>] syscall_common+0x34/0x58 Here LEDS_TRIGGER_NETDEV is being enabled on an LED. It first takes triggers_list_lock and then RTNL. A classical AB-BA deadlock. phy_led_triggers_registers() does not require the RTNL, it does not make any calls into the network stack which require protection. There is also no requirement the PHY has been attached to a MAC, the triggers only make use of phydev state. This allows the call to phy_led_triggers_registers() to be placed elsewhere. PHY probe() and release() don't hold RTNL, so solving the AB-BA deadlock.

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

    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.2 – < 6.6.130
    • 6.7 – < 6.12.78
    • 4.16 – < 5.10.253
    • 5.11 – < 5.15.203
    • 6.20 – < 7.0
    • 6.19 – < 6.19.7
    • 6.13 – < 6.18.17
    • 5.16 – < 6.1.167
    • 6.6.130
    • 6.12.78
    • 5.10.253
    • 5.15.203
    • 7.0
    • 6.19.7
    • 6.18.17
    • 6.1.167
    SiemensSIMATIC S7
    • 1500 TM MFP V1.1.1 GNU/Linux subsystem
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianlinuxbookworm
    Linuxdebianlinuxbullseye
    Linuxdebianlinuxtrixie
    Linuxdebianlinux-6.1bullseye
    Linuxlinuxlinux_kernel4.16
    Linuxlinuxlinux_kernel7.0
    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 24 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://git.kernel.org/stable/c/241cd64cf2e32b28ead151b1795cd8fef2b6e482
      Referenceadded
      —
      https://git.kernel.org/stable/c/2764dcb3c35de4410f642afc62cf979727470575
      Referenceadded
      —
      https://git.kernel.org/stable/c/2b01518eabace18f7ec8b4cafd52082303080dca
      Referenceadded
      —
      https://git.kernel.org/stable/c/305afdd02ff3e694c165457793104710ec0728e5
      Referenceadded
      —
      https://git.kernel.org/stable/c/c33523b8fd2d4c504ada18cd93f511f2a8f84217
      Referenceadded
      —
      https://git.kernel.org/stable/c/c6ffc2d2338d325e1edd0c702e3ee623aa5fdc6a
      Referenceadded
      —
      https://git.kernel.org/stable/c/c8dbdc6e380e7e96a51706db3e4b7870d8a9402d
      Referenceadded
      —
      https://git.kernel.org/stable/c/cde2d0b5ab5d03b5b6f17d4f654d8b30ccf36757
      Referenceremoved
      https://git.kernel.org/stable/c/241cd64cf2e32b28ead151b1795cd8fef2b6e482
      —
      Referenceremoved
      https://git.kernel.org/stable/c/2764dcb3c35de4410f642afc62cf979727470575
      —
      Referenceremoved
      https://git.kernel.org/stable/c/2b01518eabace18f7ec8b4cafd52082303080dca
      —
      Referenceremoved
      https://git.kernel.org/stable/c/305afdd02ff3e694c165457793104710ec0728e5
      —
      Referenceremoved
      https://git.kernel.org/stable/c/c33523b8fd2d4c504ada18cd93f511f2a8f84217
      —
      Referenceremoved
      https://git.kernel.org/stable/c/c6ffc2d2338d325e1edd0c702e3ee623aa5fdc6a
      —
      Referenceremoved
      https://git.kernel.org/stable/c/c8dbdc6e380e7e96a51706db3e4b7870d8a9402d
      —
      Referenceremoved
      https://git.kernel.org/stable/c/cde2d0b5ab5d03b5b6f17d4f654d8b30ccf36757
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/241cd64cf2e32b28ead151b1795cd8fef2b6e482 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/2764dcb3c35de4410f642afc62cf979727470575 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/2b01518eabace18f7ec8b4cafd52082303080dca Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/305afdd02ff3e694c165457793104710ec0728e5 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/c33523b8fd2d4c504ada18cd93f511f2a8f84217 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/c6ffc2d2338d325e1edd0c702e3ee623aa5fdc6a Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/c8dbdc6e380e7e96a51706db3e4b7870d8a9402d Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/cde2d0b5ab5d03b5b6f17d4f654d8b30ccf36757 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-23368.json">CVE-2026-23368</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-23368
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-23368"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-23368.svg?lang=en" alt="CVE-2026-23368 – NEOSEC Intel" height="20"></a>