cve.bz

CVE-2026-23368 linux linux kernel: Improper Locking

5.5 mediumEPSS 0.1%Fix available

Medium (5.5) in linux linux kernel. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.10% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-667 Improper Locking
Published
Modified
Assigned by
Linux (CNA)
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-23368 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-23368?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-23368?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-23368 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-23368

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-23368](https://cve.bz/cve/badge/CVE-2026-23368.svg)](https://cve.bz/cve/CVE-2026-23368)

HTML:

<a href="https://cve.bz/cve/CVE-2026-23368"><img src="https://cve.bz/cve/badge/CVE-2026-23368.svg" alt="CVE-2026-23368"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux4.16 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.253
Linux5.155.15.203
Linux6.16.1.167
Linux6.66.6.130
Linux6.126.12.78
Linux6.186.18.17
Linux6.196.19.7
Linuxlater releases7.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.170-1DEBIAN-CVE-2026-23368
Debian13linux6.12.85-1DEBIAN-CVE-2026-23368
Debian14linux6.19.8-1DEBIAN-CVE-2026-23368
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-23368
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-23368
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-23368
Ubuntu22.04:LTSlinux5.15.0-186.196UBUNTU-CVE-2026-23368 USN-8575-1
Ubuntu22.04:LTSlinux-aws5.15.0-1112.119UBUNTU-CVE-2026-23368 USN-8575-2
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1061.64~22.04.1UBUNTU-CVE-2026-23368 USN-8595-3
Ubuntu22.04:LTSlinux-azure, linux-azure-fde5.15.0-1117.126UBUNTU-CVE-2026-23368 USN-8575-3 USN-8610-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1063.71~22.04.1UBUNTU-CVE-2026-23368 USN-8606-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1062.69~22.04.1UBUNTU-CVE-2026-23368 USN-8609-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1112.122UBUNTU-CVE-2026-23368 USN-8575-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1064.72~22.04.1UBUNTU-CVE-2026-23368 USN-8567-1
Ubuntu22.04:LTSlinux-gke5.15.0-1108.114UBUNTU-CVE-2026-23368 USN-8575-1
65 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.55.1SUSE-SU-2026:2238-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_151-150700.15.3.1SUSE-SU-2026:2238-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-64kb, kernel-source, kernel-default and 1 more6.4.0-150700.53.55.1SUSE-SU-2026:2238-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-default-base6.4.0-150700.53.55.1.150700.17.33.1SUSE-SU-2026:2238-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-docs, kernel-syms, kernel-source and 1 more6.4.0-150700.53.55.1SUSE-SU-2026:2238-1
SUSELinux Enterprise Module for Public Cloud 15 SP7kernel-azure6.4.0-150700.53.55.1SUSE-SU-2026:2238-1
SUSELinux Micro Extras 6.2kernel-syms, kernel-obs-build6.12.0-160000.33.1SUSE-SU-2026:21834-1
Azure Linux3kernel6.6.130.1-1AZL-80610
Alpaquita23linux-lts6.1.167-r0BELL-CVE-2026-23368
Alpaquita25linux-lts6.12.80-r0BELL-CVE-2026-23368
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-23368

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This deadlock requires both LEDS_TRIGGER_NETDEV and LED_TRIGGER_PHY kernel configurations to be enabled simultaneously. The issue triggers during PHY attachment when a user concurrently writes to an LED trigger sysfs file. In practice, this is an uncommon configuration combination and requires specific timing to reproduce, limiting the practical impact.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-23368.

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-26-295-11Siemens SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP2026-10-13Critical Manufacturing, Transportation Systems, Energy, Healthcare and Public Health, Financial Services, Government Services and FacilitiesSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.7, SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.7, SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.7 and 2 morenone listed
ICSA-26-295-16Siemens SIMATIC S7-1500 TM MFP2026-10-13Critical Manufacturing, Transportation Systems, Energy, Healthcare and Public Health, Financial Services, Government Services and FacilitiesSIMATIC S7-1500 TM MFP - GNU/Linux subsystemnone listed
ICSA-26-209-04Siemens SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP2026-07-14Critical ManufacturingSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6, SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6, SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6 and 2 morenone listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

Attack patterns (CAPEC)

  • CAPEC-25 Forced Deadlock Likelihood: Low · Severity: High
  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON