CVE Catalog

CVE-2026-93277

HighCVSS 7.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.14%

3th percentile - higher than 3% of all known CVEs

Summary

In the Linux kernel, the RDMA/bnxt_re driver's destroy callbacks zero the udata output after tearing down driver resources. If the userspace access fails, uverbs preserves the uobject and allows the destroy callback to run again even though the driver resource has already been freed. The fix moves ib_no_udata_io() before teardown and ib_respond_empty_udata() to the start of create and modify flows.

Risk Assessment

Can lead to use-after-free and a leaked hardware object, causing system instability or privilege escalation.

Recommendation

Update the Linux kernel to a version containing the fix that validates udata before executing destroy operations and moves ib_respond_empty_udata() to the start of create and modify flows.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Validate udata before executing commands The destroy callbacks currently zero the udata output after tearing down driver resources. If the userspace access fails, uverbs preserves the uobject and allows the destroy callback to run again, even though the driver resource has already been freed. Call ib_no_udata_io() before teardown so udata failures are detected while the resource is still intact, then return success after teardown completes. As part of this change, move ib_respond_empty_udata() to the start of the create and modify flows. While this is not strictly required for general create flows, as the core layer unwinds uobjects on failure, it is necessary for create AH. In _rdma_create_ah(), the HW object is otherwise leaked.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS