Nixpkgs security tracker

Login with GitHub

Suggestion detail

Dismissed
(max. allowed matches exceeded)
Permalink CVE-2026-63844
7.8 HIGH
  • CVSS version (CVSS): 3.1
  • Attack Vector (AV): Local (L)
  • Attack Complexity (AC): Low (L)
  • Privileges Required (PR): Low (L)
  • User Interaction (UI): None (N)
  • Scope (S): Unchanged (U)
  • Confidentiality (C): High (H)
  • Integrity (I): High (H)
  • Availability (A): High (H)
  • Modified Attack Vector (MAV): Local (L)
  • Modified Attack Complexity (MAC): Low (L)
  • Modified Privileges Required (MPR): Low (L)
  • Modified User Interaction (MUI): None (N)
  • Modified Confidentiality (MC): High (H)
  • Modified Scope (MS): Unchanged (U)
  • Modified Integrity (MI): High (H)
  • Modified Availability (MA): High (H)
created 5 days, 13 hours ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring JPEG rings do not support 64-bit user fence writes, reject CS submissions with user fences. (cherry picked from commit 2f6afc97d259d530f4f86c7743efbc573a8da927)

Affected products

Linux
  • <83e37c0987ca92f9e87789b46dd311dcf5a4a6c8
  • <d6bd2a5fd611ec9c8a2411f084cff2435c709608
  • =<6.18.*
  • =<7.0.*
  • =<6.12.*
  • <b884ff67d62ef514eee9d5f605c03101c8b6bc98
  • =<*
  • =<6.6.*
  • ==6.5
  • <8549b3933038e68dc61cb934b9a54223dd244a78
  • <249fa7549736de1c8e327d7ca6b32fa148a40bd6
  • <6.5