CVE-2026-23393bridge: cfm: Fix race condition in peer_mep deletion
- 7.8HighCVSS base score
- 0.10%Exploitation in 30 daysEPSS · top 99% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 2 months later
· 2 months later
Published
- 4 months later
· 4 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.10% · top 99% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected dc32cbb3dbd7da38c700d6e0fc6354df24920525 – < e89dbd2736a45f0507949af4748cbbf3ff793146
- affected dc32cbb3dbd7da38c700d6e0fc6354df24920525 – < d8f35767bacb3c7769d470a41cf161e3f3c07e70
- affected dc32cbb3dbd7da38c700d6e0fc6354df24920525 – < 1fd81151f65927fd9edb8ecd12ad45527dbbe5ab
- affected dc32cbb3dbd7da38c700d6e0fc6354df24920525 – < 3715a00855316066cdda69d43648336367422127
- affected 5.11
- unaffected < 5.11
- unaffected 6.12.78 – ≤ 6.12.*
- unaffected 6.18.20 – ≤ 6.18.*
- unaffected 6.19.10 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References4
- https://git.kernel.org/stable/c/e89dbd2736a45f0507949af4748cbbf3ff793146 (opens in a new tab)
- https://git.kernel.org/stable/c/d8f35767bacb3c7769d470a41cf161e3f3c07e70 (opens in a new tab)
- https://git.kernel.org/stable/c/1fd81151f65927fd9edb8ecd12ad45527dbbe5ab (opens in a new tab)
- https://git.kernel.org/stable/c/3715a00855316066cdda69d43648336367422127 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-15394 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-23393)Record last updated .