{
  "cveId": "CVE-2026-31538",
  "url": "https://patchblox.com/security/cve/CVE-2026-31538",
  "summary": "CVE-2026-31538 is fixed in linux on 1 platform by DEBIAN-CVE-2026-31538 (version 6.18.12-1), released May 15, 2026. It is not reported as exploited. Patch Radar priority: High.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  smb: server: make use of smbdirect_socket.recv_i...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  smb: server: make use of smbdirect_socket.recv_io.credits.available  The logic off managing recv credits by counting posted recv_io and granted credits is racy.  That\u0027s because the peer might already consumed a credit, but between receiving the incoming recv at the hardware and processing the completion in the \u0027recv_done\u0027 functions we likely have a window where we grant credits, which don\u0027t really exist.  So we better have a decicated counter for the available credits, which will be incremented when we posted new recv buffers and drained when we grant the credits to the peer.  This fixes regression Namjae reported with the 6.18 release.",
  "published": "2026-04-24T15:16:27Z",
  "severity": "high",
  "cvss": 7.5,
  "cvssVector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00426,
  "epssPercentile": 0.37136,
  "priority": "High",
  "priorityTier": 3,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.18.12-1",
      "fix": "DEBIAN-CVE-2026-31538",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-31538",
      "released": "2026-05-15T16:01:09Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-09T07:25:28Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}