CVE-2023-53504 (GCVE-0-2023-53504)
Vulnerability from cvelistv5
Published
2025-10-01 11:45
Modified
2026-08-05 09:14
Severity ?
7.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Properly order ib_device_unalloc() to avoid UAF ib_dealloc_device() should be called only after device cleanup. Fix the dealloc sequence.
References
Impacted products
Vendor Product Version
Linux Linux Version: 6d758147c7b80a46465f72e9e6294d244ee98a21
Version: 6d758147c7b80a46465f72e9e6294d244ee98a21
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/infiniband/hw/bnxt_re/main.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "c95863f6d970ef968e7c1f3c481f72a4b0734654",
              "status": "affected",
              "version": "6d758147c7b80a46465f72e9e6294d244ee98a21",
              "versionType": "git"
            },
            {
              "lessThan": "5363fc488da579923edf6a2fdca3d3b651dd800b",
              "status": "affected",
              "version": "6d758147c7b80a46465f72e9e6294d244ee98a21",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/infiniband/hw/bnxt_re/main.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.3"
            },
            {
              "lessThan": "6.3",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.4.*",
              "status": "unaffected",
              "version": "6.4.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.5",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.4.11",
                  "versionStartIncluding": "6.3",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.5",
                  "versionStartIncluding": "6.3",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/bnxt_re: Properly order ib_device_unalloc() to avoid UAF\n\nib_dealloc_device() should be called only after device cleanup.  Fix the\ndealloc sequence."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The UAF occurs in the bnxt_re auxiliary-device removal path, reachable only from local operations on the host (PCI device unbind/removal, module unload, SR-IOV teardown) and exploited by a local heap-spray to reclaim the freed rdev; there is no remote or adjacent-network trigger.\nAC:L - The use-after-free is unconditional \u2014 every removal frees rdev and then runs the entire bnxt_re_dev_uninit() on it, with no race to win \u2014 and the RCU-deferred free plus multi-second firmware-command waits inside the function give a wide, attacker-influenceable window for reclaiming the allocation.\nPR:L - An unprivileged local user supplies the exploitation half by spraying to reclaim the freed multi-KB rdev allocation, after which the freed-memory writes and pointer dereferences act on attacker-controlled data; NIC teardown (hot-plug, SR-IOV reconfiguration, driver reload) is routine in cloud and container hosts, so no elevated privilege is assumed for the attacker.\nUI:N - No victim interaction is needed \u2014 the teardown occurs automatically via PCI hot-unplug, error-recovery re-probe, SR-IOV changes, or driver reload during upgrades, and the UAF fires unconditionally once it starts.\nS:U - Both the freed object and all corrupted state live in kernel memory under the same security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The freed rdev is read extensively after release (rdev-\u003een_dev, rdev-\u003echip_ctx, rdev-\u003ercfw, rdev-\u003eqplib_res/qplib_ctx), so reclaiming the slab lets an attacker leak adjacent kernel data and pointers, and mis-freed DMA/kernel buffers can be re-read.\nI:H - The path performs writes into freed memory (test_and_clear_bit on rdev-\u003eflags, rdev-\u003enum_msix = 0) and kfree/dma_free_coherent on pointers read from the freed struct, yielding a controlled-free and heap-corruption primitive that is leverageable for control-flow hijack.\nA:H - Even unexploited, the UAF corrupts the slab and dereferences stale pointers (bnxt_unregister_dev(rdev-\u003een_dev), chip_ctx teardown), producing KASAN splats, oopses, and kernel panics on every affected device removal."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T09:14:30.751Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/c95863f6d970ef968e7c1f3c481f72a4b0734654"
        },
        {
          "url": "https://git.kernel.org/stable/c/5363fc488da579923edf6a2fdca3d3b651dd800b"
        }
      ],
      "title": "RDMA/bnxt_re: Properly order ib_device_unalloc() to avoid UAF",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2023-53504",
    "datePublished": "2025-10-01T11:45:54.977Z",
    "dateReserved": "2025-10-01T11:39:39.404Z",
    "dateUpdated": "2026-08-05T09:14:30.751Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.