{"vulnerability": "cve-2024-41007", "sightings": [{"uuid": "34d63819-451f-4c39-87a3-542e53559181", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41007", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"}, {"uuid": "2186d0b3-ca33-463b-a9fc-912e42849bc4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41007", "type": "seen", "source": "https://t.me/cvedetector/859", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41007 - Linux Kernel TCP Avoid Too Many Retransmit Packets Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-41007 \nPublished : July 15, 2024, 9:15 a.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ntcp: avoid too many retransmit packets  \n  \nIf a TCP socket is using TCP_USER_TIMEOUT, and the other peer  \nretracted its window to zero, tcp_retransmit_timer() can  \nretransmit a packet every two jiffies (2 ms for HZ=1000),  \nfor about 4 minutes after TCP_USER_TIMEOUT has 'expired'.  \n  \nThe fix is to make sure tcp_rtx_probe0_timed_out() takes  \nicsk->icsk_user_timeout into account.  \n  \nBefore blamed commit, the socket would not timeout after  \nicsk->icsk_user_timeout, but would use standard exponential  \nbackoff for the retransmits.  \n  \nAlso worth noting that before commit e89688e3e978 (\"net: tcp:  \nfix unexcepted socket die when snd_wnd is 0\"), the issue  \nwould last 2 minutes instead of 4. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-15T11:49:50.000000Z"}]}