LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50252: igb: Do not free q_vector unless new one was allocated

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50252 is a Linux kernel issue in the Intel igb network driver. Under memory pressure, failed allocation can leave a freed queue-vector pointer in place, creating a potential use-after-free. The sources do not provide CVSS, confirmed impact, or active exploitation evidence.

Executive priority

Treat this as a kernel maintenance priority for Linux fleets using igb networking, not an emergency based on current evidence. Escalate if your vendor assigns severity, confirms broader impact, or reports exploitation.

Technical view

The flaw is in igb queue-vector allocation handling. If kzalloc() fails, q_vector may be freed while adapter->q_vector[v_idx] still references it. Kernel stable commits correct the logic by avoiding free unless a new q_vector was allocated.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with the igb Ethernet driver in use. The bundle lists affected Linux kernel versions and multiple stable fix commits, but does not identify distributions or appliances.

Exploitation context

No active exploitation is supported by the provided sources. The CVE is not marked KEV, and the bundle provides no public exploit, attack preconditions, or demonstrated impact beyond a potential use-after-free under memory pressure.

Researcher notes

The strongest evidence is the kernel commit description and stable backports. Missing data includes CVSS, CWE, exploitability conditions, affected distribution package ranges, and observable indicators. Avoid assuming privilege escalation or remote reachability without vendor confirmation.

Mitigation direction

  • Update affected Linux kernels through the normal vendor-supported kernel update channel.
  • Prioritize systems using the igb Ethernet driver in production or high-availability paths.
  • Check distribution advisories for the exact fixed package version.
  • Reboot or otherwise activate the updated kernel after maintenance approval.
  • If patch timing is unclear, monitor kernel vendor guidance for this CVE.

Validation and detection

  • Inventory Linux kernel versions across servers and images.
  • Identify hosts using or loading the igb network driver.
  • Compare deployed kernels against vendor fixed versions or listed stable commits.
  • Confirm the patched kernel is active after reboot.
  • Verify vulnerability scanners no longer report CVE-2022-50252.
Prepared
Confidence
medium
Sources
11

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50252 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
10Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux72ddef0506da852dc82f078f37ced8ef4d74a2bf, 72ddef0506da852dc82f078f37ced8ef4d74a2bf, 72ddef0506da852dc82f078f37ced8ef4d74a2bf, 72ddef0506da852dc82f078f37ced8ef4d74a2bf, 72ddef0506da852dc82f078f37ced8ef4d74a2bf, 72ddef0506da852dc82f078f37ced8ef4d74a2bf, 72ddef0506da852dc82f078f37ced8ef4d74a2bf, 72ddef0506da852dc82f078f37ced8ef4d74a2bf, 72ddef0506da852dc82f078f37ced8ef4d74a2bf, 5be042b1917ddf444c20f4e12856535307b37c01, a0e26ed623a1e1460c1a191fbc0f37bddab7851a, f4b7f93cd34a6153d454a837708fd4203990d1aeunaffected
LinuxLinux4.3, 0, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.