{"uuid": "ce80500f-41cf-4dc3-873d-056707f962ba", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45030", "type": "seen", "source": "https://t.me/cvedetector/5372", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45030 - Intel igb Linux Kernel Fragment Corruption Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-45030 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nigb: cope with large MAX_SKB_FRAGS  \n  \nSabrina reports that the igb driver does not cope well with large  \nMAX_SKB_FRAG values: setting MAX_SKB_FRAG to 45 causes payload  \ncorruption on TX.  \n  \nAn easy reproducer is to run ssh to connect to the machine.  With  \nMAX_SKB_FRAGS=17 it works, with MAX_SKB_FRAGS=45 it fails.  This has  \nbeen reported originally in  \n  \n  \nThe root cause of the issue is that the driver does not take into  \naccount properly the (possibly large) shared info size when selecting  \nthe ring layout, and will try to fit two packets inside the same 4K  \npage even when the 1st fraglist will trump over the 2nd head.  \n  \nAddress the issue by checking if 2K buffers are insufficient. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"11 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:27.000000Z"}