RDMA/bng_re: return a timeout when firmware responses stall
- 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/bng_re: return a timeout when firmware responses stall __wait_for_resp() documents that it returns a non-zero error when a firmware command does not complete, and bng_re_rcfw_send_message() already marks the firmware as stalled when the helper returns -ENODEV. However, the helper ignores wait_event_timeout() expiry. If the response slot remains in use after the timeout and after the polled CREQ service attempt, the loop starts another full timeout period and can repeat forever. Return -ENODEV after a timed out wait that still has no response. The existing caller then marks FIRMWARE_STALL_DETECTED and returns -ETIMEDOUT to the command issuer.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 53c6ee7d7f68a0679f8ddc703338aa2550d24a17 · fixed in 02d4ee65dc2e883f554169155937742e6014c243; From 53c6ee7d7f68a0679f8ddc703338aa2550d24a17 · fixed in 5f9576c6734abca88a02db72c466e09d2eddf160
- Linux Linux
6.19
- KernelLinux
From 6.19.0 · fixed in 7.2.6