RDMA/bnxt_re: Fix OOB write in bnxt_re_copy_err_stats()

{
  "id": "f7f0a6c9536ee52c10ccf41e40d4243445a77a584c679e12d1cc867c0f3461d2",
  "url": "https://osv.dev/vulnerability/CVE-2025-71092",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "RDMA/bnxt_re: Fix OOB write in bnxt_re_copy_err_stats()",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Fix OOB write in bnxt_re_copy_err_stats() Commit ef56081d1864 (\"RDMA/bnxt_re: RoCE related hardware counters update\") added three new counters and placed them after BNXT_RE_OUT_OF_SEQ_ERR. BNXT_RE_OUT_OF_SEQ_ERR acts as a boundary marker for allocating hardware statistics with different num_counters values on chip_gen_p5_p7 devices. As a result, BNXT_RE_NUM_STD_COUNTERS are used when allocating hw_stats, which leads to an out-of-bounds write in bnxt_re_copy_err_stats(). The counters BNXT_RE_REQ_CQE_ERROR, BNXT_RE_RESP_CQE_ERROR, and BNXT_RE_RESP_REMOTE_ACCESS_ERRS are applicable to generic hardware, not only p5/p7 devices. Fix this by moving these counters before BNXT_RE_OUT_OF_SEQ_ERR so they are included in the generic counter set.",
    "evidence": "osv:CVE-2025-71092",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.18.4",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2025-71092",
      "aliases": [
        "CVE-2025-71092"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "ef56081d1864582a6db50710733416c0510b7826"
                },
                {
                  "fixed": "369a161c48723f60f06f3510b82ea7d96d0499ab"
                },
                {
                  "fixed": "9b68a1cc966bc947d00e4c0df7722d118125aa37"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-71092.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.18.0"
                },
                {
                  "fixed": "6.18.4"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-71092.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:26.724693921Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/369a161c48723f60f06f3510b82ea7d96d0499ab",
        "https://git.kernel.org/stable/c/9b68a1cc966bc947d00e4c0df7722d118125aa37",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/71xxx/CVE-2025-71092.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-71092",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/71xxx/CVE-2025-71092.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-71092",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 493166,
  "published_at": "2026-01-13T15:34:53.11+00:00"
}