CVE-2026-72127
CVE CVE-2026-72127EUVD EUVD-2026-58885Published 2026-08-15T05:53:04.000ZLast changed 2026-08-17T05:08:42.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: netdev-genl: report NAPI thread PID in the caller's pid namespace netdev_nl_napi_fill_one() reports the NAPI kthread PID in NETDEV_A_NAPI_PID using task_pid_nr(), which returns the PID in the initial pid namespace. NETDEV_CMD_NAPI_GET does not have GENL_ADMIN_PERM and the netdev genl family is netnsok, so a caller in a child pid namespace can issue it. That caller then sees the kthread's global PID, even though the kthread is not visible in its pid namespace, where the value should be 0. Translate the PID through the caller's pid namespace, the same way commit 3799c2570982 ("io_uring/fdinfo: translate SqThread PID through caller's pid_ns") did for the io_uring SQPOLL thread. The doit and dumpit paths both run synchronously in the caller's context, so task_active_pid_ns(current) is the caller's pid namespace.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux db4704f4e4dfce835e934609fca735a648ce26e8 <1f24c0d01db214c9e661915e9972404c96ca73c0; db4704f4e4dfce835e934609fca735a648ce26e8 <fb18095389fe81f140d39585a2624aca9d42227e; 6.8; db4704f4e4dfce835e934609fca735a648ce26e8 <fd750b694f1f9e1ecb8ca19314e4e21edbb15f42; patch: 6.12.97; patch: 0; db4704f4e4dfce835e934609fca735a648ce26e8 <5e4c8e08ce95730c87d6ada0bdbe1131a3c06393; patch: 7.2; patch: 6.18.40; patch: 7.1.5
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.