Nixpkgs security tracker

Try the new UI
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)
Permalink CVE-2026-89832
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 1 week, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
f2fs: fix to clear dirty flag on folio in error path

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to clear dirty flag on folio in error path If node block is corrupted due to chksum mismatch or inconsistent footer info, it needs to drop clear flag of node folio, in order to persist inconsistent node data to storage.

Affected products

Linux
  • ==8d7ebdd109b4654ec5e0e9c3c6f08b06d6558f10
  • =<7.2.*
  • <5b86eab84ac8e9289b5afc52ef88ab18ba5bacab
  • <ab35ae07f2b5b4e118ea47b88577fc7d0e797b17
  • <5.2
  • <4.20
  • =<6.18.*
  • =<*
  • ==b039536485970829918aa237a08417bd0ed5437c
  • <3923ec2b98c96dda4a8bfab81d22553dbf0dd6c2
  • <5.2
  • ==5.2