CVE-2026-98173·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-after-free of iface in cifs_try_adding_channels() cifs_try_adding_channels() iterates ses->iface_list with list_for_each_entry_safe_from(), which captures the next entry (niface) under iface_lock. The loop body then drops iface_lock for the whole duration of cifs_ses_add_channel(). A concurrent interface refresh (SMB3_request_interfaces() -> parse_server_interfaces()) marks all ifaces inactive and removes and frees any that are not re-advertised via list_del() + kref_put(), where release_iface() is a bare kfree(). Since niface typically has no channel holding a reference, the list reference is its last and it can be freed inside the unlocked window. On continue, the iterator advance step then dereferences niface->iface_head.next, and the loop body reads iface->rdma_capable/is_active, both on freed memory. Fix this by never keeping an unreferenced list pointer across the unlocked window. Each channel attempt now re-scans the list from the head under iface_lock, takes a kref on the selected candidate, and passes only that referenced candidate to cifs_ses_add_channel(). weight_fulfilled still tracks selection progress, so restarting the scan preserves the original weighted distribution and the weight_fulfilled-before-kref_put ordering on the failure path. Add a per-pass attempts cap so a flapping interface refresh cannot keep the inner loop spinning within a single tries increment.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.12.112, 6.18.54, 7.2.8, 7.3
- Published
How to fix this CVE
Update your Linux kernel to address a use-after-free vulnerability in the SMB client channel management code. Users should upgrade to kernel 6.12.112, 6.18.54, 7.2.8 or later depending on their current branch, or install their distribution's patched kernel package to avoid potential memory corruption during concurrent interface refresh operations.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your kernel version with `uname -r` and compare against fixed versions (6.12.112, 6.18.54, 7.2.8, or 7.3+)
- Step 2: Verify SMB client is in use by checking for active CIFS mounts: `mount | grep cifs`
- Step 3: Review kernel logs for memory access violations or crashes in cifs_try_adding_channels(): `sudo dmesg | grep -i 'cifs\|use-after-free\|segfault'`
- Step 4: After patching, confirm the new kernel is active with `uname -r` and reboot if necessary: `sudo reboot`
FAQ
What is CVE-2026-98173?
This vulnerability is a use-after-free condition in the Linux kernel's SMB client that occurs when the kernel attempts to manage multiple SMB channels while simultaneously refreshing network interfaces. A freed memory pointer can be dereferenced, potentially leading to memory corruption or denial of service.
Is CVE-2026-98173 being actively exploited?
No, this vulnerability is not listed on the CISA KEV catalog and has no known public exploits available.
What versions of Kernel are affected by CVE-2026-98173?
Versions prior to 6.12.112 (6.12 branch), 6.18.54 (6.18 branch), 7.2.8 (7.2 branch), and mainline 7.3 are vulnerable. The exact affected range depends on your kernel branch.
How do I check if my server is vulnerable to CVE-2026-98173?
Run `uname -r` to get your kernel version, then verify it meets the fixed version threshold: 6.12.112+, 6.18.54+, 7.2.8+, or 7.3+. If your version is lower, your system is vulnerable.
Does Defensia detect CVE-2026-98173?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-98173 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-98173. Free for 1 server.
Get started free