staging: nvec: fix use-after-free in nvec_rx_completed()
- 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
- 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: staging: nvec: fix use-after-free in nvec_rx_completed() In nvec_rx_completed(), when an incomplete RX transfer is detected, nvec_msg_free() is called to return the message back to the pool by clearing its 'used' atomic flag. Immediately after this, the code accesses nvec->rx->data[0] to check the message type. Since nvec_msg_free() marks the pool slot as available via atomic_set(), any concurrent or subsequent call to nvec_msg_alloc() could claim that same slot and overwrite its data[] array. Reading nvec->rx->data[0] after freeing the message is therefore a use-after-free. Fix this by saving the message type byte before calling nvec_msg_free(), then using the saved value for the battery quirk check.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.2
References 8
git.kernel.org
- stable/c/6b2ea886ebdae44a2394029844a4e78f58e1587d
- stable/c/a37625c7b688fcf68a54263528eccbabfd7fa17a
- stable/c/9f7fe4165a1f1014bdadc8e744c0fd3c2d8c0b89
- stable/c/08626fcfe12308ca3f8b22c538ba7dee0b2dce7a
- stable/c/f19a5bc059051143c489dd6f79a0f9c3bfd13aea
- stable/c/bb3d592c7d6c4ec8ac6640c690ca13298e7e8e90
- stable/c/5de04caa46b635e180cecbd164e333eca535db94
- stable/c/26813881181deb3a32fbb59eadb2599cbe8423f6