RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters
- 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 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- 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
The Linux kernel's SCSI RDMA target (srpt) driver, which handles InfiniBand/RDMA-based SCSI target connections, is affected. When setting up data transfer contexts for a multi-buffer request fails partway through, the error cleanup leaves internal counters and a pointer in an inconsistent state, which can cause the driver to miscount available send queue slots and potentially lead to incorrect resource accounting.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
In the Linux kernel, the following vulnerability has been resolved: RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters When srpt_alloc_rw_ctxs() fails partway through a multi-buffer indirect descriptor, the unwind path destroys RDMA contexts but leaves stale n_rw_ctx and n_rdma values (and a dangling rw_ctxs pointer). Later sq_wr_avail accounting in srpt_queue_response() or srpt_write_pending() can then subtract the wrong number of send queue credits. Reset the counters and clear rw_ctxs after freeing the heap allocation before returning an error.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From b99f8e4d7bcd3bfbb3cd965918523299370d0cb2 · fixed in af00051dbc9f467d4840ec709680660a3f8990fa; From b99f8e4d7bcd3bfbb3cd965918523299370d0cb2 · fixed in 717ab4d0614e9446bf8e2de6229464499e4008d6; From b99f8e4d7bcd3bfbb3cd965918523299370d0cb2 · fixed in f1f2252da52cdda912da9993f39f58783b01b38f; From b99f8e4d7bcd3bfbb3cd965918523299370d0cb2 · fixed in f65f45dfa1e6e2eaa9e11c8b8ce8857799cb189d; From b99f8e4d7bcd3bfbb3cd965918523299370d0cb2 · fixed in be1478849e1abb1e12dc12e14cdbf800cc6fa99a; From b99f8e4d7bcd3bfbb3cd965918523299370d0cb2 · fixed in af073bd245180393bcb15d33d3990a6bdc32593a; From b99f8e4d7bcd3bfbb3cd965918523299370d0cb2 · fixed in bd02d644bd19a2795c018635d273d91e45d2bb95; From b99f8e4d7bcd3bfbb3cd965918523299370d0cb2 · fixed in b38f98e176050850f41bb6415f3a71400056623e
- Linux Linux
4.7
- KernelLinux
From 4.7.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6
References 8
git.kernel.org
- stable/c/af00051dbc9f467d4840ec709680660a3f8990fa
- stable/c/717ab4d0614e9446bf8e2de6229464499e4008d6
- stable/c/f1f2252da52cdda912da9993f39f58783b01b38f
- stable/c/f65f45dfa1e6e2eaa9e11c8b8ce8857799cb189d
- stable/c/be1478849e1abb1e12dc12e14cdbf800cc6fa99a
- stable/c/af073bd245180393bcb15d33d3990a6bdc32593a
- stable/c/bd02d644bd19a2795c018635d273d91e45d2bb95
- stable/c/b38f98e176050850f41bb6415f3a71400056623e