In the Linux kernel, the following vulnerability has been resolved: nfsd: don't replace page in rq_pages if it's a continuation of last page The splice read calls nfsd_splice_actor to put the pages containing file data into the svc_rqst->rq_pages array. It's possible however to get a splice result that only has a partial page at the end, if (e.g.) the filesystem hands back a short read that doesn't cover the whole page. nfsd_splice_actor will plop the partial page into its rq_pages array and return. Then later, when nfsd_splice_actor is called again, the remainder of the page may end up being filled out. At this point, nfsd_splice_actor will put the page into the array _again_ corrupting the reply. If this is done enough times, rq_next_page will overrun the array and corrupt the trailing fields -- the rq_respages and rq_next_page pointers themselves. If we've already added the page to the array in the last pass, don't add it to the array a second time when dealing with a splice continuation. This was originally handled properly in nfsd_splice_actor, but commit 91e23b1c3982 ("NFSD: Clean up nfsd_splice_actor()") removed the check for it.

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

  - In the Linux kernel, the following vulnerability has been resolved: nfsd: don't replace page in rq_pages     if it's a continuation of last page The splice read calls nfsd_splice_actor to put the pages containing     file data into the svc_rqst->rq_pages array. It's possible however to get a splice result that only has a     partial page at the end, if (e.g.) the filesystem hands back a short read that doesn't cover the whole     page. nfsd_splice_actor will plop the partial page into its rq_pages array and return. Then later, when     nfsd_splice_actor is called again, the remainder of the page may end up being filled out. At this point,     nfsd_splice_actor will put the page into the array _again_ corrupting the reply. If this is done enough     times, rq_next_page will overrun the array and corrupt the trailing fields -- the rq_respages and     rq_next_page pointers themselves. If we've already added the page to the array in the last pass, don't add     it to the array a second time when dealing with a splice continuation. This was originally handled     properly in nfsd_splice_actor, but commit 91e23b1c3982 (NFSD: Clean up nfsd_splice_actor()) removed the     check for it. (CVE-2023-53083)

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-2025-1054 advisory.

    A flaw was found in the Linux kernel Traffic Control (TC) subsystem. Using a specific networking     configuration (redirecting egress packets to ingress using TC action mirred) a local unprivileged user     could trigger a CPU soft lockup (ABBA deadlock) when the transport protocol in use (TCP or SCTP) does a     retransmission, resulting in a denial of service condition. (CVE-2022-4269)

    A NULL pointer dereference has been discovered in the Linux Kernel, in io_file_bitmap_get in     io_uring/filetable.c. (CVE-2023-1583)

    A use-after-free flaw was found in btrfs_search_slot in fs/btrfs/ctree.c in btrfs in the Linux Kernel.This     flaw allows an attacker to crash the system and possibly cause a kernel information lea (CVE-2023-1611)

    An out-of-bounds write vulnerability was found in the Linux kernel's SLIMpro I2C device driver. The     userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a     memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to     crash the system or potentially achieve code execution. (CVE-2023-2194)

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

    dm stats: check for and propagate alloc_percpu failure (CVE-2023-53044)

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

    dm crypt: add cond_resched() to dmcrypt_write() (CVE-2023-53051)

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

    erspan: do not use skb_mac_header() in ndo_start_xmit() (CVE-2023-53053)

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

    fscrypt: destroy keyring after security_sb_delete() (CVE-2023-53055)

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

    igb: revert rtnl_lock() that causes deadlock (CVE-2023-53060)

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

    perf/core: Fix perf_output_begin parameter is incorrectly invoked in perf_event_bpf_output     (CVE-2023-53065)

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

    mptcp: use the workqueue to destroy unaccepted sockets (CVE-2023-53072)

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

    perf/x86/amd/core: Always clear status for idx (CVE-2023-53073)

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

    xsk: Add missing overflow check in xdp_umem_reg (CVE-2023-53080)

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

    nfsd: don't replace page in rq_pages if it's a continuation of last page (CVE-2023-53083)

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

    mptcp: fix UaF in listener shutdown (CVE-2023-53088)

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

    tracing: Do not let histogram values have some modifiers (CVE-2023-53093)

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.

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:2458 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * use-after-free in l2cap_connect and l2cap_le_connect_req in net/bluetooth/l2cap_core.c (CVE-2022-42896)

    * net/ulp: use-after-free in listening ULP sockets (CVE-2023-0461)

    * cpu: AMD CPUs may transiently execute beyond unconditional direct branch (CVE-2021-26341)

    * malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory (CVE-2021-33655)

    * possible race condition in drivers/tty/tty_buffers.c (CVE-2022-1462)

    * KVM: NULL pointer dereference in kvm_mmu_invpcid_gva (CVE-2022-1789)

    * use-after-free in free_pipe_info() could lead to privilege escalation (CVE-2022-1882)

    * KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks (CVE-2022-2196)

    * netfilter: nf_conntrack_irc message handling issue (CVE-2022-2663)

    * race condition in xfrm_probe_algs can lead to OOB read/write (CVE-2022-3028)

    * out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c (CVE-2022-3435)

    * race condition in hugetlb_no_page() in mm/hugetlb.c (CVE-2022-3522)

    * memory leak in ipv6_renew_options() (CVE-2022-3524)

    * data races around icsk->icsk_af_ops in do_ipv6_setsockopt (CVE-2022-3566)

    * data races around sk->sk_prot (CVE-2022-3567)

    * memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c (CVE-2022-3619)

    * denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry (CVE-2022-3623)

    * use-after-free after failed devlink reload in devlink_param_get (CVE-2022-3625)

    * USB-accessible buffer overflow in brcmfmac (CVE-2022-3628)

    * use after free flaw in l2cap_conn_del in net/bluetooth/l2cap_core.c (CVE-2022-3640)

    * Double-free in split_2MB_gtt_entry when function intel_gvt_dma_map_guest_page failed (CVE-2022-3707)

    * mptcp: NULL pointer dereference in subflow traversal at disconnect time (CVE-2022-4128)

    * l2tp: missing lock when clearing sk_user_data can lead to NULL pointer dereference (CVE-2022-4129)

    * igmp: use-after-free in ip_check_mc_rcu when opening and closing inet sockets (CVE-2022-20141)

    * lockdown bypass using IMA (CVE-2022-21505)

    * double free in usb_8dev_start_xmit in drivers/net/can/usb/usb_8dev.c (CVE-2022-28388)

    * network backend may cause Linux netfront to use freed SKBs (XSA-405) (CVE-2022-33743)

    * unmap_mapping_range() race with munmap() on VM_PFNMAP mappings leads to stale TLB entry (CVE-2022-39188)

    * TLB flush operations are mishandled in certain KVM_VCPU_PREEMPTED leading to guest malfunctioning     (CVE-2022-39189)

    * u8 overflow problem in cfg80211_update_notlisted_nontrans() (CVE-2022-41674)

    * use-after-free related to leaf anon_vma double reuse (CVE-2022-42703)

    * use-after-free in bss_ref_get in net/wireless/scan.c (CVE-2022-42720)

    * BSS list corruption in cfg80211_add_nontrans_list in net/wireless/scan.c (CVE-2022-42721)

    * Denial of service in beacon protection for P2P-device (CVE-2022-42722)

    * memory corruption in usbmon driver (CVE-2022-43750)

    * NULL pointer dereference in traffic control subsystem (CVE-2022-47929)

    * NULL pointer dereference in rawv6_push_pending_frames (CVE-2023-0394)

    * use-after-free due to race condition in qdisc_graft() (CVE-2023-0590)

    * use-after-free caused by invalid pointer hostname in fs/cifs/connect.c (CVE-2023-1195)

    * denial of service in tipc_conn_close (CVE-2023-1382)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 9.2 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

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

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

    A flaw was found in the Linux kernel Traffic Control (TC) subsystem. Using a specific networking     configuration (redirecting egress packets to ingress using TC action mirred) a local unprivileged user     could trigger a CPU soft lockup (ABBA deadlock) when the transport protocol in use (TCP or SCTP) does a     retransmission, resulting in a denial of service condition. (CVE-2022-4269)

    A NULL pointer dereference has been discovered in the Linux Kernel, in io_file_bitmap_get in     io_uring/filetable.c. (CVE-2023-1583)

    A use-after-free flaw was found in btrfs_search_slot in fs/btrfs/ctree.c in btrfs in the Linux Kernel.This     flaw allows an attacker to crash the system and possibly cause a kernel information lea (CVE-2023-1611)

    An out-of-bounds write vulnerability was found in the Linux kernel's SLIMpro I2C device driver. The     userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a     memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to     crash the system or potentially achieve code execution. (CVE-2023-2194)

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

    dm crypt: add cond_resched() to dmcrypt_write() (CVE-2023-53051)

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

    erspan: do not use skb_mac_header() in ndo_start_xmit() (CVE-2023-53053)

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

    perf/x86/amd/core: Always clear status for idx (CVE-2023-53073)

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

    xsk: Add missing overflow check in xdp_umem_reg (CVE-2023-53080)

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

    nfsd: don't replace page in rq_pages if it's a continuation of last page (CVE-2023-53083)

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

    tracing: Do not let histogram values have some modifiers (CVE-2023-53093)

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	Severity
249456	Linux Distros Unpatched Vulnerability : CVE-2023-53083	Nessus	Misc.	medium
241778	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2025-1054)	Nessus	Amazon Linux Local Security Checks	medium
175477	RHEL 9 : kernel (RHSA-2023:2458)	Nessus	Red Hat Local Security Checks	high
174575	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2023-160)	Nessus	Amazon Linux Local Security Checks	medium

Detections

Analytics

CVE-2023-53083

medium

Tenable Plugins

medium

medium

high

medium