{"uuid": "758fdcab-fa44-4f19-a535-5a441b447fbc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21676", "type": "seen", "source": "https://t.me/cvedetector/16953", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21676 - Linux Fec Network Driver Null Pointer Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21676 \nPublished : Jan. 31, 2025, 12:15 p.m. | 1\u00a0hour, 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: fec: handle page_pool_dev_alloc_pages error  \n  \nThe fec_enet_update_cbd function calls page_pool_dev_alloc_pages but did  \nnot handle the case when it returned NULL. There was a WARN_ON(!new_page)  \nbut it would still proceed to use the NULL pointer and then crash.  \n  \nThis case does seem somewhat rare but when the system is under memory  \npressure it can happen. One case where I can duplicate this with some  \nfrequency is when writing over a smbd share to a SATA HDD attached to an  \nimx6q.  \n  \nSetting /proc/sys/vm/min_free_kbytes to higher values also seems to solve  \nthe problem for my test case. But it still seems wrong that the fec driver  \nignores the memory allocation error and can crash.  \n  \nThis commit handles the allocation error by dropping the current packet. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"31 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-31T15:23:28.000000Z"}