# CVE-2024-45030: igb: cope with large MAX_SKB_FRAGS

> The Linux kernel igb driver causes payload corruption and potential crashes when MAX_SKB_FRAGS is set to large values due to improper ring layout calculation.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 11 Sep 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-49236, BELL-CVE-2024-45030, DEBIAN-CVE-2024-45030, GHSA-pc7p-wr8c-6r5f, UBUNTU-CVE-2024-45030

## What is CVE-2024-45030?

CVE-2024-45030 is a critical memory corruption vulnerability in Linux kernel, published on 11 Sep 2024. 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:

igb: cope with large MAX_SKB_FRAGS

Sabrina reports that the igb driver does not cope well with large
MAX_SKB_FRAG values: setting MAX_SKB_FRAG to 45 causes payload
corruption on TX.

An easy reproducer is to run ssh to connect to the machine.  With
MAX_SKB_FRAGS=17 it works, with MAX_SKB_FRAGS=45 it fails.  This has
been reported originally in
https://bugzilla.redhat.com/show_bug.cgi?id=2265320

The root cause of the issue is that the driver does not take into
account properly the (possibly large) shared info size when selecting
the ring layout, and will try to fit two packets inside the same 4K
page even when the 1st fraglist will trump over the 2nd head.

Address the issue by checking if 2K buffers are insufficient.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2024-45030?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-45030?

Apply the vendor's patch.

## Is CVE-2024-45030 being exploited?

There is no known exploitation of CVE-2024-45030 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-2024-45030 and fix it if it is affected.

What it is: CVE-2024-45030 is a critical memory corruption vulnerability in Linux kernel, published on 11 Sep 2024. 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-2024-45030 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-2024-45030/ (Markdown: https://insights.sbomify.com/CVE-2024-45030/index.md)
```

## Sources

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

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