CVE-2026-72127
netdev-genl: report NAPI thread PID in the caller's pid namespace
Reported by linux · Published August 15, 2026
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.
EPSS 0.21% · 11.0th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.12 | Amazon Linux | 1:6.12.100-125.179.amzn2023 |
| microvm-kernel6.18 | Amazon Linux | 1:6.18.41-94.142.amzn2023 |
| python3-perf6.18 | Amazon Linux | 1:6.18.41-94.142.amzn2023 |
| kernel6.18-headers | Amazon Linux | 1:6.18.41-94.142.amzn2023 |
| perf6.12 | Amazon Linux | 1:6.12.100-125.179.amzn2023 |
| kernel6.12-devel | Amazon Linux | 1:6.12.100-125.179.amzn2023 |
| kernel6.12-modules-extra | Amazon Linux | 1:6.12.100-125.179.amzn2023 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | db4704f4e4dfce835e934609fca735a648ce26e8, db4704f4e4dfce835e934609fca735a648ce26e8, db4704f4e4dfce835e934609fca735a648ce26e8 |
| Linux | Linux | 6.8, 0, 6.12.97 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | microvm-kernel6.18 | 0 |
| amazon:2023 | python3-perf6.18 | 0 |
| amazon:2023 | kernel6.18-headers | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| linux | linux_kernel | 6.8, 6.8, 6.8 |
| amazon:2023 | kernel6.12-headers | 0 |
| Linux | Linux | 0, 6.8, * |
| amazon:2023 | kernel-livepatch-6.18.41-94.142 | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel-livepatch-6.12.100-125.179 | 0 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
| amazon:2023 | kernel6.18 | 0 |
| amazon:2023 | kernel6.12-tools | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| amazon:2023 | kernel6.18-devel | 0 |
…and 7 more
Timeline
- Aug 15, 2026 Coalition ESS Score
- Aug 15, 2026 CVE Published
- Aug 17, 2026 CVE Updated
- Aug 19, 2026 Security Advisory
- Aug 24, 2026 EPSS Score (14 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-72127
vulnetix vdb fixes CVE-2026-72127
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-72127/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart