CVE-2026-31537

smb: server: make use of smbdirect_socket.send_io.bcredits

Published Apr 24, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

smb: server: make use of smbdirect_socket.send_io.bcredits

It turns out that our code will corrupt the stream of
reassabled data transfer messages when we trigger an
immendiate (empty) send.

In order to fix this we'll have a single 'batch' credit per
connection. And code getting that credit is free to use
as much messages until remaining_length reaches 0, then
the batch credit it given back and the next logical send can
happen.

Analysis

AI-generated

Technical impact

An improper handling of the SMBDIRECT socket credit counter in the Linux kernel can corrupt the stream of data transfer messages when an empty immediate send is performed. The bug manifests as a loss of data integrity in SMB traffic, potentially causing downtime or erratic behavior for clients communicating with the affected SMB server. The underlying weakness is a failure to correctly validate or manage buffer credits, which aligns with the CWE-821 classification of inadequate bounds checking.

Affected Systems

All Linux kernel builds that have not yet applied the fix for CVE-2026-31537 are susceptible. The exact kernel versions impacted are not listed in the CVE data; the remedy is referenced in the commit logs linked in the advisory. System administrators should review their kernel version and upgrade to a patched release where the smbdirect_socket.send_io.bcredits logic has been corrected.

Risk and Exploitability

The EPSS score for this vulnerability is reported as < 1%, indicating a very low probability of exploitation in real‑world scenarios, and it is not listed in the CISA KEV catalog. The CVSS score is 5.5, indicating moderate severity. The defect resides at the SMB protocol handling layer of the kernel, so an attacker would need network access to an exposed SMB service to trigger the corrupting send. Although the impact could be a denial of service or data corruption, the combination of the low EPSS, lack of a known exploit, and the requirement for a crafted SMB packet suggests a moderate but not immediate threat. Patching remains the recommended countermeasure.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the kernel to a version that includes the smbdirect_socket.send_io.bcredits fix (see the commit references in the advisory).
  • If an immediate kernel upgrade cannot be performed, temporarily disable SMB services or block SMB traffic at the perimeter firewall to prevent exploitation.
  • After applying the fix or workaround, monitor SMB connections for anomalous activity and ensure related SMB code paths are also free of remaining buffer‑management bugs.

Generated by OpenCVE AI on April 28, 2026 at 23:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses NVD-CWE-noinfo
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: smb: server: make use of smbdirect_socket.send_io.bcredits It turns out that our code will corrupt the stream of reassabled data transfer messages when we trigger an immendiate (empty) send. In order to fix this we'll have a single 'batch' credit per connection. And code getting that credit is free to use as much messages until remaining_length reaches 0, then the batch credit it given back and the next logical send can happen.
Title smb: server: make use of smbdirect_socket.send_io.bcredits
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
May 11, 2026, 10:10 PM
Reserved
Mar 9, 2026, 3:48 PM
Status
Analyzed
Published
Apr 24, 2026, 3:16 PM
Modified
Nov 11, 2026, 11:10 PM
Severity
Public date
Apr 24, 2026, 12:00 AM