{"vulnerability": "CVE-2022-48819", "sightings": [{"uuid": "e609a5bf-d426-4f4d-bed1-a29c1ee97995", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-48819", "type": "seen", "source": "https://t.me/cvedetector/945", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2022-48819 - \"The Linux Kernel TCP MSG_ZEROCOPY Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2022-48819 \nPublished : July 16, 2024, 12:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ntcp: take care of mixed splice()/sendmsg(MSG_ZEROCOPY) case  \n  \nsyzbot found that mixing sendpage() and sendmsg(MSG_ZEROCOPY)  \ncalls over the same TCP socket would again trigger the  \ninfamous warning in inet_sock_destruct()  \n  \n WARN_ON(sk_forward_alloc_get(sk));  \n  \nWhile Talal took into account a mix of regular copied data  \nand MSG_ZEROCOPY one in the same skb, the sendpage() path  \nhas been forgotten.  \n  \nWe want the charging to happen for sendpage(), because  \npages could be coming from a pipe. What is missing is the  \ndowngrading of pure zerocopy status to make sure  \nsk_forward_alloc will stay synced.  \n  \nAdd tcp_downgrade_zcopy_pure() helper so that we can  \nuse it from the two callers. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-16T15:26:34.000000Z"}]}