{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72127 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72127 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-72127 and fix it if it is affected.\n\nWhat it is: CVE-2026-72127 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-72127 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-72127/ (Markdown: https://insights.sbomify.com/CVE-2026-72127/index.md)","id":"CVE-2026-72127","markdown":"https://insights.sbomify.com/CVE-2026-72127/index.md","name":"CVE-2026-72127","record":{"aliases":["BELL-CVE-2026-72127","DEBIAN-CVE-2026-72127","GHSA-hx9w-mw8p-76q2","UBUNTU-CVE-2026-72127"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker in a child PID namespace can leak global kernel thread PIDs via netdev-genl, bypassing namespace isolation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"netdev-genl: report NAPI thread PID in the caller's pid namespace","id":"CVE-2026-72127","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"nvmet: fix refcount leak in nvmet_sq_create()","id":"CVE-2026-72128"},"packages":[],"prev":{"headline":"can: isotp: use unconditional synchronize_rcu() in isotp_release()","id":"CVE-2026-72126"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A local attacker in a child PID namespace can leak global kernel thread PIDs via netdev-genl, bypassing namespace isolation.","url":"https://insights.sbomify.com/CVE-2026-72127/"}