{"uuid": "720afb48-f268-4722-974b-7c87f62b4570", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21726", "type": "seen", "source": "https://t.me/cvedetector/18977", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21726 - Linux Kernel padata Reorder Work Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21726 \nPublished : Feb. 27, 2025, 2:15 a.m. | 50\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \npadata: avoid UAF for reorder_work  \n  \nAlthough the previous patch can avoid ps and ps UAF for _do_serial, it  \ncan not avoid potential UAF issue for reorder_work. This issue can  \nhappen just as below:  \n  \ncrypto_request   crypto_request  crypto_del_alg  \npadata_do_serial  \n  ...  \n  padata_reorder  \n    // processes all remaining  \n    // requests then breaks  \n    while (1) {  \n      if (!padata)  \n        break;  \n      ...  \n    }  \n  \n    padata_do_serial  \n      // new request added  \n      list_add  \n    // sees the new request  \n    queue_work(reorder_work)  \n      padata_reorder  \n        queue_work_on(squeue->work)  \n...  \n  \n      \n    padata_serial_worker  \n    // completes new request,  \n    // no more outstanding  \n    // requests  \n  \n       crypto_del_alg  \n         // free pd  \n  \n  \ninvoke_padata_reorder  \n  // UAF of pd  \n  \nTo avoid UAF for 'reorder_work', get 'pd' ref before put 'reorder_work'  \ninto the 'serial_wq' and put 'pd' ref until the 'serial_wq' finish. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-27T04:30:10.000000Z"}