CVE-2022-50242

drivers: net: qlcnic: Fix potential memory leak in qlcnic_sriov_init()

MEDIUM

5.5

CVSS Score

Published: September 15, 2025 at 02:01 PM UTC

Updated: June 17, 2026 at 05:23 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: drivers: net: qlcnic: Fix potential memory leak in qlcnic_sriov_init() If vp alloc failed in qlcnic_sriov_init(), all previously allocated vp needs to be freed.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

3.10 ≤ v < 4.14.3033.10 ≤ v < 4.19.2703.10 ≤ v < 4.9.3373.10 ≤ v < 5.10.1633.10 ≤ v < 5.15.863.10 ≤ v < 5.4.2293.10 ≤ v < 6.0.163.10 ≤ v < 6.1.23.10 ≤ v < 6.24.10 ≤ v < 4.14.3034.15 ≤ v < 4.19.2704.20 ≤ v < 5.4.2295.11 ≤ v < 5.15.865.16 ≤ v < 6.0.165.5 ≤ v < 5.10.1636.1 ≤ v < 6.1.23.10f197a7aa62888f27c9a7976b18eb4f040f6606ce

Vendor states this is fixed in 01de1123322e4fe1bbd0fcdf0982511b55519c03 (fixed)

Vendor states this is fixed in 0aefadf23ee5e33b747df195ace42d3be2025e4e (fixed)

Vendor states this is fixed in 132c502919bb08e16e3054cb28bb7b149ec20cf5 (fixed)

Vendor states this is fixed in 14b349a15c297cf3e01b5deb4116f7cf297b6184 (fixed)

Vendor states this is fixed in 15770edc01edfce773269e8a443ca8e420f6f859 (fixed)

Vendor states this is fixed in 8399b9893548c03fdb18be277bf99d985dbde925 (fixed)

Vendor states this is fixed in a44490abaf00f5b0cc5c448a17eae331c6195d0a (fixed)

Vendor states this is fixed in aa2d179544b6815b4a23c0c44543ba0971d49fce (fixed)

Vendor states this is fixed in dcae92a249551d1a447804b4be1c9fab0e8c95e8 (fixed)

Vendor states this is fixed in 3.10 (unaffected)

Vendor states this is fixed in 4.14.303 (unaffected)

Vendor states this is fixed in 4.19.270 (unaffected)