Adjacent code execution via bridge-driver use-after-free
Published Jul 9, 2024 · Updated Feb 10, 2026
Use-after-free in the Windows Layer-2 Bridge Network Driver allows adjacent unauthenticated attackers to execute arbitrary code. The driver accesses memory after releasing it while processing Layer-2 bridge traffic; Microsoft has not disclosed the affected routine or packet field. Exploitation requires access to the adjacent network and a system using the bridge driver, and successful exploitation runs attacker-controlled code on the Windows host.
Summary
What happened
Use-after-free in the Windows Layer-2 Bridge Network Driver allows adjacent unauthenticated attackers to execute arbitrary code. The driver accesses memory after releasing it while processing Layer-2 bridge traffic; Microsoft has not disclosed the affected routine or packet field. Exploitation requires access to the adjacent network and a system using the bridge driver, and successful exploitation runs attacker-controlled code on the Windows host.
The record
- CVE
- CVE-2024-38053
- Published
- Jul 9, 2024
- Updated
- Feb 10, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-416, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 9, 2024CVE publishedPublication date reported by the CVE source.
- Feb 10, 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=10.0.10240.0 <10.0.10240.20710
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.
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