Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53597: cifs: fix mid leak during reconnection after timeout threshold

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 5.10, 57d25e9905c71133e201f6d06b56a3403d4ad433, 69cba9d3c1284e0838ae408830a02c4a063104bc.
  • Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 5.10, 57d25e9905c71133e201f6d06b56a3403d4ad433, 69cba9d3c1284e0838ae408830a02c4a063104bc or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Oct 4, 2025
Updated
Aug 5, 2026
EPSS
0.2% · 21th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CNA vs NVD score

NVD
5.5
CNA · Linux
7.5
2.0 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-53597

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.9.5 and later · before 5.15.150
  • linux linux kernel5.16 and later · before 6.1.42
  • linux linux kernel6.2 and later · before 6.4.7
  • linux linux kernel6.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • fa6d7a5853f93efb088aba36af12cb1944156411, 5.10affected
    • 8e670f77c4a55013db6d23b962f9bf6673a5e7b6 and later · before df31d05f0678cdd0796ea19983a2b93edca18bb0affected · git
    • 8e670f77c4a55013db6d23b962f9bf6673a5e7b6 and later · before c55901d381a22300c9922170e59704059f50977baffected · git
    • 8e670f77c4a55013db6d23b962f9bf6673a5e7b6 and later · before 57d25e9905c71133e201f6d06b56a3403d4ad433affected · git
    • 8e670f77c4a55013db6d23b962f9bf6673a5e7b6 and later · before 69cba9d3c1284e0838ae408830a02c4a063104bcaffected · git
    • 5.9.5 and later · before 5.10affected · semver
    • before 5.10not affected · semver
    • 5.15.150 and later · up to and including 5.15.*not affected · semver
    • 6.1.42 and later · up to and including 6.1.*not affected · semver
    • 6.4.7 and later · up to and including 6.4.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.52-16.1.52-1
Debian:13linuxbefore 6.4.11-16.4.11-1
SUSE:Linux Enterprise Live Patching 12 SP5kernel-defaultbefore 4.12.14-122.283.14.12.14-122.283.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_75before 1-8.3.11-8.3.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-sourcebefore 4.12.14-122.283.14.12.14-122.283.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-symsbefore 4.12.14-122.283.14.12.14-122.283.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-53595Oct 4, 2025 · octeontx2-pf: mcs: Fix NULL pointer dereferences
    22Monitor
  • ← EarlierCVE-2023-53596Oct 4, 2025 · drivers: base: Free devm resources when unregistering a device
    31Monitor
  • Later →CVE-2023-53599Oct 4, 2025 · crypto: af_alg - Fix missing initialisation affecting gcm-aes-s390
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux5.10Vendor (CNA)
Linux Linux57d25e9905c71133e201f6d06b56a3403d4ad433Vendor (CNA)
Linux Linux69cba9d3c1284e0838ae408830a02c4a063104bcVendor (CNA)
Linux Linuxc55901d381a22300c9922170e59704059f50977bVendor (CNA)
Linux Linuxdf31d05f0678cdd0796ea19983a2b93edca18bb0Vendor (CNA)
debian:linux6.1.52-1 · Debian:12Package registry (OSV)
suse:kernel-default4.12.14-122.283.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kernel-source4.12.14-122.283.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kernel-syms4.12.14-122.283.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_751-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-401 · Missing Release of Memory after Effective Lifetime

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records