CVE-2026-23393 Details
Description
In the Linux kernel, the following vulnerability has been resolved: bridge: cfm: Fix race condition in peer_mep deletion When a peer MEP is being deleted, cancel_delayed_work_sync() is called on ccm_rx_dwork before freeing. However, br_cfm_frame_rx() runs in softirq context under rcu_read_lock (without RTNL) and can re-schedule ccm_rx_dwork via ccm_rx_timer_start() between cancel_delayed_work_sync() returning and kfree_rcu() being called. The following is a simple race scenario: cpu0 cpu1 mep_delete_implementation() cancel_delayed_work_sync(ccm_rx_dwork); br_cfm_frame_rx() // peer_mep still in hlist if (peer_mep->ccm_defect) ccm_rx_timer_start() queue_delayed_work(ccm_rx_dwork) hlist_del_rcu(&peer_mep->head); kfree_rcu(peer_mep, rcu); ccm_rx_work_expired() // on freed peer_mep To prevent this, cancel_delayed_work_sync() is replaced with disable_delayed_work_sync() in both peer MEP deletion paths, so that subsequent queue_delayed_work() calls from br_cfm_frame_rx() are silently rejected. The cc_peer_disable() helper retains cancel_delayed_work_sync() because it is also used for the CC enable/disable toggle path where the work must remain re-schedulable.
A race condition vulnerability has been identified in the Linux kernel's bridge component, specifically within the CFM (Connectivity Fault Management) implementation. This issue arises when a peer MEP (Maintenance Endpoint) is deleted. The process first calls 'cancel_delayed_work_sync()' on the 'ccm_rx_dwork' (CCM receive work) before freeing the MEP. However, the function 'br_cfm_frame_rx()' operates in a softirq context under RCU (Read-Copy-Update) read lock, without holding the RTNL (Route Netlink) lock. This allows 'br_cfm_frame_rx()' to reschedule 'ccm_rx_dwork' via 'ccm_rx_timer_start()' after 'cancel_delayed_work_sync()' has returned, but before 'kfree_rcu()' is executed, creating a race condition. The vulnerability affects the Linux kernel stable tree.
The vulnerability has been addressed by replacing 'cancel_delayed_work_sync()' with 'disable_delayed_work_sync()' in the peer MEP deletion process. This change prevents 'br_cfm_frame_rx()' from rescheduling the work item after it has been marked for deletion.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1fd81151f65927fd9edb8ecd12ad45527dbbe5ab | kernel.org | Patch |
| https://git.kernel.org/stable/c/3715a00855316066cdda69d43648336367422127 | kernel.org | Patch |
| https://git.kernel.org/stable/c/d8f35767bacb3c7769d470a41cf161e3f3c07e70 | kernel.org | Patch |
| https://git.kernel.org/stable/c/e89dbd2736a45f0507949af4748cbbf3ff793146 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.11.1, < 6.12.78 >= 6.13, < 6.18.20 >= 6.19, < 6.19.10 5.11 - 7.0 rc1 7.0 rc2 7.0 rc3 7.0 rc4 7.0 rc5 7.0 rc6 7.0 rc7 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Apr 24, 2026 | Initial Analysis | [email protected] |
| Apr 2, 2026 | CVE Modified | kernel.org |
| Mar 25, 2026 | New CVE Received | kernel.org |