Answer in brief
CVE-2024-45030 records a Unknown severity vulnerability in igb: cope with large MAX_SKB_FRAGS. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3948b05950fdd64002a5f182c65ba5cf2d53cf71 <8ea80ff5d8298356d28077bc30913ed37df65109 || >=3948b05950fdd64002a5f182c65ba5cf2d53cf71 <b52bd8bcb9e8ff250c79b44f9af8b15cae8911ab || >=3948b05950fdd64002a5f182c65ba5cf2d53cf71 <8aba27c4a5020abdf60149239198297f88338a8d | 8ea80ff5d8298356d28077bc30913ed37df65109, b52bd8bcb9e8ff250c79b44f9af8b15cae8911ab, 8aba27c4a5020abdf60149239198297f88338a8d |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Sep 11, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-45030 records a Unknown severity vulnerability in igb: cope with large MAX_SKB_FRAGS. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3948b05950fdd64002a5f182c65ba5cf2d53cf71 <8ea80ff5d8298356d28077bc30913ed37df65109 || >=3948b05950fdd64002a5f182c65ba5cf2d53cf71 <b52bd8bcb9e8ff250c79b44f9af8b15cae8911ab || >=3948b05950fdd64002a5f182c65ba5cf2d53cf71 <8aba27c4a5020abdf60149239198297f88338a8d | 8ea80ff5d8298356d28077bc30913ed37df65109, b52bd8bcb9e8ff250c79b44f9af8b15cae8911ab, 8aba27c4a5020abdf60149239198297f88338a8d |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Sep 11, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.