Nixpkgs security tracker

Login with GitHub

Suggestion detail

Dismissed
(max. allowed matches exceeded)
Permalink CVE-2026-63847
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 6 days, 3 hours ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion 6 days, 3 hours ago
drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring

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

Affected products

Linux
  • <79405e774ede411c6b47ed41c651e40b92de64a2
  • <63691e396105611173072ad548fc2b68831ecf23
  • =<6.18.*
  • <4d96e3cbfc66e4d66ea0096bde858e28ab62da00
  • =<7.0.*
  • =<6.12.*
  • <694fe016969c5e5a24b9e0ef7c1307eedec8ddf8
  • ==5.6
  • <5.6
  • =<6.6.*
  • <3a96fee676fc0caf08f03ad915bec6fcd144d551
  • =<*