CVE-2023-52775: net/smc: avoid data corruption caused by decline
In the Linux kernel, the following vulnerability has been resolved:
net/smc: avoid data corruption caused by decline
The Linux kernel CVE team has assigned CVE-2023-52775 to this issue.
Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024052151-CVE-2023-52775-38a8@gregkh/T
Other sources
In the Linux kernel, the following vulnerability has been resolved:
net/smc: avoid data corruption caused by decline
We found a data corruption issue during testing of SMC-R on Redis applications.
The benchmark has a low probability of reporting a strange error as shown below.
"Error: Protocol error, got "\xe2" as reply type byte"
Finally, we found that the retrieved error data was as follows:
0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C 0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2
It is quite obvious that this is a SMC DECLINE message, which means that the applications received SMC protocol message. We found that this was caused by the following situations:
client server ¦ clc proposal -------------> ¦ clc accept <------------- ¦ clc confirm -------------> wait llc confirm send llc confirm ¦failed llc confirm ¦ x------ (after 2s)timeout wait llc confirm rsp
wait decline
(after 1s) timeout (after 2s) timeout ¦ decline --------------> ¦ decline <--------------
As a result, a decline message was sent in the implementation, and this message was read from TCP by the already-fallback connection.
This patch double the client timeout as 2x of the server value, With this simple change, the Decline messages should never cross or collide (during Confirm link timeout).
This issue requires an immediate solution, since the protocol updates involve a more long-term solution.
— NVD
Linux Kernel is vulnerable to a denial of service, caused by a data corruption issue during testing of SMC-R on Redis applications. By sending a specially crafted request, a local authenticated attacker could exploit this vulnerability to cause a denial of service condition.
— IBM
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2023-52775?
CVE-2023-52775 is categorized as a moderate severity vulnerability in the Linux kernel.
How do I fix CVE-2023-52775?
To fix CVE-2023-52775, upgrade to the patched kernel versions: 5.10.203, 5.15.141, 6.1.65, 6.6.4, or 6.7.
What systems are affected by CVE-2023-52775?
CVE-2023-52775 affects specific versions of the Linux kernel and IBM Security Verify Governance up to ISVG 10.0.2.
What is the impact of CVE-2023-52775?
The impact of CVE-2023-52775 can result in data corruption due to improper handling of certain operations in the net/smc subsystem.
Is CVE-2023-52775 exploitable remotely?
CVE-2023-52775 may be exploited locally if an attacker has access to user-level privileges on a vulnerable system.