CVE-2024-42256·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: cifs: Fix server re-repick on subrequest retry When a subrequest is marked for needing retry, netfs will call cifs_prepare_write() which will make cifs repick the server for the op before renegotiating credits; it then calls cifs_issue_write() which invokes smb2_async_writev() - which re-repicks the server. If a different server is then selected, this causes the increment of server->in_flight to happen against one record and the decrement to happen against another, leading to misaccounting. Fix this by just removing the repick code in smb2_async_writev(). As this is only called from netfslib-driven code, cifs_prepare_write() should always have been called first, and so server should never be NULL and the preparatory step is repeated in the event that we do a retry. The problem manifests as a warning looking something like: WARNING: CPU: 4 PID: 72896 at fs/smb/client/smb2ops.c:97 smb2_add_credits+0x3f0/0x9e0 [cifs] ... RIP: 0010:smb2_add_credits+0x3f0/0x9e0 [cifs] ... smb2_writev_callback+0x334/0x560 [cifs] cifs_demultiplex_thread+0x77a/0x11b0 [cifs] kthread+0x187/0x1d0 ret_from_fork+0x34/0x60 ret_from_fork_asm+0x1a/0x30 Which may be triggered by a number of different xfstests running against an Azure server in multichannel mode. generic/249 seems the most repeatable, but generic/215, generic/249 and generic/308 may also show it.
- Severity
- critical
- Software
- Kernel
- Fixed in
- 6.10.1
- Published
- 2024-08-08
Affected versions
From: 6.10
Until: 6.10.1
Fixed in: 6.10.1
How to fix this CVE
Update your Linux kernel to version 6.10.1 or later to resolve a critical server accounting flaw in CIFS multichannel operations. This vulnerability causes mismatched credit tracking when write subrequests are retried, potentially leading to kernel warnings and system instability. Affected systems running kernels 6.10 through 6.10.1 should prioritize this update immediately.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check installed kernel version: uname -r
- Verify if CIFS multichannel is in use: mount | grep -i cifs
- Search kernel logs for smb2_add_credits warnings: dmesg | grep -i 'smb2_add_credits\|WARNING.*fs/smb'
- After patching, confirm updated kernel version: uname -r (should be 6.10.1 or later)
FAQ
What is CVE-2024-42256?
CVE-2024-42256 is a critical Linux kernel vulnerability in CIFS (SMB) multichannel operations where server selection logic is incorrectly duplicated during subrequest retries, causing mismatched credit accounting that can trigger kernel warnings and destabilize file operations.
Is CVE-2024-42256 being actively exploited?
No, this vulnerability is not listed on the CISA KEV catalog and no public exploits are available. However, it can be triggered reliably through specific xfstests against Azure servers using multichannel mode.
What versions of Kernel are affected by CVE-2024-42256?
Linux kernel versions 6.10 through 6.10.1 are affected. The vulnerability was resolved in kernel 6.10.1 and later stable releases.
How do I check if my server is vulnerable to CVE-2024-42256?
Run 'uname -r' to check your kernel version. If it shows 6.10 or 6.10.1, your system is vulnerable. Additionally, check 'mount | grep cifs' to see if CIFS/SMB is mounted with multichannel enabled.
Does Defensia detect CVE-2024-42256?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2024-42256 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-2024-42256. Free for 1 server.
Get started free