Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-45030 | First vendor Publication | 2024-09-11 |
Vendor | Cve | Last vendor Modification | 2024-09-13 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | |||
---|---|---|---|
Overall CVSS Score | 5.5 | ||
Base Score | 5.5 | Environmental Score | 5.5 |
impact SubScore | 3.6 | Temporal Score | 5.5 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | None |
Integrity Impact | None | Availability Impact | High |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
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. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-45030 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-787 | Out-of-bounds Write (CWE/SANS Top 25) |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-03-29 03:40:10 |
|
2025-03-28 13:44:42 |
|
2025-03-28 03:18:20 |
|
2025-03-19 03:13:41 |
|
2025-03-18 03:26:37 |
|
2025-03-14 03:13:54 |
|
2025-03-06 14:10:26 |
|
2025-02-22 03:24:00 |
|
2025-01-08 03:05:02 |
|
2025-01-07 03:04:35 |
|
2024-12-25 03:03:13 |
|
2024-12-12 03:06:09 |
|
2024-11-23 03:03:10 |
|
2024-11-22 03:01:20 |
|
2024-11-20 02:59:40 |
|
2024-11-14 02:59:58 |
|
2024-11-09 02:59:58 |
|
2024-10-26 02:57:21 |
|
2024-10-25 02:59:14 |
|
2024-10-23 02:58:26 |
|
2024-10-03 02:53:37 |
|
2024-10-02 02:52:01 |
|
2024-09-14 21:29:44 |
|
2024-09-13 21:27:43 |
|
2024-09-11 21:27:24 |
|