{"api_version":"1","generated_at":"2026-08-22T15:54:04+00:00","cve":"CVE-2026-72127","urls":{"html":"https://cve.report/CVE-2026-72127","api":"https://cve.report/api/cve/CVE-2026-72127.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-72127","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-72127"},"summary":{"title":"netdev-genl: report NAPI thread PID in the caller's pid namespace","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetdev-genl: report NAPI thread PID in the caller's 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's 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's pid namespace, the same way commit\n3799c2570982 (\"io_uring/fdinfo: translate SqThread PID through caller's\npid_ns\") did for the io_uring SQPOLL thread. The doit and dumpit paths both\nrun synchronously in the caller's context, so task_active_pid_ns(current) is\nthe caller's pid namespace.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 06:21:30","updated_at":"2026-08-17 06:18:12"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/fb18095389fe81f140d39585a2624aca9d42227e","name":"https://git.kernel.org/stable/c/fb18095389fe81f140d39585a2624aca9d42227e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/fd750b694f1f9e1ecb8ca19314e4e21edbb15f42","name":"https://git.kernel.org/stable/c/fd750b694f1f9e1ecb8ca19314e4e21edbb15f42","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/1f24c0d01db214c9e661915e9972404c96ca73c0","name":"https://git.kernel.org/stable/c/1f24c0d01db214c9e661915e9972404c96ca73c0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5e4c8e08ce95730c87d6ada0bdbe1131a3c06393","name":"https://git.kernel.org/stable/c/5e4c8e08ce95730c87d6ada0bdbe1131a3c06393","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-72127","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72127","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected db4704f4e4dfce835e934609fca735a648ce26e8 fb18095389fe81f140d39585a2624aca9d42227e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected db4704f4e4dfce835e934609fca735a648ce26e8 5e4c8e08ce95730c87d6ada0bdbe1131a3c06393 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected db4704f4e4dfce835e934609fca735a648ce26e8 fd750b694f1f9e1ecb8ca19314e4e21edbb15f42 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected db4704f4e4dfce835e934609fca735a648ce26e8 1f24c0d01db214c9e661915e9972404c96ca73c0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.8","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.8 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.97 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.40 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.5 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"72127","cve":"CVE-2026-72127","epss":"0.002000000","percentile":"0.101640000","score_date":"2026-08-17","updated_at":"2026-08-18 00:11:47"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/core/netdev-genl.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"fb18095389fe81f140d39585a2624aca9d42227e","status":"affected","version":"db4704f4e4dfce835e934609fca735a648ce26e8","versionType":"git"},{"lessThan":"5e4c8e08ce95730c87d6ada0bdbe1131a3c06393","status":"affected","version":"db4704f4e4dfce835e934609fca735a648ce26e8","versionType":"git"},{"lessThan":"fd750b694f1f9e1ecb8ca19314e4e21edbb15f42","status":"affected","version":"db4704f4e4dfce835e934609fca735a648ce26e8","versionType":"git"},{"lessThan":"1f24c0d01db214c9e661915e9972404c96ca73c0","status":"affected","version":"db4704f4e4dfce835e934609fca735a648ce26e8","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/core/netdev-genl.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.8"},{"lessThan":"6.8","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.97","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.40","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.97","versionStartIncluding":"6.8","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.40","versionStartIncluding":"6.8","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.5","versionStartIncluding":"6.8","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"6.8","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetdev-genl: report NAPI thread PID in the caller's 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's 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's pid namespace, the same way commit\n3799c2570982 (\"io_uring/fdinfo: translate SqThread PID through caller's\npid_ns\") did for the io_uring SQPOLL thread. The doit and dumpit paths both\nrun synchronously in the caller's context, so task_active_pid_ns(current) is\nthe caller's pid namespace."}],"providerMetadata":{"dateUpdated":"2026-08-17T05:08:42.273Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/fb18095389fe81f140d39585a2624aca9d42227e"},{"url":"https://git.kernel.org/stable/c/5e4c8e08ce95730c87d6ada0bdbe1131a3c06393"},{"url":"https://git.kernel.org/stable/c/fd750b694f1f9e1ecb8ca19314e4e21edbb15f42"},{"url":"https://git.kernel.org/stable/c/1f24c0d01db214c9e661915e9972404c96ca73c0"}],"title":"netdev-genl: report NAPI thread PID in the caller's pid namespace","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-72127","datePublished":"2026-08-15T05:53:04.405Z","dateReserved":"2026-08-09T03:40:39.907Z","dateUpdated":"2026-08-17T05:08:42.273Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 06:21:30","lastModifiedDate":"2026-08-17 06:18:12","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"72127","Ordinal":"1","Title":"netdev-genl: report NAPI thread PID in the caller's pid namespac","CVE":"CVE-2026-72127","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"72127","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetdev-genl: report NAPI thread PID in the caller's 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's 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's pid namespace, the same way commit\n3799c2570982 (\"io_uring/fdinfo: translate SqThread PID through caller's\npid_ns\") did for the io_uring SQPOLL thread. The doit and dumpit paths both\nrun synchronously in the caller's context, so task_active_pid_ns(current) is\nthe caller's pid namespace.","Type":"Description","Title":"netdev-genl: report NAPI thread PID in the caller's pid namespac"}]}}}