https://vulnerability.circl.lu/sightings/feed 2026-06-02T13:23:56.061129+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/d20e12bc-c1a4-497c-859b-c2df006dda19/export 2026-06-02T13:23:57.071499+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "d20e12bc-c1a4-497c-859b-c2df006dda19", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48821", "type": "seen", "source": "https://t.me/cvedetector/940", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48821 - Linux Kernel - Use-After-Free in fastrpc\", \n \"Content\": \"CVE ID : CVE-2022-48821 \nPublished : July 16, 2024, 12:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nmisc: fastrpc: avoid double fput() on failed usercopy \n \nIf the copy back to userland fails for the FASTRPC_IOCTL_ALLOC_DMA_BUFF \nioctl(), we shouldn't assume that 'buf->dmabuf' is still valid. In fact, \ndma_buf_fd() called fd_install() before, i.e. \"consumed\" one reference, \nleaving us with none. \n \nCalling dma_buf_put() will therefore put a reference we no longer own, \nleading to a valid file descritor table entry for an already released \n'file' object which is a straight use-after-free. \n \nSimply avoid calling dma_buf_put() and rely on the process exit code to \ndo the necessary cleanup, if needed, i.e. if the file descriptor is \nstill valid. \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:26.000000Z"} 2024-07-16T15:26:26+00:00