CVE-2026-31535 (GCVE-0-2026-31535)

Vulnerability from cvelistv5 – Published: 2026-04-24 14:30 – Updated: 2026-04-24 14:30
VLAI?
Title
smb: client: make use of smbdirect_socket.recv_io.credits.available
Summary
In the Linux kernel, the following vulnerability has been resolved: smb: client: 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's because the peer might already consumed a credit, but between receiving the incoming recv at the hardware and processing the completion in the 'recv_done' functions we likely have a window where we grant credits, which don't 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.
Severity ?
No CVSS data available.
Assigner
Impacted products
Vendor Product Version
Linux Linux Affected: 5fb9b459b3686e366640edd4e62805ef7b4de927 , < f664e6e8a81103cb45c8802a9bc7499e0902c458 (git)
Affected: 5fb9b459b3686e366640edd4e62805ef7b4de927 , < be8845ad5d6558703d20567d8702155598325db8 (git)
Affected: 5fb9b459b3686e366640edd4e62805ef7b4de927 , < 9911b1ed187a770a43950bf51f340ad4b7beecba (git)
Create a notification for this product.
    Linux Linux Affected: 6.18
Unaffected: 0 , < 6.18 (semver)
Unaffected: 6.18.11 , ≤ 6.18.* (semver)
Unaffected: 6.19.1 , ≤ 6.19.* (semver)
Unaffected: 7.0 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/smb/client/smbdirect.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "f664e6e8a81103cb45c8802a9bc7499e0902c458",
              "status": "affected",
              "version": "5fb9b459b3686e366640edd4e62805ef7b4de927",
              "versionType": "git"
            },
            {
              "lessThan": "be8845ad5d6558703d20567d8702155598325db8",
              "status": "affected",
              "version": "5fb9b459b3686e366640edd4e62805ef7b4de927",
              "versionType": "git"
            },
            {
              "lessThan": "9911b1ed187a770a43950bf51f340ad4b7beecba",
              "status": "affected",
              "version": "5fb9b459b3686e366640edd4e62805ef7b4de927",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/smb/client/smbdirect.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.18"
            },
            {
              "lessThan": "6.18",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.19.*",
              "status": "unaffected",
              "version": "6.19.1",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.0",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.11",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19.1",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: make use of smbdirect_socket.recv_io.credits.available\n\nThe logic off managing recv credits by counting posted recv_io and\ngranted credits is racy.\n\nThat\u0027s because the peer might already consumed a credit,\nbut between receiving the incoming recv at the hardware\nand processing the completion in the \u0027recv_done\u0027 functions\nwe likely have a window where we grant credits, which\ndon\u0027t really exist.\n\nSo we better have a decicated counter for the\navailable credits, which will be incremented\nwhen we posted new recv buffers and drained when\nwe grant the credits to the peer."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-04-24T14:30:23.540Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/f664e6e8a81103cb45c8802a9bc7499e0902c458"
        },
        {
          "url": "https://git.kernel.org/stable/c/be8845ad5d6558703d20567d8702155598325db8"
        },
        {
          "url": "https://git.kernel.org/stable/c/9911b1ed187a770a43950bf51f340ad4b7beecba"
        }
      ],
      "title": "smb: client: make use of smbdirect_socket.recv_io.credits.available",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-31535",
    "datePublished": "2026-04-24T14:30:23.540Z",
    "dateReserved": "2026-03-09T15:48:24.113Z",
    "dateUpdated": "2026-04-24T14:30:23.540Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-31535",
      "date": "2026-04-26",
      "epss": "0.00017",
      "percentile": "0.0407"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-31535\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-04-24T15:16:27.427\",\"lastModified\":\"2026-04-24T17:51:40.810\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nsmb: client: make use of smbdirect_socket.recv_io.credits.available\\n\\nThe logic off managing recv credits by counting posted recv_io and\\ngranted credits is racy.\\n\\nThat\u0027s because the peer might already consumed a credit,\\nbut between receiving the incoming recv at the hardware\\nand processing the completion in the \u0027recv_done\u0027 functions\\nwe likely have a window where we grant credits, which\\ndon\u0027t really exist.\\n\\nSo we better have a decicated counter for the\\navailable credits, which will be incremented\\nwhen we posted new recv buffers and drained when\\nwe grant the credits to the peer.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/9911b1ed187a770a43950bf51f340ad4b7beecba\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/be8845ad5d6558703d20567d8702155598325db8\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/f664e6e8a81103cb45c8802a9bc7499e0902c458\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…