CVE-2023-53597
published 2025-10-04CVE-2023-53597: In the Linux kernel, the following vulnerability has been resolved: cifs: fix mid leak during reconnection after timeout threshold When the number of responses…
PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.26%
18.0th percentile
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.
Affected
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.52-1 (bookworm) | linux 6.1.52-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 5.9.5 < 5.10 | 5.10 |
| linux | linux | >= 8e670f77c4a55013db6d23b962f9bf6673a5e7b6 < df31d05f0678cdd0796ea19983a2b93edca18bb0 | df31d05f0678cdd0796ea19983a2b93edca18bb0 |
| linux | linux | >= 8e670f77c4a55013db6d23b962f9bf6673a5e7b6 < c55901d381a22300c9922170e59704059f50977b | c55901d381a22300c9922170e59704059f50977b |
| linux | linux | >= 8e670f77c4a55013db6d23b962f9bf6673a5e7b6 < 57d25e9905c71133e201f6d06b56a3403d4ad433 | 57d25e9905c71133e201f6d06b56a3403d4ad433 |
| linux | linux | >= 8e670f77c4a55013db6d23b962f9bf6673a5e7b6 < 69cba9d3c1284e0838ae408830a02c4a063104bc | 69cba9d3c1284e0838ae408830a02c4a063104bc |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.1.52-1 | 6.1.52-1 |
| linux | linux_kernel | >= 0 < 6.4.11-1 | 6.4.11-1 |
| linux | linux_kernel | >= 0 < 6.4.11-1 | 6.4.11-1 |
| linux | linux_kernel | >= 5.16 < 6.1.42 | 6.1.42 |
| linux | linux_kernel | >= 5.9.5 < 5.15.150 | 5.15.150 |
| linux | linux_kernel | >= 6.2 < 6.4.7 | 6.4.7 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Linux Kernel up to 5.15.149/6.1.41/6.4.6 cifs memory leak (EUVD-2023-60011 / Nessus ID 279908)
vuldb·2026-04-28·CVSS 5.5
CVE-2023-53597 [MEDIUM] Linux Kernel up to 5.15.149/6.1.41/6.4.6 cifs memory leak (EUVD-2023-60011 / Nessus ID 279908)
A vulnerability labeled as critical has been found in Linux Kernel up to 5.15.149/6.1.41/6.4.6. This affects an unknown function of the component cifs. Executing a manipulation can lead to memory leak.
This vulnerability appears as CVE-2023-53597. The attacker needs to be present on the local network. There is no available exploit.
The affected component should be upgraded.
OSV
CVE-2023-53597: In the Linux kernel, the following vulnerability has been resolved: cifs: fix mid leak during reconnection after timeout threshold When the number of
osv·2025-10-04·CVSS 5.5
CVE-2023-53597 [MEDIUM] CVE-2023-53597: In the Linux kernel, the following vulnerability has been resolved: cifs: fix mid leak during reconnection after timeout threshold When the number of
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
GHSA
GHSA-g6xj-m5qj-cqp6: In the Linux kernel, the following vulnerability has been resolved:
cifs: fix mid leak during reconnection after timeout threshold
When the number o
ghsa_unreviewed·2025-10-04
CVE-2023-53597 [MEDIUM] CWE-401 GHSA-g6xj-m5qj-cqp6: In the Linux kernel, the following vulnerability has been resolved:
cifs: fix mid leak during reconnection after timeout threshold
When the number o
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 ma
Red Hat
kernel: cifs: fix mid leak during reconnection after timeout threshold
vendor_redhat·2025-10-04·CVSS 5.5
CVE-2023-53597 [MEDIUM] CWE-772 kernel: cifs: fix mid leak during reconnection after timeout threshold
kernel: cifs: fix mid leak during reconnection after timeout threshold
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
Debian
CVE-2023-53597: linux - In the Linux kernel, the following vulnerability has been resolved: cifs: fix m...
vendor_debian·2023·CVSS 5.5
CVE-2023-53597 [MEDIUM] CVE-2023-53597: linux - In the Linux kernel, the following vulnerability has been resolved: cifs: fix m...
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
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2025-10-04
Published