Network-management hang via stale bridge-cleanup barrier
Published Oct 23, 2026 · Updated Oct 23, 2026
Denial of service in Linux bridge cleanup allows attackers to hang network-management tasks during bridge-device removal. The br_multicast_dev_del() function retains an rcu_barrier() despite using kfree_rcu(), causing extreme RTNL contention and blocked tasks. Reaching the path requires bridge teardown, including network-namespace cleanup; public evidence does not establish attacker privileges or a remote trigger.
Summary
What happened
Denial of service in Linux bridge cleanup allows attackers to hang network-management tasks during bridge-device removal. The br_multicast_dev_del() function retains an rcu_barrier() despite using kfree_rcu(), causing extreme RTNL contention and blocked tasks. Reaching the path requires bridge teardown, including network-namespace cleanup; public evidence does not establish attacker privileges or a remote trigger.
The record
- CVE
- CVE-2026-98881
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 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=0 <5.10.271
- Affected versionversion=0 <5.15.222
- Affected versionversion=0 <6.1.189
- Affected versionversion=0 <6.12.111
- Affected versionversion=0 <6.18.53
- Affected versionversion=0 <6.6.158
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0443f6aac6bf6a91e406273fdda11497cef6ad07
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <25ae123db10ba9ab890b56bcdb0a4363aee8529a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <35f9f11740515a10b084adfb1ce691351f2452ab
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <372ee8fbe0f796031c60f676ec90f0788c26523d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <39679927fa7aaf4601119f7234342d1b5d4f6f84
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ac0e823a228f94ad9d7a3d876cc07e59a7afb806
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f0018acf0b66f93a292667c9a9c2a26c570cf270
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us