Answer in brief
CVE-2026-72127 records a Unknown severity vulnerability in netdev-genl: report NAPI thread PID in the caller's pid namespace. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=db4704f4e4dfce835e934609fca735a648ce26e8 <fb18095389fe81f140d39585a2624aca9d42227e || >=db4704f4e4dfce835e934609fca735a648ce26e8 <5e4c8e08ce95730c87d6ada0bdbe1131a3c06393 || >=db4704f4e4dfce835e934609fca735a648ce26e8 <fd750b694f1f9e1ecb8ca19314e4e21edbb15f42 || >=db4704f4e4dfce835e934609fca735a648ce26e8 <1f24c0d01db214c9e661915e9972404c96ca73c0 | fb18095389fe81f140d39585a2624aca9d42227e, 5e4c8e08ce95730c87d6ada0bdbe1131a3c06393, fd750b694f1f9e1ecb8ca19314e4e21edbb15f42, 1f24c0d01db214c9e661915e9972404c96ca73c0 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72127 records a Unknown severity vulnerability in netdev-genl: report NAPI thread PID in the caller's pid namespace. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=db4704f4e4dfce835e934609fca735a648ce26e8 <fb18095389fe81f140d39585a2624aca9d42227e || >=db4704f4e4dfce835e934609fca735a648ce26e8 <5e4c8e08ce95730c87d6ada0bdbe1131a3c06393 || >=db4704f4e4dfce835e934609fca735a648ce26e8 <fd750b694f1f9e1ecb8ca19314e4e21edbb15f42 || >=db4704f4e4dfce835e934609fca735a648ce26e8 <1f24c0d01db214c9e661915e9972404c96ca73c0 | fb18095389fe81f140d39585a2624aca9d42227e, 5e4c8e08ce95730c87d6ada0bdbe1131a3c06393, fd750b694f1f9e1ecb8ca19314e4e21edbb15f42, 1f24c0d01db214c9e661915e9972404c96ca73c0 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 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.
Quoted source text, attributed separately from HOL analysis.