{"uuid": "28a97d4b-fff9-4ebc-b828-afc2423282d2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21893", "type": "seen", "source": "https://t.me/cvedetector/21651", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21893 - Linux Kernel Keyring Use After Free (UAF) Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21893 \nPublished : March 31, 2025, 8:15 p.m. | 51\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nkeys: Fix UAF in key_put()  \n  \nOnce a key's reference count has been reduced to 0, the garbage collector  \nthread may destroy it at any time and so key_put() is not allowed to touch  \nthe key after that point.  The most key_put() is normally allowed to do is  \nto touch key_gc_work as that's a static global variable.  \n  \nHowever, in an effort to speed up the reclamation of quota, this is now  \ndone in key_put() once the key's usage is reduced to 0 - but now the code  \nis looking at the key after the deadline, which is forbidden.  \n  \nFix this by using a flag to indicate that a key can be gc'd now rather than  \nlooking at the key's refcount in the garbage collector. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"31 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-31T23:23:54.000000Z"}