Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-97410 Overview
CVE-2026-97410 is a race condition in the Linux kernel's netconsole subsystem. The flaw lives in drop_netconsole_target(), which unlinks a target while holding only target_list_lock. When the underlying network interface has been unregistered, netconsole_netdev_event() moves the target to target_cleanup_list, and netconsole_process_cleanups_core() walks that list under target_cleanup_list_lock. The two code paths take disjoint locks on the same list node, allowing concurrent list_del() operations to corrupt the list.
Critical Impact
Concurrent removal of a configfs netconsole target during cleanup worker execution can corrupt kernel linked-list state, leading to memory corruption or kernel panic.
Affected Products
- Linux kernel (netconsole subsystem)
- Distributions shipping affected mainline kernel versions prior to the stable patches
- Systems using netconsole with configfs-managed targets
Discovery Timeline
- 2026-09-24 - CVE-2026-97410 published to NVD
- 2026-09-25 - Last updated in NVD database
Technical Details for CVE-2026-97410
Vulnerability Analysis
The Linux kernel's netconsole driver maintains two lists of targets: target_list for active targets and target_cleanup_list for targets whose underlying interface has been unregistered. Each list is protected by its own spinlock. The function drop_netconsole_target() is invoked when a user removes a target through configfs, and it calls list_del() while holding only target_list_lock.
If the underlying network device is unregistered concurrently, netconsole_netdev_event() migrates the target node from target_list to target_cleanup_list. A kernel worker then invokes netconsole_process_cleanups_core(), which iterates target_cleanup_list under target_cleanup_list_lock. Because the configfs removal path and the cleanup worker operate on the same list node under different locks, their list_del() operations are not serialized.
This is a classic [CWE-362] race condition that can corrupt the doubly linked list's prev and next pointers. Downstream consequences include memory corruption, use-after-free of the target structure, and kernel panic.
Root Cause
The root cause is inconsistent lock coverage for a shared list node. The target structure can legally reside on either target_list or target_cleanup_list depending on interface state, but drop_netconsole_target() assumes only the former and acquires only target_list_lock. No check or coordination exists to ensure the cleanup worker is not simultaneously iterating the node.
Attack Vector
Exploitation requires local privileges sufficient to manipulate configfs netconsole entries, typically root or CAP_SYS_ADMIN. An attacker triggers the race by rapidly removing a netconsole target while the underlying network interface is being torn down. The window is narrow but reachable via scripted interface up/down cycles combined with configfs removals.
The fix acquires target_cleanup_list_lock around the list_del() in drop_netconsole_target(), serializing the unlink against netconsole_process_cleanups_core() regardless of which list the target currently belongs to. The state transition from STATE_DEACTIVATED to STATE_DISABLED is preserved under the combined locking, maintaining ordering with resume_target().
Technical details are available in the upstream fixes: Linux Kernel Stable Commit 84592ee2, Linux Kernel Stable Commit 91aeb87f, and Linux Kernel Stable Commit fe8e6c0a.
Detection Methods for CVE-2026-97410
Indicators of Compromise
- Kernel log messages referencing list_del corruption, list_add corruption, or general protection faults originating in netconsole symbols.
- Unexpected kernel panics or oopses in drop_netconsole_target or netconsole_process_cleanups_core call stacks.
- Repeated interface up/down events coinciding with configfs activity under /sys/kernel/config/netconsole/.
Detection Strategies
- Query installed kernel version against vendor advisories to identify unpatched hosts.
- Enable CONFIG_DEBUG_LIST on test kernels to surface list corruption early during fuzzing or regression testing.
- Monitor audit logs for processes writing to /sys/kernel/config/netconsole/*/enabled or removing target directories.
Monitoring Recommendations
- Forward kernel ring-buffer messages to a centralized logging platform and alert on list-corruption patterns.
- Track user-space tooling that programmatically manages netconsole targets, especially in automated remote-logging deployments.
- Correlate interface unregister events with configfs modifications to flag race-prone activity.
How to Mitigate CVE-2026-97410
Immediate Actions Required
- Apply the upstream stable kernel patches referenced in the kernel.org commits listed above.
- Inventory hosts running netconsole and prioritize patching systems that expose configfs management to automation.
- Restrict root and CAP_SYS_ADMIN to trusted administrators to reduce the attack surface for local race exploitation.
Patch Information
The fix is committed to the Linux stable tree in commits 84592ee22f7d1583ce33aa733411ff36c7a1c44c, 91aeb87f052367a5a2743cc93777dfb4386f2f14, and fe8e6c0a2f28bdab14cdf7eff4dd9755d3793007. Each patch modifies drop_netconsole_target() to acquire target_cleanup_list_lock around the list_del() call. Consume the fix through your distribution's kernel update channel or by rebuilding from a patched stable branch.
Workarounds
- Unload the netconsole module (modprobe -r netconsole) on systems that do not require remote kernel console logging.
- Avoid dynamic add/remove of netconsole targets concurrent with interface state changes until the patch is deployed.
- Limit write access to /sys/kernel/config/netconsole/ using filesystem permissions and mandatory access control policies such as SELinux or AppArmor.
# Verify kernel version and netconsole module status
uname -r
lsmod | grep netconsole
# Temporarily unload netconsole where not required
sudo modprobe -r netconsole
# Blacklist the module to prevent auto-load until patched
echo 'blacklist netconsole' | sudo tee /etc/modprobe.d/netconsole-blacklist.conf
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

