Riskcovery

CVE-2023-53597

cifs: fix mid leak during reconnection after timeout threshold

State
Published
Severity
7.5 High
Published
Oct 4, 2025
Updated
Aug 5, 2026
Reserved
Oct 4, 2025

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

cifs: fix mid leak during reconnection after timeout threshold

When the number of responses with status of STATUS_IO_TIMEOUT exceeds a specified threshold (NUM_STATUS_IO_TIMEOUT), we reconnect the connection. But we do not return the mid, or the credits returned for the mid, or reduce the number of in-flight requests.

This bug could result in the server->in_flight count to go bad, and also cause a leak in the mids.

This change moves the check to a few lines below where the response is decrypted, even of the response is read from the transform header. This way, the code for returning the mids can be reused.

Also, the cifs_reconnect was reconnecting just the transport connection before. In case of multi-channel, this may not be what we want to do after several timeouts. Changed that to reconnect the session and the tree too.

Also renamed NUM_STATUS_IO_TIMEOUT to a more appropriate name MAX_STATUS_IO_TIMEOUT.

Scores

CVSSScoreVectorSource
3.17.5 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 8e670f77c4a55013db6d23b962f9bf6673a5e7b6 to before df31d05f0678cdd0796ea19983a2b93edca18bb0Affected
  • 8e670f77c4a55013db6d23b962f9bf6673a5e7b6 to before c55901d381a22300c9922170e59704059f50977bAffected
  • 8e670f77c4a55013db6d23b962f9bf6673a5e7b6 to before 57d25e9905c71133e201f6d06b56a3403d4ad433Affected
  • 8e670f77c4a55013db6d23b962f9bf6673a5e7b6 to before 69cba9d3c1284e0838ae408830a02c4a063104bcAffected
  • fa6d7a5853f93efb088aba36af12cb1944156411Affected
  • 5.9.5 to before 5.10Affected
LinuxLinux
  • 5.10Affected
  • before 5.10Not affected
  • 5.15.150 through 5.15.*Not affected
  • 6.1.42 through 6.1.*Not affected
  • 6.4.7 through 6.4.*Not affected
  • 6.5 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.