System hang via recursive VLAN device locking
Published May 1, 2025 · Updated May 11, 2026
Improper locking in Linux kernel VLAN handling allows local users to hang the system by opening a specially configured network device. During bond enslaving, vlan_dev_open propagates ALLMULTI or PROMISC to the real device and dev_set_allmulti attempts to reacquire the device lock already held by dev_open. Local access able to create and enslave VLAN and bond links is required; the recursive lock can deadlock the kernel and halt host service.
Summary
What happened
Improper locking in Linux kernel VLAN handling allows local users to hang the system by opening a specially configured network device. During bond enslaving, vlan_dev_open propagates ALLMULTI or PROMISC to the real device and dev_set_allmulti attempts to reacquire the device lock already held by dev_open. Local access able to create and enslave VLAN and bond links is required; the recursive lock can deadlock the kernel and halt host service.
The record
- CVE
- CVE-2025-23163
- Published
- May 1, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.23
- Affected versionversion=6c78dcbd47a68a7d25d2bee7a6c74b9136cb5fde <27b918007d96402aba10ed52a6af8015230f1793
- Affected versionversion=6c78dcbd47a68a7d25d2bee7a6c74b9136cb5fde <299d7d27af6b5844cda06a0fdfa635705e1bc50f
- Affected versionversion=6c78dcbd47a68a7d25d2bee7a6c74b9136cb5fde <523fa0979d842443aa14b80002e45b471cbac137
- Affected versionversion=6c78dcbd47a68a7d25d2bee7a6c74b9136cb5fde <538b43aa21e3b17c110104efd218b966d2eda5f8
- Affected versionversion=6c78dcbd47a68a7d25d2bee7a6c74b9136cb5fde <53fb25e90c0a503a17c639341ba5e755cb2feb5c
- Affected versionversion=6c78dcbd47a68a7d25d2bee7a6c74b9136cb5fde <8980018a9806743d9b80837330d46f06ecf78516
- Affected versionversion=6c78dcbd47a68a7d25d2bee7a6c74b9136cb5fde <a32f1d4f1f4c9d978698f3c718621f6198f2e7ac
- Affected versionversion=6c78dcbd47a68a7d25d2bee7a6c74b9136cb5fde <b1e3eeb037256a2f1206a8d69810ec47eb152026
- Affected versionversion=6c78dcbd47a68a7d25d2bee7a6c74b9136cb5fde <d537859e56bcc3091805c524484a4c85386b3cc8
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo