CVE-2026-89529 (GCVE-0-2026-89529)

Vulnerability from cvelistv5 – Published: 2026-09-11 19:44 – Updated: 2026-10-19 08:48
VLAI
Title
svcrdma: Reject oversized Read segments at decode time
Summary
In the Linux kernel, the following vulnerability has been resolved: svcrdma: Reject oversized Read segments at decode time The RPC/RDMA Read list decoder stores wire-supplied segment lengths without validation. xdr_count_read_segments() checks 4-byte alignment for non-zero position values but does not cap the segment length. An oversized rs_length reaches svc_rdma_build_read_segment(), which derives nr_bvec from it and can drive a large dynamic bvec allocation before verifying that enough rq_pages remain. If the post-allocation page-overrun guard fires, the freshly acquired rw context is not returned, leaking the resource. Reject any segment whose length exceeds the receive context's page budget during Read list decoding, consistent with how xdr_check_write_chunk() bounds Write segment counts against rc_maxpages. Also return the rw context on the existing post-allocation overrun path in svc_rdma_build_read_segment(), keeping that defensive guard balanced.
Severity
No CVSS data available.
Assigner
Linux CNA under the mitre root
CNA scorecard D 53/100 over 6639 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 5ee62b4a91137557ee4b09d1604f1dfd0b4344a8 , < 5120fe54e0e2f5b62797a432115cc61d61117a5b (git)
Affected: 5ee62b4a91137557ee4b09d1604f1dfd0b4344a8 , < af6f0e06bed818ee7fc8b869915964410020a1c5 (git)
guessed Create a notification for this product.
Linux Linux Affected: 7.0
Unaffected: 0 , < 7.0 (semver)
Unaffected: 7.2.4 , ≤ 7.2.* (semver)
Unaffected: 7.3 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/sunrpc/xprtrdma/svc_rdma_recvfrom.c",
            "net/sunrpc/xprtrdma/svc_rdma_rw.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "5120fe54e0e2f5b62797a432115cc61d61117a5b",
              "status": "affected",
              "version": "5ee62b4a91137557ee4b09d1604f1dfd0b4344a8",
              "versionType": "git"
            },
            {
              "lessThan": "af6f0e06bed818ee7fc8b869915964410020a1c5",
              "status": "affected",
              "version": "5ee62b4a91137557ee4b09d1604f1dfd0b4344a8",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/sunrpc/xprtrdma/svc_rdma_recvfrom.c",
            "net/sunrpc/xprtrdma/svc_rdma_rw.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.0"
            },
            {
              "lessThan": "7.0",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.4",
                  "versionStartIncluding": "7.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "7.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: Reject oversized Read segments at decode time\n\nThe RPC/RDMA Read list decoder stores wire-supplied segment\nlengths without validation. xdr_count_read_segments() checks\n4-byte alignment for non-zero position values but does not\ncap the segment length.\n\nAn oversized rs_length reaches svc_rdma_build_read_segment(),\nwhich derives nr_bvec from it and can drive a large dynamic\nbvec allocation before verifying that enough rq_pages remain.\nIf the post-allocation page-overrun guard fires, the freshly\nacquired rw context is not returned, leaking the resource.\n\nReject any segment whose length exceeds the receive context\u0027s\npage budget during Read list decoding, consistent with how\nxdr_check_write_chunk() bounds Write segment counts against\nrc_maxpages. Also return the rw context on the existing\npost-allocation overrun path in svc_rdma_build_read_segment(),\nkeeping that defensive guard balanced."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T08:48:20.953Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/5120fe54e0e2f5b62797a432115cc61d61117a5b"
        },
        {
          "url": "https://git.kernel.org/stable/c/af6f0e06bed818ee7fc8b869915964410020a1c5"
        }
      ],
      "title": "svcrdma: Reject oversized Read segments at decode time",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-89529",
    "datePublished": "2026-09-11T19:44:09.259Z",
    "dateReserved": "2026-09-11T19:38:34.719Z",
    "dateUpdated": "2026-10-19T08:48:20.953Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-89529",
      "date": "2026-11-09",
      "epss": "0.00198",
      "percentile": "0.09542"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "net/sunrpc/xprtrdma/svc_rdma_recvfrom.c",
                  "net/sunrpc/xprtrdma/svc_rdma_rw.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "5120fe54e0e2f5b62797a432115cc61d61117a5b",
                    "status": "affected",
                    "version": "5ee62b4a91137557ee4b09d1604f1dfd0b4344a8",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "af6f0e06bed818ee7fc8b869915964410020a1c5",
                    "status": "affected",
                    "version": "5ee62b4a91137557ee4b09d1604f1dfd0b4344a8",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "net/sunrpc/xprtrdma/svc_rdma_recvfrom.c",
                  "net/sunrpc/xprtrdma/svc_rdma_rw.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "7.0"
                  },
                  {
                    "lessThan": "7.0",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "7.2.*",
                    "status": "unaffected",
                    "version": "7.2.4",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "7.3",
                    "versionType": "original_commit_for_fix"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: Reject oversized Read segments at decode time\n\nThe RPC/RDMA Read list decoder stores wire-supplied segment\nlengths without validation. xdr_count_read_segments() checks\n4-byte alignment for non-zero position values but does not\ncap the segment length.\n\nAn oversized rs_length reaches svc_rdma_build_read_segment(),\nwhich derives nr_bvec from it and can drive a large dynamic\nbvec allocation before verifying that enough rq_pages remain.\nIf the post-allocation page-overrun guard fires, the freshly\nacquired rw context is not returned, leaking the resource.\n\nReject any segment whose length exceeds the receive context\u0027s\npage budget during Read list decoding, consistent with how\nxdr_check_write_chunk() bounds Write segment counts against\nrc_maxpages. Also return the rw context on the existing\npost-allocation overrun path in svc_rdma_build_read_segment(),\nkeeping that defensive guard balanced."
          }
        ],
        "id": "CVE-2026-89529",
        "lastModified": "2026-10-19T09:17:47.460",
        "metrics": {},
        "published": "2026-09-11T20:19:35.740",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/5120fe54e0e2f5b62797a432115cc61d61117a5b"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/af6f0e06bed818ee7fc8b869915964410020a1c5"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Received"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-06T01:17:15+00:00",
      "cve": "CVE-2026-89529",
      "id": "CVE-2026-89529",
      "initial_release_date": "2026-09-11T00:00:00+00:00",
      "product_status:known_affected": "15",
      "product_status:known_not_affected": "188",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: svcrdma: Reject oversized Read segments at decode time",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-89529.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.