{"vulnerability": "CVE-2023-53133", "sightings": [{"uuid": "b251ea8c-f604-4f65-bfc2-510bc70323e3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-53133", "type": "seen", "source": "https://t.me/cvedetector/24364", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-53133 - Apache Linux bpf Infinite Loop Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-53133 \nPublished : May 2, 2025, 4:15 p.m. | 1\u00a0hour, 4\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf, sockmap: Fix an infinite loop error when len is 0 in tcp_bpf_recvmsg_parser()  \n  \nWhen the buffer length of the recvmsg system call is 0, we got the  \nflollowing soft lockup problem:  \n  \nwatchdog: BUG: soft lockup - CPU#3 stuck for 27s! [a.out:6149]  \nCPU: 3 PID: 6149 Comm: a.out Kdump: loaded Not tainted 6.2.0+ #30  \nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014  \nRIP: 0010:remove_wait_queue+0xb/0xc0  \nCode: 5e 41 5f c3 cc cc cc cc 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 41 57 <4156 41 55 41 54 55 48 89 fd 53 48 89 f3 4c 8d 6b 18 4c 8d 73 20  \nRSP: 0018:ffff88811b5978b8 EFLAGS: 00000246  \nRAX: 0000000000000000 RBX: ffff88811a7d3780 RCX: ffffffffb7a4d768  \nRDX: dffffc0000000000 RSI: ffff88811b597908 RDI: ffff888115408040  \nRBP: 1ffff110236b2f1b R08: 0000000000000000 R09: ffff88811a7d37e7  \nR10: ffffed10234fa6fc R11: 0000000000000001 R12: ffff88811179b800  \nR13: 0000000000000001 R14: ffff88811a7d38a8 R15: ffff88811a7d37e0  \nFS:  00007f6fb5398740(0000) GS:ffff888237180000(0000) knlGS:0000000000000000  \nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \nCR2: 0000000020000000 CR3: 000000010b6ba002 CR4: 0000000000370ee0  \nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  \nCall Trace:  \n   \n tcp_msg_wait_data+0x279/0x2f0  \n tcp_bpf_recvmsg_parser+0x3c6/0x490  \n inet_recvmsg+0x280/0x290  \n sock_recvmsg+0xfc/0x120  \n ____sys_recvmsg+0x160/0x3d0  \n ___sys_recvmsg+0xf0/0x180  \n __sys_recvmsg+0xea/0x1a0  \n do_syscall_64+0x3f/0x90  \n entry_SYSCALL_64_after_hwframe+0x72/0xdc  \n  \nThe logic in tcp_bpf_recvmsg_parser is as follows:  \n  \nmsg_bytes_ready:  \n copied = sk_msg_recvmsg(sk, psock, msg, len, flags);  \n if (!copied) {  \n  wait data;  \n  goto msg_bytes_ready;  \n }  \n  \nIn this case, \"copied\" always is 0, the infinite loop occurs.  \n  \nAccording to the Linux system call man page, 0 should be returned in this  \ncase. Therefore, in tcp_bpf_recvmsg_parser(), if the length is 0, directly  \nreturn. Also modify several other functions with the same problem. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T20:07:53.000000Z"}, {"uuid": "f4c431ad-a95f-4816-b05c-a0143e0804a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-53133", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "66c2d78d-4e85-4176-a2bc-7a873def019c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-53133", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo7mr52jgp2t", "content": "", "creation_timestamp": "2025-05-02T20:06:11.001210Z"}]}