{
  "cveId": "CVE-2024-47689",
  "url": "https://patchblox.com/security/cve/CVE-2024-47689",
  "summary": "CVE-2024-47689 is fixed in linux on 1 platform, first by DEBIAN-CVE-2024-47689, released October 21, 2024. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to don\u0027t set SB_RDONLY in f2fs_handle_...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to don\u0027t set SB_RDONLY in f2fs_handle_critical_error()  syzbot reports a f2fs bug as below:  ------------[ cut here ]------------ WARNING: CPU: 1 PID: 58 at kernel/rcu/sync.c:177 rcu_sync_dtor\u002B0xcd/0x180 kernel/rcu/sync.c:177 CPU: 1 UID: 0 PID: 58 Comm: kworker/1:2 Not tainted 6.10.0-syzkaller-12562-g1722389b0d86 #0 Workqueue: events destroy_super_work RIP: 0010:rcu_sync_dtor\u002B0xcd/0x180 kernel/rcu/sync.c:177 Call Trace:  percpu_free_rwsem\u002B0x41/0x80 kernel/locking/percpu-rwsem.c:42  destroy_super_work\u002B0xec/0x130 fs/super.c:282  process_one_work kernel/workqueue.c:3231 [inline]  process_scheduled_works\u002B0xa2c/0x1830 kernel/workqueue.c:3312  worker_thread\u002B0x86d/0xd40 kernel/workqueue.c:3390  kthread\u002B0x2f0/0x390 kernel/kthread.c:389  ret_from_fork\u002B0x4b/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm\u002B0x1a/0x30 arch/x86/entry/entry_64.S:244  As Christian Brauner pointed out [1]: the root cause is f2fs sets SB_RDONLY flag in internal function, rather than setting the flag covered w/ sb-\u003Es_umount semaphore via remount procedure, then below race condition causes this bug:  - freeze_super()  - sb_wait_write(sb, SB_FREEZE_WRITE)  - sb_wait_write(sb, SB_FREEZE_PAGEFAULT)  - sb_wait_write(sb, SB_FREEZE_FS) \t\t\t\t\t- f2fs_handle_critical_error \t\t\t\t\t - sb-\u003Es_flags |= SB_RDONLY - thaw_super  - thaw_super_locked   - sb_rdonly() is true, so it skips     sb_freeze_unlock(sb, SB_FREEZE_FS)   - deactivate_locked_super  Since f2fs has almost the same logic as ext4 [2] when handling critical error in filesystem if it mounts w/ errors=remount-ro option: - set CP_ERROR_FLAG flag which indicates filesystem is stopped - record errors to superblock - set SB_RDONLY falg Once we set CP_ERROR_FLAG flag, all writable interfaces can detect the flag and stop any further updates on filesystem. So, it is safe to not set SB_RDONLY flag, let\u0027s remove the logic and keep in line w/ ext4 [3].  [1] https://lore.kernel.org/all/20240729-himbeeren-funknetz-96e62f9c7aee@brauner [2] https://lore.kernel.org/all/20240729132721.hxih6ehigadqf7wx@quack3 [3] https://lore.kernel.org/linux-ext4/20240805201241.27286-1-jack@suse.cz",
  "published": "2024-10-21T12:15:05Z",
  "severity": "medium",
  "cvss": 5.3,
  "cvssVector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00622,
  "epssPercentile": 0.50091,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.11.2-1",
      "fix": "DEBIAN-CVE-2024-47689",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2024-47689",
      "released": "2024-10-21T12:15:05Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.11.2-1",
      "fix": "DEBIAN-CVE-2024-47689",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2024-47689",
      "released": "2024-10-21T12:15:05Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T13:06:02Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}