Network statistics corruption via unsynchronized bridge updates
Published Mar 2, 2024 · Updated May 11, 2026
Race condition in the Linux kernel bridge subsystem allows local users to corrupt interface statistics through concurrent packet processing. The br_handle_frame_finish function updates shared rx_packets, rx_bytes, and tx_dropped fields from multiple CPUs without mutual exclusion or SMP-safe DEV_STATS_INC operations. Exploitation requires low-privileged local access and concurrent bridge traffic; the demonstrated effect is lost or inconsistent device statistics, while direct code execution is not established.
Summary
What happened
Race condition in the Linux kernel bridge subsystem allows local users to corrupt interface statistics through concurrent packet processing. The br_handle_frame_finish function updates shared rx_packets, rx_bytes, and tx_dropped fields from multiple CPUs without mutual exclusion or SMP-safe DEV_STATS_INC operations. Exploitation requires low-privileged local access and concurrent bridge traffic; the demonstrated effect is lost or inconsistent device statistics, while direct code execution is not established.
The record
- CVE
- CVE-2023-52578
- Published
- Mar 2, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 2, 2024CVE 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=1c29fc4989bc2a3838b2837adc12b8aeb0feeede <04cc361f029c14dd067ad180525c7392334c9bfd
- Affected versionversion=1c29fc4989bc2a3838b2837adc12b8aeb0feeede <44bdb313da57322c9b3c108eb66981c6ec6509f4
- Affected versionversion=1c29fc4989bc2a3838b2837adc12b8aeb0feeede <89f9f20b1cbd36d99d5a248a4bf8d11d4fd049a2
- Affected versionversion=1c29fc4989bc2a3838b2837adc12b8aeb0feeede <8bc97117b51d68d5cea8f5351cca2d8c4153f394
- Affected versionversion=1c29fc4989bc2a3838b2837adc12b8aeb0feeede <ad8d39c7b437fcdab7208a6a56c093d222c008d5
- Affected versionversion=1c29fc4989bc2a3838b2837adc12b8aeb0feeede <d2346e6beb699909ca455d9d20c4e577ce900839
- Affected versionversion=1c29fc4989bc2a3838b2837adc12b8aeb0feeede <f2ef4cb4d418fa64fe73eb84d10cc5c0e52e00fa
- Affected versionversion=2.6.17
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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