- Published on
-
Oct 04, 2025
- Research 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.
- Affected versions
-
max 1.5.0.
Plugin Security Certification
Join the community of developers who prioritize security. Highlight your plugin in the WordPress catalog.
Get Plugin Security Certificate
| New vulnerability |
|
Boldermail – Email Marketing and Newsletters for WordPress
(CVE-2025-52740)
, Nov 11, 2025
|
|
Block Country
(CVE-2025-48077)
, Nov 11, 2025
|
|
Attesa Extra
(CVE-2025-62971)
, Nov 11, 2025
|
|
Content Locker for Elementor
(CVE-2025-10896)
, Nov 11, 2025
|
|
WP-DownloadManager
(CVE-2025-10747)
, Nov 11, 2025
|