Hardware rule corruption via cross-instance race
Published Aug 15, 2026 · Updated Aug 15, 2026
Incorrect synchronization in the Linux Microchip VCAP API allows local users to corrupt hardware rules via concurrent debugfs and tc access. Per-instance locks fail to serialize IS0 and IS2 accesses to the shared Super VCAP cache, letting a debugfs read replace a writer's cached data before commit. Reachability requires sparx5 or lan969x hardware, a full debugfs rule dump, and a concurrent privileged tc-flower write; the documented result is dump and hardware-entry corruption.
Summary
What happened
Incorrect synchronization in the Linux Microchip VCAP API allows local users to corrupt hardware rules via concurrent debugfs and tc access. Per-instance locks fail to serialize IS0 and IS2 accesses to the shared Super VCAP cache, letting a debugfs read replace a writer's cached data before commit. Reachability requires sparx5 or lan969x hardware, a full debugfs rule dump, and a concurrent privileged tc-flower write; the documented result is dump and hardware-entry corruption.
The record
- CVE
- CVE-2026-72340
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-821
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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=6.2
- Affected versionversion=71c9de995260222e739020104d477af4775a6d26 <1e71a40d101547380590db582213c1f1dce1f041
- Affected versionversion=71c9de995260222e739020104d477af4775a6d26 <49806bef9572a2e012610517bc14ed0a4db0d1fc
- Affected versionversion=71c9de995260222e739020104d477af4775a6d26 <786456d0a244bbd405dfc60e4de51f8b348b9cb1
- Affected versionversion=71c9de995260222e739020104d477af4775a6d26 <952928564cc5fdb06f92d7e25c6cd2e1d816362b
- Affected versionversion=71c9de995260222e739020104d477af4775a6d26 <d7a8d500d7e42837bd8dce40cb52c97c6e8706a9
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