Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> btrfs: fix error propagation of split bios<br /> <br /> The purpose of btrfs_bbio_propagate_error() shall be propagating an error<br /> of split bio to its original btrfs_bio, and tell the error to the upper<br /> layer. However, it&amp;#39;s not working well on some cases.<br /> <br /> * Case 1. Immediate (or quick) end_bio with an error<br /> <br /> When btrfs sends btrfs_bio to mirrored devices, btrfs calls<br /> btrfs_bio_end_io() when all the mirroring bios are completed. If that<br /> btrfs_bio was split, it is from btrfs_clone_bioset and its end_io function<br /> is btrfs_orig_write_end_io. For this case, btrfs_bbio_propagate_error()<br /> accesses the orig_bbio&amp;#39;s bio context to increase the error count.<br /> <br /> That works well in most cases. However, if the end_io is called enough<br /> fast, orig_bbio&amp;#39;s (remaining part after split) bio context may not be<br /> properly set at that time. Since the bio context is set when the orig_bbio<br /> (the last btrfs_bio) is sent to devices, that might be too late for earlier<br /> split btrfs_bio&amp;#39;s completion. That will result in NULL pointer<br /> dereference.<br /> <br /> That bug is easily reproducible by running btrfs/146 on zoned devices [1]<br /> and it shows the following trace.<br /> <br /> [1] You need raid-stripe-tree feature as it create "-d raid0 -m raid1" FS.<br /> <br /> BUG: kernel NULL pointer dereference, address: 0000000000000020<br /> #PF: supervisor read access in kernel mode<br /> #PF: error_code(0x0000) - not-present page<br /> PGD 0 P4D 0<br /> Oops: Oops: 0000 [#1] PREEMPT SMP PTI<br /> CPU: 1 UID: 0 PID: 13 Comm: kworker/u32:1 Not tainted 6.11.0-rc7-BTRFS-ZNS+ #474<br /> Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011<br /> Workqueue: writeback wb_workfn (flush-btrfs-5)<br /> RIP: 0010:btrfs_bio_end_io+0xae/0xc0 [btrfs]<br /> BTRFS error (device dm-0): bdev /dev/mapper/error-test errs: wr 2, rd 0, flush 0, corrupt 0, gen 0<br /> RSP: 0018:ffffc9000006f248 EFLAGS: 00010246<br /> RAX: 0000000000000000 RBX: ffff888005a7f080 RCX: ffffc9000006f1dc<br /> RDX: 0000000000000000 RSI: 000000000000000a RDI: ffff888005a7f080<br /> RBP: ffff888011dfc540 R08: 0000000000000000 R09: 0000000000000001<br /> R10: ffffffff82e508e0 R11: 0000000000000005 R12: ffff88800ddfbe58<br /> R13: ffff888005a7f080 R14: ffff888005a7f158 R15: ffff888005a7f158<br /> FS: 0000000000000000(0000) GS:ffff88803ea80000(0000) knlGS:0000000000000000<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> CR2: 0000000000000020 CR3: 0000000002e22006 CR4: 0000000000370ef0<br /> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br /> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400<br /> Call Trace:<br /> <br /> ? __die_body.cold+0x19/0x26<br /> ? page_fault_oops+0x13e/0x2b0<br /> ? _printk+0x58/0x73<br /> ? do_user_addr_fault+0x5f/0x750<br /> ? exc_page_fault+0x76/0x240<br /> ? asm_exc_page_fault+0x22/0x30<br /> ? btrfs_bio_end_io+0xae/0xc0 [btrfs]<br /> ? btrfs_log_dev_io_error+0x7f/0x90 [btrfs]<br /> btrfs_orig_write_end_io+0x51/0x90 [btrfs]<br /> dm_submit_bio+0x5c2/0xa50 [dm_mod]<br /> ? find_held_lock+0x2b/0x80<br /> ? blk_try_enter_queue+0x90/0x1e0<br /> __submit_bio+0xe0/0x130<br /> ? ktime_get+0x10a/0x160<br /> ? lockdep_hardirqs_on+0x74/0x100<br /> submit_bio_noacct_nocheck+0x199/0x410<br /> btrfs_submit_bio+0x7d/0x150 [btrfs]<br /> btrfs_submit_chunk+0x1a1/0x6d0 [btrfs]<br /> ? lockdep_hardirqs_on+0x74/0x100<br /> ? __folio_start_writeback+0x10/0x2c0<br /> btrfs_submit_bbio+0x1c/0x40 [btrfs]<br /> submit_one_bio+0x44/0x60 [btrfs]<br /> submit_extent_folio+0x13f/0x330 [btrfs]<br /> ? btrfs_set_range_writeback+0xa3/0xd0 [btrfs]<br /> extent_writepage_io+0x18b/0x360 [btrfs]<br /> extent_write_locked_range+0x17c/0x340 [btrfs]<br /> ? __pfx_end_bbio_data_write+0x10/0x10 [btrfs]<br /> run_delalloc_cow+0x71/0xd0 [btrfs]<br /> btrfs_run_delalloc_range+0x176/0x500 [btrfs]<br /> ? find_lock_delalloc_range+0x119/0x260 [btrfs]<br /> writepage_delalloc+0x2ab/0x480 [btrfs]<br /> extent_write_cache_pages+0x236/0x7d0 [btrfs]<br /> btrfs_writepages+0x72/0x130 [btrfs]<br /> do_writepages+0xd4/0x240<br /> ? find_held_lock+0x2b/0x80<br /> ? wbc_attach_and_unlock_inode+0x12c/0x290<br /> ? wbc_attach_and_unlock_inode+0x12c/0x29<br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ocfs2: pass u64 to ocfs2_truncate_inline maybe overflow<br /> <br /> Syzbot reported a kernel BUG in ocfs2_truncate_inline. There are two<br /> reasons for this: first, the parameter value passed is greater than<br /> ocfs2_max_inline_data_with_xattr, second, the start and end parameters of<br /> ocfs2_truncate_inline are "unsigned int".<br /> <br /> So, we need to add a sanity check for byte_start and byte_len right before<br /> ocfs2_truncate_inline() in ocfs2_remove_inode_range(), if they are greater<br /> than ocfs2_max_inline_data_with_xattr return -EINVAL.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/tests: hdmi: Fix memory leaks in drm_display_mode_from_cea_vic()<br /> <br /> modprobe drm_hdmi_state_helper_test and then rmmod it, the following<br /> memory leak occurs.<br /> <br /> The `mode` allocated in drm_mode_duplicate() called by<br /> drm_display_mode_from_cea_vic() is not freed, which cause the memory leak:<br /> <br /> unreferenced object 0xffffff80ccd18100 (size 128):<br /> comm "kunit_try_catch", pid 1851, jiffies 4295059695<br /> hex dump (first 32 bytes):<br /> 57 62 00 00 80 02 90 02 f0 02 20 03 00 00 e0 01 Wb........ .....<br /> ea 01 ec 01 0d 02 00 00 0a 00 00 00 00 00 00 00 ................<br /> backtrace (crc c2f1aa95):<br /> [] kmemleak_alloc+0x34/0x40<br /> [] __kmalloc_cache_noprof+0x26c/0x2f4<br /> [] drm_mode_duplicate+0x44/0x19c<br /> [] drm_display_mode_from_cea_vic+0x88/0x98<br /> [] 0xffffffedc11ae69c<br /> [] kunit_try_run_case+0x13c/0x3ac<br /> [] kunit_generic_run_threadfn_adapter+0x80/0xec<br /> [] kthread+0x2e8/0x374<br /> [] ret_from_fork+0x10/0x20<br /> ......<br /> <br /> Free `mode` by using drm_kunit_display_mode_from_cea_vic()<br /> to fix it.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/connector: hdmi: Fix memory leak in drm_display_mode_from_cea_vic()<br /> <br /> modprobe drm_connector_test and then rmmod drm_connector_test,<br /> the following memory leak occurs.<br /> <br /> The `mode` allocated in drm_mode_duplicate() called by<br /> drm_display_mode_from_cea_vic() is not freed, which cause the memory leak:<br /> <br /> unreferenced object 0xffffff80cb0ee400 (size 128):<br /> comm "kunit_try_catch", pid 1948, jiffies 4294950339<br /> hex dump (first 32 bytes):<br /> 14 44 02 00 80 07 d8 07 04 08 98 08 00 00 38 04 .D............8.<br /> 3c 04 41 04 65 04 00 00 05 00 00 00 00 00 00 00

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> xfs: fix finding a last resort AG in xfs_filestream_pick_ag<br /> <br /> When the main loop in xfs_filestream_pick_ag fails to find a suitable<br /> AG it tries to just pick the online AG. But the loop for that uses<br /> args-&gt;pag as loop iterator while the later code expects pag to be<br /> set. Fix this by reusing the max_pag case for this last resort, and<br /> also add a check for impossible case of no AG just to make sure that<br /> the uninitialized pag doesn&amp;#39;t even escape in theory.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> nvmet-auth: assign dh_key to NULL after kfree_sensitive<br /> <br /> ctrl-&gt;dh_key might be used across multiple calls to nvmet_setup_dhgroup()<br /> for the same controller. So it&amp;#39;s better to nullify it after release on<br /> error path in order to avoid double free later in nvmet_destroy_auth().<br /> <br /> Found by Linux Verification Center (linuxtesting.org) with Svace.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> lib: alloc_tag_module_unload must wait for pending kfree_rcu calls<br /> <br /> Ben Greear reports following splat:<br /> ------------[ cut here ]------------<br /> net/netfilter/nf_nat_core.c:1114 module nf_nat func:nf_nat_register_fn has 256 allocated at module unload<br /> WARNING: CPU: 1 PID: 10421 at lib/alloc_tag.c:168 alloc_tag_module_unload+0x22b/0x3f0<br /> Modules linked in: nf_nat(-) btrfs ufs qnx4 hfsplus hfs minix vfat msdos fat<br /> ...<br /> Hardware name: Default string Default string/SKYBAY, BIOS 5.12 08/04/2020<br /> RIP: 0010:alloc_tag_module_unload+0x22b/0x3f0<br /> codetag_unload_module+0x19b/0x2a0<br /> ? codetag_load_module+0x80/0x80<br /> <br /> nf_nat module exit calls kfree_rcu on those addresses, but the free<br /> operation is likely still pending by the time alloc_tag checks for leaks.<br /> <br /> Wait for outstanding kfree_rcu operations to complete before checking<br /> resolves this warning.<br /> <br /> Reproducer:<br /> unshare -n iptables-nft -t nat -A PREROUTING -p tcp<br /> grep nf_nat /proc/allocinfo # will list 4 allocations<br /> rmmod nft_chain_nat<br /> rmmod nf_nat # will WARN.<br /> <br /> [akpm@linux-foundation.org: add comment]

