Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 3 weeks, 3 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
staging: nvec: fix use-after-free in nvec_rx_completed()

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.

Affected products

Linux
  • <5de04caa46b635e180cecbd164e333eca535db94
  • =<5.10.*
  • <9f7fe4165a1f1014bdadc8e744c0fd3c2d8c0b89
  • <08626fcfe12308ca3f8b22c538ba7dee0b2dce7a
  • <a37625c7b688fcf68a54263528eccbabfd7fa17a
  • <26813881181deb3a32fbb59eadb2599cbe8423f6
  • <6b2ea886ebdae44a2394029844a4e78f58e1587d
  • <bb3d592c7d6c4ec8ac6640c690ca13298e7e8e90
  • =<6.6.*
  • =<*
  • =<6.18.*
  • =<6.12.*
  • ==3.2
  • =<7.1.*
  • =<5.15.*
  • <3.2
  • =<6.1.*
  • <f19a5bc059051143c489dd6f79a0f9c3bfd13aea