CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2023-52775 remediation guide

Linux Linux, linux kernel

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...

Open CVE record
ProductLinux Linux, linux kernel
Affected versions>= 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 < 5ada292b5c504720a0acef8cae9acc62a694d19c, >= 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 < 90072af9efe8c7bd7d086709014ddd44cebd5e7c, >= 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 < 94a0ae698b4d5d5bb598e23228002a1491c50add, >= 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 < 7234d2b5dffa5af77fd4e0deaebab509e130c6b1, >= 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 < e6d71b437abc2f249e3b6a1ae1a7228e09c6e563, >= 5.8, >= 5.8 < 5.10.203, >= 5.11 < 5.15.141, >= 5.16 < 6.1.65, >= 6.2 < 6.6.4, 6.7
Fixed versions5.10.203, 5.15.141, 6.1.65, 6.6.4
Priority basisReview · CVSS 7.8 · EPSS 0.66%
01

Identify the affected asset

Confirm whether Linux Linux, linux kernel is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 < 5ada292b5c504720a0acef8cae9acc62a694d19c, >= 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 < 90072af9efe8c7bd7d086709014ddd44cebd5e7c, >= 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 < 94a0ae698b4d5d5bb598e23228002a1491c50add, >= 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 < 7234d2b5dffa5af77fd4e0deaebab509e130c6b1, >= 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 < e6d71b437abc2f249e3b6a1ae1a7228e09c6e563, >= 5.8, >= 5.8 < 5.10.203, >= 5.11 < 5.15.141, >= 5.16 < 6.1.65, >= 6.2 < 6.6.4, 6.7. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 5.10.203, 5.15.141, 6.1.65, 6.6.4. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.