{
  "cveId": "CVE-2024-42266",
  "url": "https://patchblox.com/security/cve/CVE-2024-42266",
  "summary": "CVE-2024-42266 is fixed in linux on 1 platform, first by DEBIAN-CVE-2024-42266, released August 17, 2024. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  btrfs: make cow_file_range_inline() honor locked...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  btrfs: make cow_file_range_inline() honor locked_page on error  The btrfs buffered write path runs through __extent_writepage() which has some tricky return value handling for writepage_delalloc(). Specifically, when that returns 1, we exit, but for other return values we continue and end up calling btrfs_folio_end_all_writers(). If the folio has been unlocked (note that we check the PageLocked bit at the start of __extent_writepage()), this results in an assert panic like this one from syzbot:    BTRFS: error (device loop0 state EAL) in free_log_tree:3267: errno=-5 IO failure   BTRFS warning (device loop0 state EAL): Skipping commit of aborted transaction.   BTRFS: error (device loop0 state EAL) in cleanup_transaction:2018: errno=-5 IO failure   assertion failed: folio_test_locked(folio), in fs/btrfs/subpage.c:871   ------------[ cut here ]------------   kernel BUG at fs/btrfs/subpage.c:871!   Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI   CPU: 1 PID: 5090 Comm: syz-executor225 Not tainted   6.10.0-syzkaller-05505-gb1bc554e009e #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS   Google 06/27/2024   RIP: 0010:btrfs_folio_end_all_writers\u002B0x55b/0x610 fs/btrfs/subpage.c:871   Code: e9 d3 fb ff ff e8 25 22 c2 fd 48 c7 c7 c0 3c 0e 8c 48 c7 c6 80 3d   0e 8c 48 c7 c2 60 3c 0e 8c b9 67 03 00 00 e8 66 47 ad 07 90 \u003C0f\u003E 0b e8   6e 45 b0 07 4c 89 ff be 08 00 00 00 e8 21 12 25 fe 4c 89   RSP: 0018:ffffc900033d72e0 EFLAGS: 00010246   RAX: 0000000000000045 RBX: 00fff0000000402c RCX: 663b7a08c50a0a00   RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000   RBP: ffffc900033d73b0 R08: ffffffff8176b98c R09: 1ffff9200067adfc   R10: dffffc0000000000 R11: fffff5200067adfd R12: 0000000000000001   R13: dffffc0000000000 R14: 0000000000000000 R15: ffffea0001cbee80   FS:  0000000000000000(0000) GS:ffff8880b9500000(0000)   knlGS:0000000000000000   CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033   CR2: 00007f5f076012f8 CR3: 000000000e134000 CR4: 00000000003506f0   DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000   DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400   Call Trace:   \u003CTASK\u003E   __extent_writepage fs/btrfs/extent_io.c:1597 [inline]   extent_write_cache_pages fs/btrfs/extent_io.c:2251 [inline]   btrfs_writepages\u002B0x14d7/0x2760 fs/btrfs/extent_io.c:2373   do_writepages\u002B0x359/0x870 mm/page-writeback.c:2656   filemap_fdatawrite_wbc\u002B0x125/0x180 mm/filemap.c:397   __filemap_fdatawrite_range mm/filemap.c:430 [inline]   __filemap_fdatawrite mm/filemap.c:436 [inline]   filemap_flush\u002B0xdf/0x130 mm/filemap.c:463   btrfs_release_file\u002B0x117/0x130 fs/btrfs/file.c:1547   __fput\u002B0x24a/0x8a0 fs/file_table.c:422   task_work_run\u002B0x24f/0x310 kernel/task_work.c:222   exit_task_work include/linux/task_work.h:40 [inline]   do_exit\u002B0xa2f/0x27f0 kernel/exit.c:877   do_group_exit\u002B0x207/0x2c0 kernel/exit.c:1026   __do_sys_exit_group kernel/exit.c:1037 [inline]   __se_sys_exit_group kernel/exit.c:1035 [inline]   __x64_sys_exit_group\u002B0x3f/0x40 kernel/exit.c:1035   x64_sys_call\u002B0x2634/0x2640   arch/x86/include/generated/asm/syscalls_64.h:232   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64\u002B0xf3/0x230 arch/x86/entry/common.c:83   entry_SYSCALL_64_after_hwframe\u002B0x77/0x7f   RIP: 0033:0x7f5f075b70c9   Code: Unable to access opcode bytes at   0x7f5f075b709f.  I was hitting the same issue by doing hundreds of accelerated runs of generic/475, which also hits IO errors by design.  I instrumented that reproducer with bpftrace and found that the undesirable folio_unlock was coming from the following callstack:    folio_unlock\u002B5   __process_pages_contig\u002B475   cow_file_range_inline.constprop.0\u002B230   cow_file_range\u002B803   btrfs_run_delalloc_range\u002B566   writepage_delalloc\u002B332   __extent_writepage # inlined in my stacktrace, but I added it here   extent_write_cache_pages\u002B622  Looking at the bisected-to pa ---truncated---",
  "published": "2024-08-17T09:15:07Z",
  "severity": "medium",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00203,
  "epssPercentile": 0.10365,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.10.4-1",
      "fix": "DEBIAN-CVE-2024-42266",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2024-42266",
      "released": "2024-08-17T09:15:07Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.10.4-1",
      "fix": "DEBIAN-CVE-2024-42266",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2024-42266",
      "released": "2024-08-17T09:15:07Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-09T01:18:40Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}