Nixpkgs security tracker

Login with GitHub

Suggestion detail

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

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

Affected products

Linux
  • <f675801889b265634aefd30aa4503fc2b9e6ce1c
  • =<6.18.*
  • =<7.0.*
  • <e5f612dc91650561fe2b5b76dd6d2898ec9ad480
  • =<6.12.*
  • <b41248d1c18384835f6532e68592ee07605da283
  • <5.6
  • =<6.6.*
  • =<*
  • ==5.6
  • <2e216c2ff159b2eb1da6e9c716d727efc73c64b5
  • <41c4f3f68a343d62bd352a95ace93a11c4ad92ed