Vulnerabilities

pgAdmin

Dell PowerEdge Server BIOS contains an TOCTOU race condition vulnerability. A local low privileged attacker could potentially exploit this vulnerability to gain access to otherwise unauthorized resources.

Due to an improper input validation, an unauthenticated threat actor can send a malicious message to invoke a local or remote executable and cause a remote code execution condition on the Rockwell Automation ThinManager® ThinServer™.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: mgb4: Fix double debugfs remove<br /> <br /> Fixes an error where debugfs_remove_recursive() is called first on a parent<br /> directory and then again on a child which causes a kernel panic.<br /> <br /> [hverkuil: added Fixes/Cc tags]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> thermal/drivers/qcom/lmh: Check for SCM availability at probe<br /> <br /> Up until now, the necessary scm availability check has not been<br /> performed, leading to possible null pointer dereferences (which did<br /> happen for me on RB1).<br /> <br /> Fix that.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode()<br /> <br /> syzbot reports a kernel bug as below:<br /> <br /> F2FS-fs (loop0): Mounted with checkpoint version = 48b305e4<br /> ==================================================================<br /> BUG: KASAN: slab-out-of-bounds in f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline]<br /> BUG: KASAN: slab-out-of-bounds in current_nat_addr fs/f2fs/node.h:213 [inline]<br /> BUG: KASAN: slab-out-of-bounds in f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600<br /> Read of size 1 at addr ffff88807a58c76c by task syz-executor280/5076<br /> <br /> CPU: 1 PID: 5076 Comm: syz-executor280 Not tainted 6.9.0-rc5-syzkaller #0<br /> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024<br /> Call Trace:<br /> <br /> __dump_stack lib/dump_stack.c:88 [inline]<br /> dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114<br /> print_address_description mm/kasan/report.c:377 [inline]<br /> print_report+0x169/0x550 mm/kasan/report.c:488<br /> kasan_report+0x143/0x180 mm/kasan/report.c:601<br /> f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline]<br /> current_nat_addr fs/f2fs/node.h:213 [inline]<br /> f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600<br /> f2fs_xattr_fiemap fs/f2fs/data.c:1848 [inline]<br /> f2fs_fiemap+0x55d/0x1ee0 fs/f2fs/data.c:1925<br /> ioctl_fiemap fs/ioctl.c:220 [inline]<br /> do_vfs_ioctl+0x1c07/0x2e50 fs/ioctl.c:838<br /> __do_sys_ioctl fs/ioctl.c:902 [inline]<br /> __se_sys_ioctl+0x81/0x170 fs/ioctl.c:890<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<br /> <br /> The root cause is we missed to do sanity check on i_xattr_nid during<br /> f2fs_iget(), so that in fiemap() path, current_nat_addr() will access<br /> nat_bitmap w/ offset from invalid i_xattr_nid, result in triggering<br /> kasan bug report, fix it.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> smb: client: fix deadlock in smb2_find_smb_tcon()<br /> <br /> Unlock cifs_tcp_ses_lock before calling cifs_put_smb_ses() to avoid such<br /> deadlock.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> eventfs: Fix a possible null pointer dereference in eventfs_find_events()<br /> <br /> In function eventfs_find_events,there is a potential null pointer<br /> that may be caused by calling update_events_attr which will perform<br /> some operations on the members of the ei struct when ei is NULL.<br /> <br /> Hence,When ei-&gt;is_freed is set,return NULL directly.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu: add error handle to avoid out-of-bounds<br /> <br /> if the sdma_v4_0_irq_id_to_seq return -EINVAL, the process should<br /> be stop to avoid out-of-bounds read, so directly return -EINVAL.

Improper Authentication vulnerability in Progress MOVEit Gateway (SFTP modules) allows Authentication Bypass.This issue affects MOVEit Gateway: 2024.0.0.

Improper Authentication vulnerability in Progress MOVEit Transfer (SFTP module) can lead to Authentication Bypass.This issue affects MOVEit Transfer: from 2023.0.0 before 2023.0.11, from 2023.1.0 before 2023.1.6, from 2024.0.0 before 2024.0.2.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> nilfs2: fix nilfs_empty_dir() misjudgment and long loop on I/O errors<br /> <br /> The error handling in nilfs_empty_dir() when a directory folio/page read<br /> fails is incorrect, as in the old ext2 implementation, and if the<br /> folio/page cannot be read or nilfs_check_folio() fails, it will falsely<br /> determine the directory as empty and corrupt the file system.<br /> <br /> In addition, since nilfs_empty_dir() does not immediately return on a<br /> failed folio/page read, but continues to loop, this can cause a long loop<br /> with I/O if i_size of the directory&amp;#39;s inode is also corrupted, causing the<br /> log writer thread to wait and hang, as reported by syzbot.<br /> <br /> Fix these issues by making nilfs_empty_dir() immediately return a false<br /> value (0) if it fails to get a directory folio/page.