RDMA/bnxt_re: Validate udata before executing commands
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From bed686d8dcd4fbcaa18cf67468caaf8772acfc7a · fixed in c5643ea4f040acc2f4d1e88f49bd0be51110ff2f; From bed686d8dcd4fbcaa18cf67468caaf8772acfc7a · fixed in d38c835925d4a3bfdf0a85ff2829ee90c709c561
- Linux Linux
7.1
- KernelLinux
From 7.1.0 · fixed in 7.2.6