# CVE-2026-97410: netconsole: take target_cleanup_list_lock in drop_netconsole_target()

> A race condition in the Linux kernel netconsole module can cause list corruption and system crashes when targets are removed concurrently with cleanup operations.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** AZL-103766, BELL-CVE-2026-97410, DEBIAN-CVE-2026-97410, GHSA-m57g-35wp-4xgr, UBUNTU-CVE-2026-97410

## What is CVE-2026-97410?

CVE-2026-97410 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

netconsole: take target_cleanup_list_lock in drop_netconsole_target()

drop_netconsole_target() unlinks the target while only holding
target_list_lock. However, when the underlying interface has been
unregistered, netconsole_netdev_event() moves the target from
target_list to target_cleanup_list, and netconsole_process_cleanups_core()
walks that list under target_cleanup_list_lock only.

If a user removes the configfs target at the same time the cleanup
worker is iterating target_cleanup_list, list_del() can corrupt the list
because the two paths take disjoint locks while operating on the same
list node.

Acquire target_cleanup_list_lock around the list_del() so the unlink is
serialised against netconsole_process_cleanups_core() regardless of
which list the target currently belongs to. The state transition that
downgrades STATE_DEACTIVATED to STATE_DISABLED is left intact and is
performed under the same combined locking, preserving the existing
ordering with resume_target().

## Which versions are affected by CVE-2026-97410?


## How do I fix CVE-2026-97410?

Apply the vendor's patch.

## Is CVE-2026-97410 being exploited?

There is no known exploitation of CVE-2026-97410 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97410 and fix it if it is affected.

What it is: CVE-2026-97410 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97410 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-97410/ (Markdown: https://insights.sbomify.com/CVE-2026-97410/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97410
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97410
- OSV: https://osv.dev/vulnerability/CVE-2026-97410

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97410/
Summaries are generated and may contain mistakes; the official description above is the record.