Skip to content
Heist/ feed
Back to feed
UnratedFix available

netdev-genl: report NAPI thread PID in the caller's pid namespace

Type: advisorySources: OSV

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.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.12.97, 6.18.40, 7.1.5
CVEs
CVE-2026-72127
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 04:44 UTC · Revision 1

Source evidence

netdev-genl: report NAPI thread PID in the caller's pid namespace

core-osv · Original source

Published 15 Aug 2026, 05:53 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.

osv:CVE-2026-72127

Kernel

Fixed versions: 6.12.97, 6.18.40, 7.1.5

Complete source record
{
  "id": "e9f44b6cc8c528450c83f6a071252aa98590b0a5bdfe8be06df948090e847d6f",
  "url": "https://osv.dev/vulnerability/CVE-2026-72127",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "netdev-genl: report NAPI thread PID in the caller's pid namespace",
    "summary": "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.",
    "evidence": "osv:CVE-2026-72127",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.12.97",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.40",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "7.1.5",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-72127",
      "aliases": [
        "CVE-2026-72127"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "db4704f4e4dfce835e934609fca735a648ce26e8"
                },
                {
                  "fixed": "fb18095389fe81f140d39585a2624aca9d42227e"
                },
                {
                  "fixed": "5e4c8e08ce95730c87d6ada0bdbe1131a3c06393"
                },
                {
                  "fixed": "fd750b694f1f9e1ecb8ca19314e4e21edbb15f42"
                },
                {
                  "fixed": "1f24c0d01db214c9e661915e9972404c96ca73c0"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-72127.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.8.0"
                },
                {
                  "fixed": "6.12.97"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.18.40"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "7.1.5"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-72127.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:25.865178836Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/1f24c0d01db214c9e661915e9972404c96ca73c0",
        "https://git.kernel.org/stable/c/5e4c8e08ce95730c87d6ada0bdbe1131a3c06393",
        "https://git.kernel.org/stable/c/fb18095389fe81f140d39585a2624aca9d42227e",
        "https://git.kernel.org/stable/c/fd750b694f1f9e1ecb8ca19314e4e21edbb15f42",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/72xxx/CVE-2026-72127.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-72127",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/72xxx/CVE-2026-72127.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-72127",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 492559,
  "published_at": "2026-08-15T05:53:04.405+00:00"
}