rpcrdma: arm rn_done before publishing the notification
- 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 6.12.111, 6.18.51, 7.2.5
- 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: rpcrdma: arm rn_done before publishing the notification rpcrdma_rn_register() inserts @rn into rd_xa with xa_alloc() before storing the caller's callback in rn->rn_done. The xarray makes @rn reachable to rpcrdma_remove_one(), which walks rd_xa and invokes rn->rn_done(rn) for every registered notification. A device removal that races a fresh registration can therefore observe @rn with rn_done still NULL, because the notification objects are zero allocated by their owners, and call through a NULL function pointer. Store rn->rn_done before xa_alloc() publishes @rn. The xarray's store-side and load-side ordering then guarantees that any CPU which finds @rn in rd_xa also observes the armed callback. rpcrdma_rn_unregister() treats a non-NULL rn_done as the sentinel for a completed registration, so the early store must not survive a failed registration. Clear rn_done again when xa_alloc() fails. Were it left set, the failed-accept cleanup path would call rpcrdma_rn_unregister() on an @rn that was never inserted, erasing an unrelated rd_xa slot and underflowing rd_kref.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 7e86845a0346efc95fddaa97ce5cd6a8bda8c71c · fixed in f9fe3cad43c42d874a388583552b39b411d886eb; From 7e86845a0346efc95fddaa97ce5cd6a8bda8c71c · fixed in 3c97b8e76ca2bba9e8770571413aed694068e78e; From 7e86845a0346efc95fddaa97ce5cd6a8bda8c71c · fixed in ea0408273ccf5df1fb52d9a1b9db4d31600dcb36; From 7e86845a0346efc95fddaa97ce5cd6a8bda8c71c · fixed in 5b06f706374c37375bdff9d21cc10e61df925a92
- Linux Linux
6.11
- KernelLinux
From 6.11.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5