{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2023-53504","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2025-10-01T11:39:39.404Z","datePublished":"2025-10-01T11:45:54.977Z","dateUpdated":"2026-08-05T09:14:30.751Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T09:14:30.751Z"},"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":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"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 — every removal frees rdev and then runs the entire bnxt_re_dev_uninit() on it, with no race to win — 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 — 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->en_dev, rdev->chip_ctx, rdev->rcfw, rdev->qplib_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->flags, rdev->num_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->en_dev), chip_ctx teardown), producing KASAN splats, oopses, and kernel panics on every affected device removal."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/infiniband/hw/bnxt_re/main.c"],"versions":[{"version":"6d758147c7b80a46465f72e9e6294d244ee98a21","lessThan":"c95863f6d970ef968e7c1f3c481f72a4b0734654","status":"affected","versionType":"git"},{"version":"6d758147c7b80a46465f72e9e6294d244ee98a21","lessThan":"5363fc488da579923edf6a2fdca3d3b651dd800b","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/infiniband/hw/bnxt_re/main.c"],"versions":[{"version":"6.3","status":"affected"},{"version":"0","lessThan":"6.3","status":"unaffected","versionType":"semver"},{"version":"6.4.11","lessThanOrEqual":"6.4.*","status":"unaffected","versionType":"semver"},{"version":"6.5","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.3","versionEndExcluding":"6.4.11"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.3","versionEndExcluding":"6.5"}]}]}],"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"}}}}