Nixpkgs security tracker

Login with GitHub

Suggestion detail

Dismissed
(max. allowed matches exceeded)
Permalink CVE-2026-63802
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, 5 hours ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
blk-cgroup: fix UAF in __blkcg_rstat_flush()

In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix UAF in __blkcg_rstat_flush() When multiple blkgs in the same blkcg are released concurrently, a use-after-free can occur. The race happens when one blkg's __blkcg_rstat_flush() removes another blkg's iostat entries via llist_del_all(). The second blkg sees an empty list and proceeds to free itself while the first is still iterating over its entries. Move the flush from __blkg_release() (RCU callback) to blkg_release() (before call_rcu). This ensures the RCU grace period waits for any concurrent flush's rcu_read_lock() section to complete before freeing.

Affected products

Linux
  • <afebe44facc48a61761e885bbb7f0380d4a603ec
  • =<6.18.*
  • ==6.4
  • =<6.12.*
  • =<7.1.*
  • <6.4
  • <bbebd9425cad3573d1527441753899b926525a0f
  • ==0f6090d90f627d8c58f939067d6c6821ce1b3c68
  • =<*
  • =<6.6.*
  • <96e545410c4f74c89d496c1d5d9ef8d08f14368b
  • <5e5b7f2ef854936e95dceb6a2fdfefcb7152d2c6
  • <0ab5ee5a1badb58cbb2242617cb01a4972b1f2a2
  • <6.4