Vulnerability Description
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.
CVSS Score
HIGH
References
- https://git.kernel.org/stable/c/c5643ea4f040acc2f4d1e88f49bd0be51110ff2f
- https://git.kernel.org/stable/c/d38c835925d4a3bfdf0a85ff2829ee90c709c561
FAQ
What is CVE-2026-93277?
CVE-2026-93277 is a vulnerability with a CVSS score of 7.8 (HIGH). 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 dr...
How severe is CVE-2026-93277?
CVE-2026-93277 has been rated HIGH with a CVSS base score of 7.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-93277?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.