CVE-2024-45030

9.8 CRITICAL 0.5% exploit odds Fix listed Memory safety OS & kernel

What it is

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.

At a glance

Exploitability: Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
Exploit odds: 0.5% chance of exploitation in the next 30 days (EPSS).
Fix: A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

2024-09-11 16:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-08-04 11:20 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 0.5% in the next 30 days (EPSS).
Severity: 9.8 CRITICAL (CVSS).
Fix: a patch or advisory is linked.

Details

Published: 2024-09-11 16:15 UTC
Last modified: 2026-08-04 11:20 UTC
Exploit probability: 0.5% · EPSS, next 30 days
Weakness: CWE-787 · Out-of-bounds write
Record status: Modified

Affected

Linux Kernel < 6.6.48
Linux Kernel < 6.10.7
Linux Kernel 6.11

Attack profile CVSS 3.1 · 9.8

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2024-45030.md and follow it. Check whether this project is affected by CVE-2024-45030. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record