# CVE-2022-49084: qede: confirm skb is allocated before using

> A missing null check in the qede network driver causes a kernel panic when memory allocation fails, leading to denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Feb 2025
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2022-49084, GHSA-f6f6-f4j2-hrcf, UBUNTU-CVE-2022-49084

## What is CVE-2022-49084?

CVE-2022-49084 is a high-severity vulnerability in Linux kernel, published on 26 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

qede: confirm skb is allocated before using

qede_build_skb() assumes build_skb() always works and goes straight
to skb_reserve(). However, build_skb() can fail under memory pressure.
This results in a kernel panic because the skb to reserve is NULL.

Add a check in case build_skb() failed to allocate and return NULL.

The NULL return is handled correctly in callers to qede_build_skb().

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2022-49084?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2022-49084?

Apply the vendor's patch.

## Is CVE-2022-49084 being exploited?

There is no known exploitation of CVE-2022-49084 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-49084 and fix it if it is affected.

What it is: CVE-2022-49084 is a high-severity vulnerability in Linux kernel, published on 26 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-49084 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-49084/ (Markdown: https://insights.sbomify.com/CVE-2022-49084/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-49084
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-49084
- OSV: https://osv.dev/vulnerability/CVE-2022-49084

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-49084/
Summaries are generated and may contain mistakes; the official description above is the record.