{"vulnerability": "CVE-2024-56372", "sightings": [{"uuid": "fda90941-a13f-4ca3-95aa-5a4effab564e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56372", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfhs63ifyk2m", "content": "", "creation_timestamp": "2025-01-11T13:17:23.224015Z"}, {"uuid": "c6007489-7480-409d-adba-2311fe2eb62a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56372", "type": "seen", "source": "https://t.me/cvedetector/15071", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56372 - Linux Tun Network Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56372 \nPublished : Jan. 11, 2025, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: tun: fix tun_napi_alloc_frags()  \n  \nsyzbot reported the following crash [1]  \n  \nIssue came with the blamed commit. Instead of going through  \nall the iov components, we keep using the first one  \nand end up with a malformed skb.  \n  \n[1]  \n  \nkernel BUG at net/core/skbuff.c:2849 !  \nOops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI  \nCPU: 0 UID: 0 PID: 6230 Comm: syz-executor132 Not tainted 6.13.0-rc1-syzkaller-00407-g96b6fcc0ee41 #0  \nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024  \n RIP: 0010:__pskb_pull_tail+0x1568/0x1570 net/core/skbuff.c:2848  \nCode: 38 c1 0f 8c 32 f1 ff ff 4c 89 f7 e8 92 96 74 f8 e9 25 f1 ff ff e8 e8 ae 09 f8 48 8b 5c 24 08 e9 eb fb ff ff e8 d9 ae 09 f8 90 <0f0b 66 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90  \nRSP: 0018:ffffc90004cbef30 EFLAGS: 00010293  \nRAX: ffffffff8995c347 RBX: 00000000fffffff2 RCX: ffff88802cf45a00  \nRDX: 0000000000000000 RSI: 00000000fffffff2 RDI: 0000000000000000  \nRBP: ffff88807df0c06a R08: ffffffff8995b084 R09: 1ffff1100fbe185c  \nR10: dffffc0000000000 R11: ffffed100fbe185d R12: ffff888076e85d50  \nR13: ffff888076e85c80 R14: ffff888076e85cf4 R15: ffff888076e85c80  \nFS:  00007f0dca6ea6c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000  \nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \nCR2: 00007f0dca6ead58 CR3: 00000000119da000 CR4: 00000000003526f0  \nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  \nCall Trace:  \n   \n  skb_cow_data+0x2da/0xcb0 net/core/skbuff.c:5284  \n  tipc_aead_decrypt net/tipc/crypto.c:894 [inline]  \n  tipc_crypto_rcv+0x402/0x24e0 net/tipc/crypto.c:1844  \n  tipc_rcv+0x57e/0x12a0 net/tipc/node.c:2109  \n  tipc_l2_rcv_msg+0x2bd/0x450 net/tipc/bearer.c:668  \n  __netif_receive_skb_list_ptype net/core/dev.c:5720 [inline]  \n  __netif_receive_skb_list_core+0x8b7/0x980 net/core/dev.c:5762  \n  __netif_receive_skb_list net/core/dev.c:5814 [inline]  \n  netif_receive_skb_list_internal+0xa51/0xe30 net/core/dev.c:5905  \n  gro_normal_list include/net/gro.h:515 [inline]  \n  napi_complete_done+0x2b5/0x870 net/core/dev.c:6256  \n  napi_complete include/linux/netdevice.h:567 [inline]  \n  tun_get_user+0x2ea0/0x4890 drivers/net/tun.c:1982  \n  tun_chr_write_iter+0x10d/0x1f0 drivers/net/tun.c:2057  \n do_iter_readv_writev+0x600/0x880  \n  vfs_writev+0x376/0xba0 fs/read_write.c:1050  \n  do_writev+0x1b6/0x360 fs/read_write.c:1096  \n  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  \n  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  \n entry_SYSCALL_64_after_hwframe+0x77/0x7f \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"11 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-11T14:55:24.000000Z"}]}