Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> landlock: Don&amp;#39;t lose track of restrictions on cred_transfer<br /> <br /> When a process&amp;#39; cred struct is replaced, this _almost_ always invokes<br /> the cred_prepare LSM hook; but in one special case (when<br /> KEYCTL_SESSION_TO_PARENT updates the parent&amp;#39;s credentials), the<br /> cred_transfer LSM hook is used instead. Landlock only implements the<br /> cred_prepare hook, not cred_transfer, so KEYCTL_SESSION_TO_PARENT causes<br /> all information on Landlock restrictions to be lost.<br /> <br /> This basically means that a process with the ability to use the fork()<br /> and keyctl() syscalls can get rid of all Landlock restrictions on<br /> itself.<br /> <br /> Fix it by adding a cred_transfer hook that does the same thing as the<br /> existing cred_prepare hook. (Implemented by having hook_cred_prepare()<br /> call hook_cred_transfer() so that the two functions are less likely to<br /> accidentally diverge in the future.)

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> s390/dasd: fix error checks in dasd_copy_pair_store()<br /> <br /> dasd_add_busid() can return an error via ERR_PTR() if an allocation<br /> fails. However, two callsites in dasd_copy_pair_store() do not check<br /> the result, potentially resulting in a NULL pointer dereference. Fix<br /> this by checking the result with IS_ERR() and returning the error up<br /> the stack.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: flow_dissector: use DEBUG_NET_WARN_ON_ONCE<br /> <br /> The following splat is easy to reproduce upstream as well as in -stable<br /> kernels. Florian Westphal provided the following commit:<br /> <br /> d1dab4f71d37 ("net: add and use __skb_get_hash_symmetric_net")<br /> <br /> but this complementary fix has been also suggested by Willem de Bruijn<br /> and it can be easily backported to -stable kernel which consists in<br /> using DEBUG_NET_WARN_ON_ONCE instead to silence the following splat<br /> given __skb_get_hash() is used by the nftables tracing infrastructure to<br /> to identify packets in traces.<br /> <br /> [69133.561393] ------------[ cut here ]------------<br /> [69133.561404] WARNING: CPU: 0 PID: 43576 at net/core/flow_dissector.c:1104 __skb_flow_dissect+0x134f/<br /> [...]<br /> [69133.561944] CPU: 0 PID: 43576 Comm: socat Not tainted 6.10.0-rc7+ #379<br /> [69133.561959] RIP: 0010:__skb_flow_dissect+0x134f/0x2ad0<br /> [69133.561970] Code: 83 f9 04 0f 84 b3 00 00 00 45 85 c9 0f 84 aa 00 00 00 41 83 f9 02 0f 84 81 fc ff<br /> ff 44 0f b7 b4 24 80 00 00 00 e9 8b f9 ff ff 0b e9 20 f3 ff ff 41 f6 c6 20 0f 84 e4 ef ff ff 48 8d 7b 12 e8<br /> [69133.561979] RSP: 0018:ffffc90000006fc0 EFLAGS: 00010246<br /> [69133.561988] RAX: 0000000000000000 RBX: ffffffff82f33e20 RCX: ffffffff81ab7e19<br /> [69133.561994] RDX: dffffc0000000000 RSI: ffffc90000007388 RDI: ffff888103a1b418<br /> [69133.562001] RBP: ffffc90000007310 R08: 0000000000000000 R09: 0000000000000000<br /> [69133.562007] R10: ffffc90000007388 R11: ffffffff810cface R12: ffff888103a1b400<br /> [69133.562013] R13: 0000000000000000 R14: ffffffff82f33e2a R15: ffffffff82f33e28<br /> [69133.562020] FS: 00007f40f7131740(0000) GS:ffff888390800000(0000) knlGS:0000000000000000<br /> [69133.562027] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [69133.562033] CR2: 00007f40f7346ee0 CR3: 000000015d200001 CR4: 00000000001706f0<br /> [69133.562040] Call Trace:<br /> [69133.562044] <br /> [69133.562049] ? __warn+0x9f/0x1a0<br /> [ 1211.841384] ? __skb_flow_dissect+0x107e/0x2860<br /> [...]<br /> [ 1211.841496] ? bpf_flow_dissect+0x160/0x160<br /> [ 1211.841753] __skb_get_hash+0x97/0x280<br /> [ 1211.841765] ? __skb_get_hash_symmetric+0x230/0x230<br /> [ 1211.841776] ? mod_find+0xbf/0xe0<br /> [ 1211.841786] ? get_stack_info_noinstr+0x12/0xe0<br /> [ 1211.841798] ? bpf_ksym_find+0x56/0xe0<br /> [ 1211.841807] ? __rcu_read_unlock+0x2a/0x70<br /> [ 1211.841819] nft_trace_init+0x1b9/0x1c0 [nf_tables]<br /> [ 1211.841895] ? nft_trace_notify+0x830/0x830 [nf_tables]<br /> [ 1211.841964] ? get_stack_info+0x2b/0x80<br /> [ 1211.841975] ? nft_do_chain_arp+0x80/0x80 [nf_tables]<br /> [ 1211.842044] nft_do_chain+0x79c/0x850 [nf_tables]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ipvs: properly dereference pe in ip_vs_add_service<br /> <br /> Use pe directly to resolve sparse warning:<br /> <br /> net/netfilter/ipvs/ip_vs_ctl.c:1471:27: warning: dereference of noderef expression

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: fsl: fsl_qmc_audio: Check devm_kasprintf() returned value<br /> <br /> devm_kasprintf() can return a NULL pointer on failure but this returned<br /> value is not checked.<br /> <br /> Fix this lack and check the returned value.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> erofs: fix race in z_erofs_get_gbuf()<br /> <br /> In z_erofs_get_gbuf(), the current task may be migrated to another<br /> CPU between `z_erofs_gbuf_id()` and `spin_lock(&amp;gbuf-&gt;lock)`.<br /> <br /> Therefore, z_erofs_put_gbuf() will trigger the following issue<br /> which was found by stress test:<br /> <br /> [772156.434168] kernel BUG at fs/erofs/zutil.c:58!<br /> ..<br /> [772156.435007]<br /> [772156.439237] CPU: 0 PID: 3078 Comm: stress Kdump: loaded Tainted: G E 6.10.0-rc7+ #2<br /> [772156.439239] Hardware name: Alibaba Cloud Alibaba Cloud ECS, BIOS 1.0.0 01/01/2017<br /> [772156.439241] pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)<br /> [772156.439243] pc : z_erofs_put_gbuf+0x64/0x70 [erofs]<br /> [772156.439252] lr : z_erofs_lz4_decompress+0x600/0x6a0 [erofs]<br /> ..<br /> [772156.445958] stress (3127): drop_caches: 1<br /> [772156.446120] Call trace:<br /> [772156.446121] z_erofs_put_gbuf+0x64/0x70 [erofs]<br /> [772156.446761] z_erofs_lz4_decompress+0x600/0x6a0 [erofs]<br /> [772156.446897] z_erofs_decompress_queue+0x740/0xa10 [erofs]<br /> [772156.447036] z_erofs_runqueue+0x428/0x8c0 [erofs]<br /> [772156.447160] z_erofs_readahead+0x224/0x390 [erofs]<br /> ..

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: imx-pxp: Fix ERR_PTR dereference in pxp_probe()<br /> <br /> devm_regmap_init_mmio() can fail, add a check and bail out in case of<br /> error.

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> nilfs2: handle inconsistent state in nilfs_btnode_create_block()<br /> <br /> Syzbot reported that a buffer state inconsistency was detected in<br /> nilfs_btnode_create_block(), triggering a kernel bug.<br /> <br /> It is not appropriate to treat this inconsistency as a bug; it can occur<br /> if the argument block address (the buffer index of the newly created<br /> block) is a virtual block number and has been reallocated due to<br /> corruption of the bitmap used to manage its allocation state.<br /> <br /> So, modify nilfs_btnode_create_block() and its callers to treat it as a<br /> possible filesystem error, rather than triggering a kernel bug.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix return value of f2fs_convert_inline_inode()<br /> <br /> If device is readonly, make f2fs_convert_inline_inode()<br /> return EROFS instead of zero, otherwise it may trigger<br /> panic during writeback of inline inode&amp;#39;s dirty page as<br /> below:<br /> <br /> f2fs_write_single_data_page+0xbb6/0x1e90 fs/f2fs/data.c:2888<br /> f2fs_write_cache_pages fs/f2fs/data.c:3187 [inline]<br /> __f2fs_write_data_pages fs/f2fs/data.c:3342 [inline]<br /> f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3369<br /> do_writepages+0x359/0x870 mm/page-writeback.c:2634<br /> filemap_fdatawrite_wbc+0x125/0x180 mm/filemap.c:397<br /> __filemap_fdatawrite_range mm/filemap.c:430 [inline]<br /> file_write_and_wait_range+0x1aa/0x290 mm/filemap.c:788<br /> f2fs_do_sync_file+0x68a/0x1ae0 fs/f2fs/file.c:276<br /> generic_write_sync include/linux/fs.h:2806 [inline]<br /> f2fs_file_write_iter+0x7bd/0x24e0 fs/f2fs/file.c:4977<br /> call_write_iter include/linux/fs.h:2114 [inline]<br /> new_sync_write fs/read_write.c:497 [inline]<br /> vfs_write+0xa72/0xc90 fs/read_write.c:590<br /> ksys_write+0x1a0/0x2c0 fs/read_write.c:643<br /> do_syscall_x64 arch/x86/entry/common.c:52 [inline]<br /> do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83<br /> entry_SYSCALL_64_after_hwframe+0x77/0x7f

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix to don&amp;#39;t dirty inode for readonly filesystem<br /> <br /> syzbot reports f2fs bug as below:<br /> <br /> kernel BUG at fs/f2fs/inode.c:933!<br /> RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933<br /> Call Trace:<br /> evict+0x2a4/0x620 fs/inode.c:664<br /> dispose_list fs/inode.c:697 [inline]<br /> evict_inodes+0x5f8/0x690 fs/inode.c:747<br /> generic_shutdown_super+0x9d/0x2c0 fs/super.c:675<br /> kill_block_super+0x44/0x90 fs/super.c:1667<br /> kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894<br /> deactivate_locked_super+0xc1/0x130 fs/super.c:484<br /> cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256<br /> task_work_run+0x24a/0x300 kernel/task_work.c:180<br /> ptrace_notify+0x2cd/0x380 kernel/signal.c:2399<br /> ptrace_report_syscall include/linux/ptrace.h:411 [inline]<br /> ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]<br /> syscall_exit_work kernel/entry/common.c:251 [inline]<br /> syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline]<br /> __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]<br /> syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296<br /> do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88<br /> entry_SYSCALL_64_after_hwframe+0x63/0x6b<br /> <br /> The root cause is:<br /> - do_sys_open<br /> - f2fs_lookup<br /> - __f2fs_find_entry<br /> - f2fs_i_depth_write<br /> - f2fs_mark_inode_dirty_sync<br /> - f2fs_dirty_inode<br /> - set_inode_flag(inode, FI_DIRTY_INODE)<br /> <br /> - umount<br /> - kill_f2fs_super<br /> - kill_block_super<br /> - generic_shutdown_super<br /> - sync_filesystem<br /> : sb is readonly, skip sync_filesystem()<br /> - evict_inodes<br /> - iput<br /> - f2fs_evict_inode<br /> - f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE))<br /> : trigger kernel panic<br /> <br /> When we try to repair i_current_depth in readonly filesystem, let&amp;#39;s<br /> skip dirty inode to avoid panic in later f2fs_evict_inode().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fs/ntfs3: Update log-&gt;page_{mask,bits} if log-&gt;page_size changed<br /> <br /> If an NTFS file system is mounted to another system with different<br /> PAGE_SIZE from the original system, log-&gt;page_size will change in<br /> log_replay(), but log-&gt;page_{mask,bits} don&amp;#39;t change correspondingly.<br /> This will cause a panic because "u32 bytes = log-&gt;page_size - page_off"<br /> will get a negative value in the later read_log_page().