In the Linux kernel, the following vulnerability has been resolved: x86: fix clear_user_rep_good() exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 ("x86: don't use REP_GOOD or ERMS for user memory clearing") upstream. However, rather than backport the full range of x86 memory clearing and copying cleanups, fix the exception table annotation placement for the final 'rep movsb' in clear_user_rep_good(): rather than pointing at the actual instruction that did the user space access, it pointed to the register move just before it. That made sense from a code flow standpoint, but not from an actual usage standpoint: it means that if user access takes an exception, the exception handler won't actually find the instruction in the exception tables. As a result, rather than fixing it up and returning -EFAULT, it would then turn it into a kernel oops report instead, something like: BUG: unable to handle page fault for address: 0000000020081000 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page ... RIP: 0010:clear_user_rep_good+0x1c/0x30 arch/x86/lib/clear_page_64.S:147 ... Call Trace: __clear_user arch/x86/include/asm/uaccess_64.h:103 [inline] clear_user arch/x86/include/asm/uaccess_64.h:124 [inline] iov_iter_zero+0x709/0x1290 lib/iov_iter.c:800 iomap_dio_hole_iter fs/iomap/direct-io.c:389 [inline] iomap_dio_iter fs/iomap/direct-io.c:440 [inline] __iomap_dio_rw+0xe3d/0x1cd0 fs/iomap/direct-io.c:601 iomap_dio_rw+0x40/0xa0 fs/iomap/direct-io.c:689 ext4_dio_read_iter fs/ext4/file.c:94 [inline] ext4_file_read_iter+0x4be/0x690 fs/ext4/file.c:145 call_read_iter include/linux/fs.h:2183 [inline] do_iter_readv_writev+0x2e0/0x3b0 fs/read_write.c:733 do_iter_read+0x2f2/0x750 fs/read_write.c:796 vfs_readv+0xe5/0x150 fs/read_write.c:916 do_preadv+0x1b6/0x270 fs/read_write.c:1008 __do_sys_preadv2 fs/read_write.c:1070 [inline] __se_sys_preadv2 fs/read_write.c:1061 [inline] __x64_sys_preadv2+0xef/0x150 fs/read_write.c:1061 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd which then looks like a filesystem bug rather than the incorrect exception annotation that it is. [ The alternative to this one-liner fix is to take the upstream series that cleans this all up: 68674f94ffc9 ("x86: don't use REP_GOOD or ERMS for small memory copies") 20f3337d350c ("x86: don't use REP_GOOD or ERMS for small memory clearing") adfcf4231b8c ("x86: don't use REP_GOOD or ERMS for user memory copies") * d2c95f9d6802 ("x86: don't use REP_GOOD or ERMS for user memory clearing") 3639a535587d ("x86: move stac/clac from user copy routines into callers") 577e6a7fd50d ("x86: inline the 'rep movs' in user copies for the FSRM case") 8c9b6a88b7e2 ("x86: improve on the non-rep 'clear_user' function") 427fda2c8a49 ("x86: improve on the non-rep 'copy_user' function") * e046fe5a36a9 ("x86: set FSRS automatically on AMD CPUs that have FSRM") e1f2750edc4a ("x86: remove 'zerorest' argument from __copy_user_nocache()") 034ff37d3407 ("x86: rewrite '__copy_user_nocache' function") with either the whole series or at a minimum the two marked commits being needed to fix this issue ]

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - x86: fix clear_user_rep_good() exception handling annotation This code no longer exists in mainline,     because it was removed in commit d2c95f9d6802 (x86: don't use REP_GOOD or ERMS for user memory clearing)     upstream. However, rather than backport the full range of x86 memory clearing and copying cleanups, fix     the exception table annotation placement for the final 'rep movsb' in clear_user_rep_good(): rather than     pointing at the actual instruction that did the user space access, it pointed to the register move just     before it. That made sense from a code flow standpoint, but not from an actual usage standpoint: it means     that if user access takes an exception, the exception handler won't actually find the instruction in the     exception tables. As a result, rather than fixing it up and returning -EFAULT, it would then turn it into     a kernel oops report instead, something like: BUG: unable to handle page fault for address:
    0000000020081000 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page     ... RIP: 0010:clear_user_rep_good+0x1c/0x30 arch/x86/lib/clear_page_64.S:147 ... Call Trace: __clear_user     arch/x86/include/asm/uaccess_64.h:103 [inline] clear_user arch/x86/include/asm/uaccess_64.h:124 [inline]     iov_iter_zero+0x709/0x1290 lib/iov_iter.c:800 iomap_dio_hole_iter fs/iomap/direct-io.c:389 [inline]     iomap_dio_iter fs/iomap/direct-io.c:440 [inline] __iomap_dio_rw+0xe3d/0x1cd0 fs/iomap/direct-io.c:601     iomap_dio_rw+0x40/0xa0 fs/iomap/direct-io.c:689 ext4_dio_read_iter fs/ext4/file.c:94 [inline]     ext4_file_read_iter+0x4be/0x690 fs/ext4/file.c:145 call_read_iter include/linux/fs.h:2183 [inline]     do_iter_readv_writev+0x2e0/0x3b0 fs/read_write.c:733 do_iter_read+0x2f2/0x750 fs/read_write.c:796     vfs_readv+0xe5/0x150 fs/read_write.c:916 do_preadv+0x1b6/0x270 fs/read_write.c:1008 __do_sys_preadv2     fs/read_write.c:1070 [inline] __se_sys_preadv2 fs/read_write.c:1061 [inline] __x64_sys_preadv2+0xef/0x150     fs/read_write.c:1061 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd which then looks like a filesystem bug     rather than the incorrect exception annotation that it is. [ The alternative to this one-liner fix is to     take the upstream series that cleans this all up: 68674f94ffc9 (x86: don't use REP_GOOD or ERMS for small     memory copies) 20f3337d350c (x86: don't use REP_GOOD or ERMS for small memory clearing) adfcf4231b8c     (x86: don't use REP_GOOD or ERMS for user memory copies) * d2c95f9d6802 (x86: don't use REP_GOOD or     ERMS for user memory clearing) 3639a535587d (x86: move stac/clac from user copy routines into callers)     577e6a7fd50d (x86: inline the 'rep movs' in user copies for the FSRM case) 8c9b6a88b7e2 (x86: improve     on the non-rep 'clear_user' function) 427fda2c8a49 (x86: improve on the non-rep 'copy_user' function) *     e046fe5a36a9 (x86: set FSRS automatically on AMD CPUs that have FSRM) e1f2750edc4a (x86: remove     'zerorest' argument from __copy_user_nocache()) 034ff37d3407 (x86: rewrite '__copy_user_nocache'     function) with either the whole series or at a minimum the two marked commits being needed to fix this     issue ] (CVE-2023-53642)

Note that Nessus relies on the presence of the package as reported by the vendor.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2023-184 advisory.

    There is a potential deadlock in the eBPF subsystem in the Linux kernel.

    The default sysctl configuration kernel.unprivileged_bpf_disabled on Amazon Linux does not allow     unprivileged users to use eBPF. (CVE-2023-0160)

    A denial of service problem was found, due to a possible recursive locking scenario, resulting in a     deadlock in table_clear in drivers/md/dm-ioctl.c in the Linux Kernel Device Mapper-Multipathing sub-     component. (CVE-2023-2269)

    In the Linux kernel through 6.3.1, a use-after-free in Netfilter nf_tables when processing batch requests     can be abused to perform arbitrary read and write operations on kernel memory. Unprivileged local users     can obtain root privileges. This occurs because anonymous sets are mishandled. (CVE-2023-32233)

    An issue was discovered in the Linux kernel before 6.3.3. There is an out-of-bounds read in crc16 in     lib/crc16.c when called from fs/ext4/super.c because ext4_group_desc_csum does not properly check an     offset. (CVE-2023-34256)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: fix i_disksize exceeding i_size problem in paritally written case (CVE-2023-53270)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: add bounds checking in get_max_inline_xattr_value_size() (CVE-2023-53285)

    In the Linux kernel, the following vulnerability has been resolved:

    fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs_lookup() (CVE-2023-53294)

    In the Linux kernel, the following vulnerability has been resolved:

    md/raid10: fix leak of 'r10bio->remaining' for recovery (CVE-2023-53299)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: fix WARNING in mb_find_extent (CVE-2023-53317)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: remove a BUG_ON in ext4_mb_release_group_pa() (CVE-2023-53450)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: improve error handling from ext4_dirhash() (CVE-2023-53473)

    In the Linux kernel, the following vulnerability has been resolved:

    x86/MCE/AMD: Use an u64 for bank_map (CVE-2023-53474)

    In the Linux kernel, the following vulnerability has been resolved:

    tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp. (CVE-2023-53489)

    In the Linux kernel, the following vulnerability has been resolved:

    blk-crypto: make blk_crypto_evict_key() more robust (CVE-2023-53536)

    In the Linux kernel, the following vulnerability has been resolved:

    drm/i915: Make intel_get_crtc_new_encoder() less oopsy (CVE-2023-53571)

    In the Linux kernel, the following vulnerability has been resolved:

    scsi: target: Fix multiple LUN_RESET handling (CVE-2023-53586)

    In the Linux kernel, the following vulnerability has been resolved:

    ring-buffer: Sync IRQ works before buffer destruction (CVE-2023-53587)

    In the Linux kernel, the following vulnerability has been resolved:

    dm integrity: call kmem_cache_destroy() in dm_integrity_init() error path (CVE-2023-53604)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: sch_fq: fix integer overflow of credit (CVE-2023-53624)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: conntrack: fix wrong ct->timeout value (CVE-2023-53635)

    In the Linux kernel, the following vulnerability has been resolved:

    x86: fix clear_user_rep_good() exception handling annotation (CVE-2023-53642)

    In the Linux kernel, the following vulnerability has been resolved:

    rcu: Avoid stack overflow due to __rcu_irq_enter_check_tick() being kprobe-ed (CVE-2023-53655)

    In the Linux kernel, the following vulnerability has been resolved:

    tcp: fix skb_copy_ubufs() vs BIG TCP (CVE-2023-53669)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: fix use-after-free read in ext4_find_extent for bigalloc + inline (CVE-2023-53692)

    In the Linux kernel, the following vulnerability has been resolved:

    x86: fix clear_user_rep_good() exception handling annotation (CVE-2023-53749)

    In the Linux kernel, the following vulnerability has been resolved:

    cifs: fix potential use-after-free bugs in TCP_Server_Info::hostname (CVE-2023-53751)

    In the Linux kernel, the following vulnerability has been resolved:

    virt/coco/sev-guest: Double-buffer messages (CVE-2023-53769)

    In the Linux kernel, the following vulnerability has been resolved:

    dm flakey: fix a crash with invalid table line (CVE-2023-53786)

    In the Linux kernel, the following vulnerability has been resolved:

    ethtool: Fix uninitialized number of lanes (CVE-2023-53798)

    In the Linux kernel, the following vulnerability has been resolved:

    blk-mq: release crypto keyslot before reporting I/O complete (CVE-2023-53810)

    In the Linux kernel, the following vulnerability has been resolved:

    md/raid10: fix null-ptr-deref in raid10_sync_request (CVE-2023-53832)

    In the Linux kernel, the following vulnerability has been resolved:

    ceph: fix potential use-after-free bug when trimming caps (CVE-2023-53867)

    In the Linux kernel, the following vulnerability has been resolved:

    fs/ntfs3: Fix slab-out-of-bounds read in hdr_delete_de() (CVE-2023-53988)

    In the Linux kernel, the following vulnerability has been resolved:

    SMB3: Add missing locks to protect deferred close file list (CVE-2023-53990)

    In the Linux kernel, the following vulnerability has been resolved:

    btrfs: fix assertion of exclop condition when starting balance (CVE-2023-54002)

    In the Linux kernel, the following vulnerability has been resolved:

    vmci_host: fix a race condition in vmci_host_poll() causing GPF (CVE-2023-54007)

    In the Linux kernel, the following vulnerability has been resolved:

    spmi: Add a check for remove callback when removing a SPMI driver (CVE-2023-54044)

    In the Linux kernel, the following vulnerability has been resolved:

    kheaders: Use array declaration instead of char (CVE-2023-54056)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: fix invalid free tracking in ext4_xattr_move_to_block() (CVE-2023-54062)

    In the Linux kernel, the following vulnerability has been resolved:

    fs/ntfs3: Fix OOB read in indx_insert_into_buffer (CVE-2023-54063)

    In the Linux kernel, the following vulnerability has been resolved:

    tpm: Add !tpm_amd_is_rng_defective() to the hwrng_unregister() call site (CVE-2023-54073)

    In the Linux kernel, the following vulnerability has been resolved:

    fs/ntfs3: Fix memory leak if ntfs_read_mft failed (CVE-2023-54077)

    In the Linux kernel, the following vulnerability has been resolved:

    inotify: Avoid reporting event with invalid wd (CVE-2023-54119)

    In the Linux kernel, the following vulnerability has been resolved:

    md/raid10: fix memleak for 'conf->bio_split' (CVE-2023-54123)

    In the Linux kernel, the following vulnerability has been resolved:

    btrfs: don't free qgroup space unless specified (CVE-2023-54158)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: cls_api: remove block_cb from driver_list before freeing (CVE-2023-54193)

    In the Linux kernel, the following vulnerability has been resolved:

    fs/ntfs3: Add check for kmemdup (CVE-2023-54248)

    In the Linux kernel, the following vulnerability has been resolved:

    md/raid10: fix memleak of md thread (CVE-2023-54294)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: fix deadlock when converting an inline directory in nojournal mode (CVE-2023-54311)

    A use-after-free flaw was found in the __ext4_remount in fs/ext4/super.c in ext4 in the Linux kernel. This     flaw allows a local user to cause an information leak problem while freeing the old quota file names     before a potential failure, leading to a use-after-free. (CVE-2024-0775)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
270247	Linux Distros Unpatched Vulnerability : CVE-2023-53642	Nessus	Misc.	Local	medium
176925	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2023-184)	Nessus	Amazon Linux Local Security Checks	Local	high

Detections

Analytics

CVE-2023-53642

medium

Tenable Plugins

medium

high