{"vulnerability": "CVE-2025-21686", "sightings": [{"uuid": "33840a03-f29a-43b3-832a-54d98bd2f5b5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21686", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhtk5rexfe2i", "content": "", "creation_timestamp": "2025-02-10T16:16:22.848440Z"}, {"uuid": "24d342ce-02d8-4d1b-b850-5fd52b880bdd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21686", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113980598265852945", "content": "", "creation_timestamp": "2025-02-10T16:45:06.498013Z"}, {"uuid": "24c0d8bf-ea6b-4d12-94d0-3d76d8609d15", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21686", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lhtx7ownt52n", "content": "", "creation_timestamp": "2025-02-10T20:10:11.609181Z"}, {"uuid": "51e65d30-8279-4977-b54c-824c26a3b453", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21686", "type": "seen", "source": "https://t.me/cvedetector/17574", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21686 - Linux Kernel io_uring Unprivileged Memory Corruption Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21686 \nPublished : Feb. 10, 2025, 4:15 p.m. | 1\u00a0hour, 27\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nio_uring/rsrc: require cloned buffers to share accounting contexts  \n  \nWhen IORING_REGISTER_CLONE_BUFFERS is used to clone buffers from uring  \ninstance A to uring instance B, where A and B use different MMs for  \naccounting, the accounting can go wrong:  \nIf uring instance A is closed before uring instance B, the pinned memory  \ncounters for uring instance B will be decremented, even though the pinned  \nmemory was originally accounted through uring instance A; so the MM of  \nuring instance B can end up with negative locked memory. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"10 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-10T18:45:49.000000Z"}]}