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 2 weeks, 6 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG There were multiple issues in that code. First of all the order between the reset semaphore and the mm_lock was wrong (e.g. copy_to_user) was called while holding the lock. Then we allocated memory while holding the reset semaphore which is also a pretty big bug and can deadlock. Then we used down_read_trylock() instead of waiting for the reset to finish. (cherry picked from commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e)

Affected products

Linux
  • <a31c3feb54b15a90232e497ad0e27e8a82052d8d
  • <5c29d20470d4566d1b68df57097d642d01f8b427
  • =<6.6.*
  • =<*
  • ==9a98563345697bdb1d3410ff428473b2e781f4db
  • ==6.12
  • <6.11
  • <6.12
  • =<7.0.*
  • ==17a98c942cb106ec08564e8f43b5470a4dd5d3f6
  • =<6.18.*
  • <0ef196a208385b7d7da79f411c161b04e97283e2
  • <6.6.141
  • <61957c2e467b39b528a290016367d32a433fa846
  • <8c4254c8f5836e77ae83e7fc037f02b69f7a0977
  • <6.12
  • =<6.12.*