Linux
veth: fix NAPI leak in XDP enable error path
In the Linux kernel, the following vulnerability has been resolved: veth: fix NAPI leak in XDP enable error path During XDP enablement in veth, if xdp_rxq_info_reg() or xdp_rxq_info_reg_mem_model() fails, the driver rolls back the changes. However, the rollback loop: for (i--; i >= start; i--) { decrements the loop index 'i' before the first iteration. This correctly skips unregistering the rxq for the failed index 'i' (as registration failed or was already cleaned up), but it also erroneously skips calling netif_napi_deli() for rq[i].xdp_napi. Since netif_napi_add() was already called for index 'i', this leaves a dangling napi_struct in the device's napi_list. When the veth device is later destroyed, the freed queue memory (which contains the leaked NAPI structure) can be reused. The subsequent device teardown iterates the NAPI list and corrupts the reallocated memory, leading to UAF. Fix this by explicitly deleting the NAPI association for the failed index 'i' before rolling back the successfully configured queues.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= b02e5a0ebb172c8276cea3151942aac681f7a4a6, < fc51373345e7e6ea73da2650cb497309c50b077a
- >= b02e5a0ebb172c8276cea3151942aac681f7a4a6, < 4559770b2a241344d762719e674241fcc8528f02
- >= b02e5a0ebb172c8276cea3151942aac681f7a4a6, < 83090f5e7b54721d71875a6c224d2490b9e73050
- >= b02e5a0ebb172c8276cea3151942aac681f7a4a6, < d3eb258ad398cc9402bab3a5e730cd7c5b34efad
- >= b02e5a0ebb172c8276cea3151942aac681f7a4a6, < a9e6707322ef215d39d4655b176c094f45f0ab52
- >= b02e5a0ebb172c8276cea3151942aac681f7a4a6, < 4bd2e5dbe62334aae1182d0f0d260f334a49d739
- >= b02e5a0ebb172c8276cea3151942aac681f7a4a6, < 6739027cb72da26890edd424c77080d187b2a92e
Fixed in fc51373345e7e6ea73da2650cb497309c50b077a, 4559770b2a241344d762719e674241fcc8528f02, 83090f5e7b54721d71875a6c224d2490b9e73050, d3eb258ad398cc9402bab3a5e730cd7c5b34efad, a9e6707322ef215d39d4655b176c094f45f0ab52, 4bd2e5dbe62334aae1182d0f0d260f334a49d739, 6739027cb72da26890edd424c77080d187b2a92e
- 5.11
Fixed in 0, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5, 7.2
Mitigation
Upgrade Linux to fc51373345e7e6ea73da2650cb497309c50b077a or 4559770b2a241344d762719e674241fcc8528f02 or 83090f5e7b54721d71875a6c224d2490b9e73050 or d3eb258ad398cc9402bab3a5e730cd7c5b34efad or a9e6707322ef215d39d4655b176c094f45f0ab52 or 4bd2e5dbe62334aae1182d0f0d260f334a49d739 or 6739027cb72da26890edd424c77080d187b2a92e or later.
Upgrade Linux to 0 or 5.15.212 or 6.1.178 or 6.6.145 or 6.12.97 or 6.18.40 or 7.1.5 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.