{"uuid": "ab4f0fc1-a2c8-4e86-b709-525fd1be378a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21981", "type": "seen", "source": "https://t.me/cvedetector/21782", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21981 - \"Ice: Memory Leak in aRFS after Reset\"\", \n  \"Content\": \"CVE ID : CVE-2025-21981 \nPublished : April 1, 2025, 4:15 p.m. | 1\u00a0hour, 15\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nice: fix memory leak in aRFS after reset  \n  \nFix aRFS (accelerated Receive Flow Steering) structures memory leak by  \nadding a checker to verify if aRFS memory is already allocated while  \nconfiguring VSI. aRFS objects are allocated in two cases:  \n- as part of VSI initialization (at probe), and  \n- as part of reset handling  \n  \nHowever, VSI reconfiguration executed during reset involves memory  \nallocation one more time, without prior releasing already allocated  \nresources. This led to the memory leak with the following signature:  \n  \n[root@os-delivery ~]# cat /sys/kernel/debug/kmemleak  \nunreferenced object 0xff3c1ca7252e6000 (size 8192):  \n  comm \"kworker/0:0\", pid 8, jiffies 4296833052  \n  hex dump (first 32 bytes):  \n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................  \n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................  \n  backtrace (crc 0):  \n    [] __kmalloc_cache_noprof+0x275/0x340  \n    [] ice_init_arfs+0x3a/0xe0 [ice]  \n    [] ice_vsi_cfg_def+0x607/0x850 [ice]  \n    [] ice_vsi_setup+0x5b/0x130 [ice]  \n    [] ice_init+0x1c1/0x460 [ice]  \n    [] ice_probe+0x2af/0x520 [ice]  \n    [] local_pci_probe+0x43/0xa0  \n    [] work_for_cpu_fn+0x13/0x20  \n    [] process_one_work+0x179/0x390  \n    [] worker_thread+0x239/0x340  \n    [] kthread+0xcc/0x100  \n    [] ret_from_fork+0x2d/0x50  \n    [] ret_from_fork_asm+0x1a/0x30  \n    ... \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-01T19:44:25.000000Z"}