https://db.gcve.eu/sightings/feed 2026-10-01T22:39:16.885856+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent sightings. https://db.gcve.eu/sighting/4747be18-ca07-4a6d-b166-cec19ef9768e/export 2026-10-01T22:39:16.915873+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "4747be18-ca07-4a6d-b166-cec19ef9768e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-53121", "type": "seen", "source": "https://t.me/cvedetector/24365", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2023-53121 - Linux Kernel TCP Information Disclosure Vulnerability\", \n \"Content\": \"CVE ID : CVE-2023-53121 \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 \ntcp: tcp_make_synack() can be called from process context \n \ntcp_rtx_synack() now could be called in process context as explained in \n0a375c822497 (\"tcp: tcp_rtx_synack() can be called from process \ncontext\"). \n \ntcp_rtx_synack() might call tcp_make_synack(), which will touch per-CPU \nvariables with preemption enabled. This causes the following BUG: \n \n BUG: using __this_cpu_add() in preemptible [00000000] code: ThriftIO1/5464 \n caller is tcp_make_synack+0x841/0xac0 \n Call Trace: \n \n dump_stack_lvl+0x10d/0x1a0 \n check_preemption_disabled+0x104/0x110 \n tcp_make_synack+0x841/0xac0 \n tcp_v6_send_synack+0x5c/0x450 \n tcp_rtx_synack+0xeb/0x1f0 \n inet_rtx_syn_ack+0x34/0x60 \n tcp_check_req+0x3af/0x9e0 \n tcp_rcv_state_process+0x59b/0x2030 \n tcp_v6_do_rcv+0x5f5/0x700 \n release_sock+0x3a/0xf0 \n tcp_sendmsg+0x33/0x40 \n ____sys_sendmsg+0x2f2/0x490 \n __sys_sendmsg+0x184/0x230 \n do_syscall_64+0x3d/0x90 \n \nAvoid calling __TCP_INC_STATS() with will touch per-cpu variables. Use \nTCP_INC_STATS() which is safe to be called from context switch. \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:54.000000Z"} 2025-05-02T20:07:54+00:00