Kernel memory exhaustion via leaked VP allocations
Published Sep 15, 2025 · Updated Sep 15, 2025
Memory leak in the qlcnic SR-IOV initialization path in Linux allows local users to exhaust kernel memory during device setup. qlcnic_sriov_init allocates VP objects in a loop but returns after a later allocation failure without freeing objects created by earlier iterations. Reachability requires local access, the qlcnic driver, SR-IOV initialization, and a VP allocation failure; the resulting leak can interrupt service by consuming kernel memory.
Summary
What happened
Memory leak in the qlcnic SR-IOV initialization path in Linux allows local users to exhaust kernel memory during device setup. qlcnic_sriov_init allocates VP objects in a loop but returns after a later allocation failure without freeing objects created by earlier iterations. Reachability requires local access, the qlcnic driver, SR-IOV initialization, and a VP allocation failure; the resulting leak can interrupt service by consuming kernel memory.
The record
- CVE
- CVE-2022-50242
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 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=3.10
- Affected versionversion=f197a7aa62888f27c9a7976b18eb4f040f6606ce <01de1123322e4fe1bbd0fcdf0982511b55519c03
- Affected versionversion=f197a7aa62888f27c9a7976b18eb4f040f6606ce <0aefadf23ee5e33b747df195ace42d3be2025e4e
- Affected versionversion=f197a7aa62888f27c9a7976b18eb4f040f6606ce <132c502919bb08e16e3054cb28bb7b149ec20cf5
- Affected versionversion=f197a7aa62888f27c9a7976b18eb4f040f6606ce <14b349a15c297cf3e01b5deb4116f7cf297b6184
- Affected versionversion=f197a7aa62888f27c9a7976b18eb4f040f6606ce <15770edc01edfce773269e8a443ca8e420f6f859
- Affected versionversion=f197a7aa62888f27c9a7976b18eb4f040f6606ce <8399b9893548c03fdb18be277bf99d985dbde925
- Affected versionversion=f197a7aa62888f27c9a7976b18eb4f040f6606ce <a44490abaf00f5b0cc5c448a17eae331c6195d0a
- Affected versionversion=f197a7aa62888f27c9a7976b18eb4f040f6606ce <aa2d179544b6815b4a23c0c44543ba0971d49fce
- Affected versionversion=f197a7aa62888f27c9a7976b18eb4f040f6606ce <dcae92a249551d1a447804b4be1c9fab0e8c95e8
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