Description
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.
Published: 2026-08-15
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

In the Linux kernel, the netdev-genl subsystem reports the NAPI kthread PID using task_pid_nr(). That function returns the PID in the initial, global pid namespace instead of translating it to the caller’s namespace. The NETDEV_CMD_NAPI_GET command lacks GENL_ADMIN_PERM and the netdev genl family is marked netnsok, allowing a process inside a child pid namespace to invoke it. Consequently, the caller receives the global PID of a kernel NAPI thread, even though that thread is invisible in its own namespace where the correct value should be zero. This exposes kernel thread identifiers that should remain opaque to the caller, constituting an information‑exposure vulnerability.

Affected Systems

The issue exists in the Linux kernel itself. Any host running an unpatched kernel that contains the netdev‑genl implementation is affected. Because no specific kernel version range is indicated, the entire distribution is potentially vulnerable until the namespace‑translation fix is incorporated into an released kernel revision.

Risk and Exploitability

The EPSS score is less than 1 % and the vulnerability is not listed in the CISA KEV catalog, indicating no publicly known exploitation. The likely attack vector is a local process capable of creating or entering a child pid namespace—a capability broadly available on Linux systems. The vulnerability is local and does not require remote interaction. The CVSS score of 5.5 assigns a moderate severity, but the low EPSS and lack of exposure to remote users suggest the overall risk is low.

Generated by OpenCVE AI on August 18, 2026 at 04:42 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the kernel to a release that incorporates the namespace‑translation fix.
  • If an upgrade is not yet available, restrict NETDEV_CMD_NAPI_GET by applying SELinux, AppArmor, or capabilities policies that limit access to netdev commands in non‑privileged namespaces.
  • Prevent unprivileged users from creating child PID namespaces by disabling user namespaces or adjusting relevant sysctl settings.

Generated by OpenCVE AI on August 18, 2026 at 04:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 18 Aug 2026 03:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
CWE-284

Tue, 18 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-272
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low


Sat, 15 Aug 2026 21:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
CWE-284

Sat, 15 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Description 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.
Title netdev-genl: report NAPI thread PID in the caller's pid namespace
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T05:08:42.273Z

Reserved: 2026-08-09T03:40:39.907Z

Link: CVE-2026-72127

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:21:30.113

Modified: 2026-08-17T06:18:12.363

Link: CVE-2026-72127

cve-icon Redhat

Severity : Low

Publid Date: 2026-08-15T00:00:00Z

Links: CVE-2026-72127 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T04:45:04Z

Weaknesses
  • CWE-272

    Least Privilege Violation