CVE-2026-74608
Linux kernel vulnerability
- Published22 Aug 2026
Description
In the Linux kernel, the following vulnerability has been resolved: smb: client: Fix use-after-free in cifs_try_adding_channels() cifs_try_adding_channels() takes a temporary reference to an interface before dropping iface_lock. If cifs_ses_add_channel() fails, it drops that reference and then increments iface->weight_fulfilled. A concurrent interface list refresh can remove the list reference while channel creation is in progress. In that case, the failure-path kref_put() releases the last reference and frees iface. Updating weight_fulfilled afterward then accesses freed memory. Increment weight_fulfilled before dropping the temporary reference, keeping iface alive for the final access.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/1305eadc6a7d78a8d0a52eee29ddd2d9e8a27805
- https://git.kernel.org/stable/c/1ffacbadc14530e55b8d86f7b917524f6a0fb891
- https://git.kernel.org/stable/c/47dfac48bce7198ad4f1a388fc8c9491f878ac3b
- https://git.kernel.org/stable/c/4986410316b1ae0e63c6ce418e4eb196723626e7
- https://git.kernel.org/stable/c/64d7584e62ac8cdc750455c5fdc6008fc2de4f06
- https://git.kernel.org/stable/c/c292d4686f717c03e5022fc4ae7c782f39a94915
Frequently asked
Is CVE-2026-74608 being actively exploited?
CVE-2026-74608 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.70%.
How severe is CVE-2026-74608?
CVE-2026-74608 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.70% probability of exploitation.
How do I fix CVE-2026-74608?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-74608 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.