Kernel memory exhaustion via VLAN allocation leak
Published Feb 26, 2025 · Updated May 23, 2026
Memory leak in the Linux kernel VLAN link handler allows local users to exhaust kernel memory through crafted egress QoS maps. The vlan_newlink error path leaves earlier vlan_dev_set_egress_priority allocations referenced when a later vlan_changelink allocation fails because no destructor runs after failed link creation. A local user must be able to create VLAN links and trigger the allocation-failure path; repeated attempts can deplete kernel memory and interrupt service.
Summary
What happened
Memory leak in the Linux kernel VLAN link handler allows local users to exhaust kernel memory through crafted egress QoS maps. The vlan_newlink error path leaves earlier vlan_dev_set_egress_priority allocations referenced when a later vlan_changelink allocation fails because no destructor runs after failed link creation. A local user must be able to create VLAN links and trigger the allocation-failure path; repeated attempts can deplete kernel memory and interrupt service.
The record
- CVE
- CVE-2022-49636
- Published
- Feb 26, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 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=37aa50c539bcbcc01767e515bd170787fcfc0f33 <4c43069bb1097dd6cc1cf0f7c43a36d1f7b3910b
- Affected versionversion=37aa50c539bcbcc01767e515bd170787fcfc0f33 <72a0b329114b1caa8e69dfa7cdad1dd3c69b8602
- Affected versionversion=5.10.235 <5.10.236
- Affected versionversion=5.15.142 <5.15.180
- Affected versionversion=5.17
- Affected versionversion=5.4.291 <5.4.292
- Affected versionversion=62d7ad2c191122119c66361ba6d9f04974b51afe <df27729a4fe0002dfd80c96fe1c142829c672728
- Affected versionversion=842801181864690fdcde73b017cce4c1353a7083 <f5dc10b910bdac523e5947336445a77066c51bf9
- Affected versionversion=b195d229de401377f70c04e0dff93b342464ec8e <549de58dba4bf1b2adc72e9948b9c76fa88be9d2
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