GHSA-HX9W-MW8P-76Q2
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32In 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.
{
"affected": [],
"aliases": [
"CVE-2026-72127"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:21:30Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnetdev-genl: report NAPI thread PID in the caller\u0027s pid namespace\n\nnetdev_nl_napi_fill_one() reports the NAPI kthread PID in NETDEV_A_NAPI_PID\nusing task_pid_nr(), which returns the PID in the initial pid namespace.\n\nNETDEV_CMD_NAPI_GET does not have GENL_ADMIN_PERM and the netdev genl family\nis netnsok, so a caller in a child pid namespace can issue it. That caller\nthen sees the kthread\u0027s global PID, even though the kthread is not visible\nin its pid namespace, where the value should be 0.\n\nTranslate the PID through the caller\u0027s pid namespace, the same way commit\n3799c2570982 (\"io_uring/fdinfo: translate SqThread PID through caller\u0027s\npid_ns\") did for the io_uring SQPOLL thread. The doit and dumpit paths both\nrun synchronously in the caller\u0027s context, so task_active_pid_ns(current) is\nthe caller\u0027s pid namespace.",
"id": "GHSA-hx9w-mw8p-76q2",
"modified": "2026-08-15T06:32:13Z",
"published": "2026-08-15T06:32:13Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72127"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1f24c0d01db214c9e661915e9972404c96ca73c0"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5e4c8e08ce95730c87d6ada0bdbe1131a3c06393"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fb18095389fe81f140d39585a2624aca9d42227e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fd750b694f1f9e1ecb8ca19314e4e21edbb15f42"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.