CVE-2022-50252

igb: Do not free q_vector unless new one was allocated

HIGH

7.8

CVSS Score

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

Updated: October 15, 2026 at 10:17 PM 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

HIGH7.8

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: igb: Do not free q_vector unless new one was allocated Avoid potential use-after-free condition under memory pressure. If the kzalloc() fails, q_vector will be freed but left in the original adapter->q_vector[v_idx] array position.

Affected

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

Linux Kernel · Linux

95%

v < 4.9.3374.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.18.23 4.1.9 4.2.2 4.35be042b1917ddf444c20f4e12856535307b37c0172ddef0506da852dc82f078f37ced8ef4d74a2bfa0e26ed623a1e1460c1a191fbc0f37bddab7851af4b7f93cd34a6153d454a837708fd4203990d1ae

Vendor states this is fixed in 0200f0fbb11e359cc35af72ab10b2ec224e6f633 (fixed)

Vendor states this is fixed in 0668716506ca66f90d395f36ccdaebc3e0e84801 (fixed)

Vendor states this is fixed in 314f7092b27749bdde44c14095b5533afa2a3bc8 (fixed)

Vendor states this is fixed in 3cb18dea11196fb4a06f78294cec5e61985e1aff (fixed)

Vendor states this is fixed in 56483aecf6b22eb7dff6315b3a174688c6ad494c (fixed)

Vendor states this is fixed in 64ca1969599857143e91aeec4440640656100803 (fixed)

Vendor states this is fixed in 68e8adbcaf7a8743e473343b38b9dad66e2ac6f3 (fixed)

Vendor states this is fixed in 6e399577bd397a517df4b938601108c63769ce0a (fixed)

Vendor states this is fixed in f96bd8adc8adde25390965a8c1ee81b73cb62075 (fixed)

Affected range stops below 3.19, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.14.303 (unaffected)

Vendor states this is fixed in 4.19.270 (unaffected)

Affected range stops below 4.2, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.3 (unaffected)

Vendor states this is fixed in 4.9.337 (unaffected)

Vendor states this is fixed in 5.10.163 (unaffected)

Vendor states this is fixed in 5.15.86 (unaffected)

Vendor states this is fixed in 5.4.229 (unaffected)

Vendor states this is fixed in 6.0.16 (unaffected)

Vendor states this is fixed in 6.1.2 (unaffected)

Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references