Remote memory exhaustion via unreleased network frames
Published Oct 16, 2022 · Updated Apr 14, 2025
Memory leak in the macvlan receive path in Linux Kernel 5.13 through 5.15.34 and 5.16 through 5.17.3 allows remote attackers to exhaust memory. macvlan_handle_frame treats frames consumed by macvlan_forward_source as handled but returns without freeing the associated socket buffer. An unauthenticated sender must reach a host with an affected macvlan configuration; repeated qualifying frames consume kernel memory until service is interrupted.
Summary
What happened
Memory leak in the macvlan receive path in Linux Kernel 5.13 through 5.15.34 and 5.16 through 5.17.3 allows remote attackers to exhaust memory. macvlan_handle_frame treats frames consumed by macvlan_forward_source as handled but returns without freeing the associated socket buffer. An unauthenticated sender must reach a host with an affected macvlan configuration; repeated qualifying frames consume kernel memory until service is interrupted.
The record
- CVE
- CVE-2022-3526
- Published
- Oct 16, 2022
- Updated
- Apr 14, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, CWE-404, T1499.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2022CVE publishedPublication date reported by the CVE source.
- Apr 14, 2025Record 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=n/a
What conditions does exploitation require?
What is affected?
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