{"uuid": "924748ae-b139-426d-907f-9ddb41e62bc5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-42083", "type": "seen", "source": "https://t.me/cvedetector/1878", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42083 - Intel ionic Kernel Panic Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42083 \nPublished : July 29, 2024, 4:15 p.m. | 26\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nionic: fix kernel panic due to multi-buffer handling  \n  \nCurrently, the ionic_run_xdp() doesn't handle multi-buffer packets  \nproperly for XDP_TX and XDP_REDIRECT.  \nWhen a jumbo frame is received, the ionic_run_xdp() first makes xdp  \nframe with all necessary pages in the rx descriptor.  \nAnd if the action is either XDP_TX or XDP_REDIRECT, it should unmap  \ndma-mapping and reset page pointer to NULL for all pages, not only the  \nfirst page.  \nBut it doesn't for SG pages. So, SG pages unexpectedly will be reused.  \nIt eventually causes kernel panic.  \n  \nOops: general protection fault, probably for non-canonical address 0x504f4e4dbebc64ff: 0000 [#1] PREEMPT SMP NOPTI  \nCPU: 3 PID: 0 Comm: swapper/3 Not tainted 6.10.0-rc3+ #25  \nRIP: 0010:xdp_return_frame+0x42/0x90  \nCode: 01 75 12 5b 4c 89 e6 5d 31 c9 41 5c 31 d2 41 5d e9 73 fd ff ff 44 8b 6b 20 0f b7 43 0a 49 81 ed 68 01 00 00 49 29 c5 49 01 fd  80 7d0  \nRSP: 0018:ffff99d00122ce08 EFLAGS: 00010202  \nRAX: 0000000000005453 RBX: ffff8d325f904000 RCX: 0000000000000001  \nRDX: 00000000670e1000 RSI: 000000011f90d000 RDI: 504f4e4d4c4b4a49  \nRBP: ffff99d003907740 R08: 0000000000000000 R09: 0000000000000000  \nR10: 000000011f90d000 R11: 0000000000000000 R12: ffff8d325f904010  \nR13: 504f4e4dbebc64fd R14: ffff8d3242b070c8 R15: ffff99d0039077c0  \nFS:  0000000000000000(0000) GS:ffff8d399f780000(0000) knlGS:0000000000000000  \nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \nCR2: 00007f41f6c85e38 CR3: 000000037ac30000 CR4: 00000000007506f0  \nPKRU: 55555554  \nCall Trace:  \n   \n ? die_addr+0x33/0x90  \n ? exc_general_protection+0x251/0x2f0  \n ? asm_exc_general_protection+0x22/0x30  \n ? xdp_return_frame+0x42/0x90  \n ionic_tx_clean+0x211/0x280 [ionic 15881354510e6a9c655c59c54812b319ed2cd015]  \n ionic_tx_cq_service+0xd3/0x210 [ionic 15881354510e6a9c655c59c54812b319ed2cd015]  \n ionic_txrx_napi+0x41/0x1b0 [ionic 15881354510e6a9c655c59c54812b319ed2cd015]  \n __napi_poll.constprop.0+0x29/0x1b0  \n net_rx_action+0x2c4/0x350  \n handle_softirqs+0xf4/0x320  \n irq_exit_rcu+0x78/0xa0  \n common_interrupt+0x77/0x90 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T18:48:30.000000Z"}