CVE-2026-23453 | Linux Kernel up to 6.19.9/7.0-rc4 emac_run_xdp memory leak

VDB-355158 · CVE-2026-23453 · GCVE-0-2026-23453 LINUX KERNEL UP TO 6.19.9/7.0-RC4 EMAC_RUN_XDP MEMORY LEAK HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.5 $0-$5k 0.56 Summaryinfo A vulnerability was found in Linux Kernel up to 6.19.9/7.0-rc4. It has been declared as critical. Affected by this issue is the function emac_run_xdp. The manipulation results in memory leak. This vulnerability was named CVE-2026-23453. There is no available exploit. It is recommended to upgrade the affected component. Detailsinfo A vulnerability classified as critical has been found in Linux Kernel up to 6.19.9/7.0-rc4. Affected is the function emac_run_xdp. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on availability. CVE summarizes: In the Linux kernel, the following vulnerability has been resolved: net: ti: icssg-prueth: Fix memory leak in XDP_DROP for non-zero-copy mode Page recycling was removed from the XDP_DROP path in emac_run_xdp() to avoid conflicts with AF_XDP zero-copy mode, which uses xsk_buff_free() instead. However, this causes a memory leak when running XDP programs that drop packets in non-zero-copy mode (standard page pool mode). The pages are never returned to the page pool, leading to OOM conditions. Fix this by handling cleanup in the caller, emac_rx_packet(). When emac_run_xdp() returns ICSSG_XDP_CONSUMED for XDP_DROP, the caller now recycles the page back to the page pool. The zero-copy path, emac_rx_packet_zc() already handles cleanup correctly with xsk_buff_free(). The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2026-23453 since 01/13/2026. Technical details are known, but there is no available exploit. Upgrading to version 6.19.10 or 7.0-rc5 eliminates this vulnerability. Applying the patch d16d57dedcb69c1a1257e0638f8698ce1f0ccbe5/719d3e71691db7c4f1658ba5a6d1472928121594 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Type Operating System Vendor Linux Name Kernel Version 6.19.0 6.19.1 6.19.2 6.19.3 6.19.4 6.19.5 6.19.6 6.19.7 6.19.8 6.19.9 7.0-rc1 7.0-rc2 7.0-rc3 7.0-rc4 License open-source Website Vendor: https://www.kernel.org/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.7 VulDB Meta Temp Score: 5.5 VulDB Base Score: 5.7 VulDB Temp Score: 5.5 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Memory leak CWE: CWE-401 / CWE-404 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Partially Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: Kernel 6.19.10/7.0-rc5 Patch: d16d57dedcb69c1a1257e0638f8698ce1f0ccbe5/719d3e71691db7c4f1658ba5a6d1472928121594 Timelineinfo 01/13/2026 CVE reserved 04/03/2026 +79 days Advisory disclosed 04/03/2026 +0 days VulDB entry created 04/03/2026 +0 days VulDB entry last update Sourcesinfo Vendor: kernel.org Advisory: git.kernel.org Status: Confirmed CVE: CVE-2026-23453 (🔒) GCVE (CVE): GCVE-0-2026-23453 GCVE (VulDB): GCVE-100-355158 Entryinfo Created: 04/03/2026 18:16 Changes: 04/03/2026 18:16 (58) Complete: 🔍 Cache ID: 99:E10:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