CVE-2026-80616 ieee802154: Avoid calling WARN_ON() on -ENOMEM in cfg802154_switch_netns()
Not scored
Published
Updated
Check this codebase for CVE-2026-80616 and fix it if it is affected.
What it is: CVE-2026-80616 is a vulnerability in Linux, published on 28 Aug 2026.
Exploitation: There is no known exploitation of CVE-2026-80616 in the wild and no public exploit code.
Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-80616/ (Markdown: https://insights.sbomify.com/CVE-2026-80616/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-80616?
CVE-2026-80616 is a vulnerability in Linux, published on 28 Aug 2026.
Official description
In the Linux kernel, the following vulnerability has been resolved:
ieee802154: Avoid calling WARN_ON() on -ENOMEM in cfg802154_switch_netns()
It's pointless to call WARN_ON() in case of an allocation failure in dev_change_net_namespace() and device_rename(), since it only leads to useless splats caused by deliberate fault injections, so avoid it.
Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
Which versions are affected by CVE-2026-80616?
How do I fix CVE-2026-80616?
Upgrade to a fixed version.
Is CVE-2026-80616 being exploited?
There is no known exploitation of CVE-2026-80616 in the wild and no public exploit code.
Sources
Also known as AZL-98186, BELL-CVE-2026-80616, DEBIAN-CVE-2026-80616, GHSA-hccx-rj7h-28cw, UBUNTU-CVE-2026-80616.