Improper Neutralization of Input During Web Page Generation (&amp;#39;Cross-site Scripting&amp;#39;) vulnerability in Jason Coleman Don&amp;#39;t Break The Code dont-break-the-code allows Reflected XSS.This issue affects Don&amp;#39;t Break The Code: from n/a through

Improper Neutralization of Input During Web Page Generation (&amp;#39;Cross-site Scripting&amp;#39;) vulnerability in eewee eewee admin custom eewee-admincustom allows Reflected XSS.This issue affects eewee admin custom: from n/a through

Improper Neutralization of Input During Web Page Generation (&amp;#39;Cross-site Scripting&amp;#39;) vulnerability in Stefan Backor Firework Shoppable Live Video firework-videos allows Reflected XSS.This issue affects Firework Shoppable Live Video: from n/a through

Improper Neutralization of Input During Web Page Generation (&amp;#39;Cross-site Scripting&amp;#39;) vulnerability in Sam Hotchkiss Daily Image daily-image allows Reflected XSS.This issue affects Daily Image: from n/a through

Improper Neutralization of Input During Web Page Generation (&amp;#39;Cross-site Scripting&amp;#39;) vulnerability in Tevya Satisfaction Reports from Help Scout happiness-reports-for-help-scout allows Reflected XSS.This issue affects Satisfaction Reports from Help Scout: from n/a through