Bug 2516555 (CVE-2026-72127) - CVE-2026-72127 kernel: netdev-genl: report NAPI thread PID in the caller's pid namespace
Summary: CVE-2026-72127 kernel: netdev-genl: report NAPI thread PID in the caller's pi...
Keywords:
Status: NEW
Alias: CVE-2026-72127
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-15 06:18 UTC by OSIDB Bzimport
Modified: 2026-08-17 23:05 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-15 06:18:43 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.