<?xml version="1.0" encoding="utf-8"?>
  <?xml-stylesheet type="text/xsl" href="sa-render.xsl"?>
  <update from="huaweicloud.com" type="security" status="stable" version="1">
    <id>HCE2-SA-2023-0127</id>
    <title>An update for kernel is now available for HCE 2.0</title>
    <severity>Important</severity>
    <release>HCE 2.0</release>
    <issued date="2023-03-27 08:19:26"/>
    <updated date="2023-03-27 08:19:26"/>
    <references>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2022-2196" id="CVE-2022-2196" title="CVE-2022-2196 Base Score: 8.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-26545" id="CVE-2023-26545" title="CVE-2023-26545 Base Score: 7.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-1075" id="CVE-2023-1075" title="CVE-2023-1075 Base Score: 2.5 Vector: CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2022-47929" id="CVE-2022-47929" title="CVE-2022-47929 Base Score: 5.5 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2022-47946" id="CVE-2022-47946" title="CVE-2022-47946 Base Score: 5.5 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-0394" id="CVE-2023-0394" title="CVE-2023-0394 Base Score: 5.5 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2022-4842" id="CVE-2022-4842" title="CVE-2022-4842 Base Score: 5.5 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-0045" id="CVE-2023-0045" title="CVE-2023-0045 Base Score: 6.3 Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-1076" id="CVE-2023-1076" title="CVE-2023-1076 Base Score: 4.7 Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-0597" id="CVE-2023-0597" title="CVE-2023-0597 Base Score: 5.5 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2022-3424" id="CVE-2022-3424" title="CVE-2022-3424 Base Score: 7.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-22995" id="CVE-2023-22995" title="CVE-2023-22995 Base Score: 7.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-23455" id="CVE-2023-23455" title="CVE-2023-23455 Base Score: 5.5 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-0461" id="CVE-2023-0461" title="CVE-2023-0461 Base Score: 7.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2022-4696" id="CVE-2022-4696" title="CVE-2022-4696 Base Score: 7.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-1073" id="CVE-2023-1073" title="CVE-2023-1073 Base Score: 6.3 Vector: CVSS:3.1/AV:P/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-23454" id="CVE-2023-23454" title="CVE-2023-23454 Base Score: 5.5 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-0590" id="CVE-2023-0590" title="CVE-2023-0590 Base Score: 7.0 Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-1074" id="CVE-2023-1074" title="CVE-2023-1074 Base Score: 4.7 Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-20928" id="CVE-2023-20928" title="CVE-2023-20928 Base Score: 7.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2022-4269" id="CVE-2022-4269" title="CVE-2022-4269 Base Score: 5.5 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2022-27672" id="CVE-2022-27672" title="CVE-2022-27672 Base Score: 4.7 Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2022-3707" id="CVE-2022-3707" title="CVE-2022-3707 Base Score: 5.5 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-0179" id="CVE-2023-0179" title="CVE-2023-0179 Base Score: 7.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2023-1118" id="CVE-2023-1118" title="CVE-2023-1118 Base Score: 7.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2022-41218" id="CVE-2022-41218" title="CVE-2022-41218 Base Score: 5.5 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2022-4662" id="CVE-2022-4662" title="CVE-2022-4662 Base Score: 5.5 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
    </references>
    <description>Security Fix(es):

A regression exists in the Linux Kernel within KVM: nVMX that allowed for speculative execution attacks. L2 can carry out Spectre v2 attacks on L1 due to L1 thinking it doesn't need retpolines or IBPB after running L2 due to KVM (L0) advertising eIBRS support to L1. An attacker at L2 with code execution can execute code on an indirect branch on the host machine. We recommend upgrading to Kernel 6.2 or past commit 2e7eab81425a (CVE-2022-2196)

In the Linux kernel before 6.1.13, there is a double free in net/mpls/af_mpls.c upon an allocation failure (for registering the sysctl table under a new location) during the renaming of a device. (CVE-2023-26545)

A flaw in the Linux Kernel found. The tls_is_tx_ready() incorrectly checks for list emptiness, potentially accessing a type confused entry to the list_head, leaking the last byte of the confused field that overlaps with rec-&gt;tx_ready.Reference:https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=ffe2a22562444720b05bdfeb999c03e810d84cbb (CVE-2023-1075)

In the Linux kernel before 6.1.6, a NULL pointer dereference bug in the traffic control subsystem allows an unprivileged user to trigger a denial of service (system crash) via a crafted traffic control configuration that is set up with &quot;tc qdisc&quot; and &quot;tc class&quot; commands. This affects qdisc_graft in net/sched/sch_api.c. (CVE-2022-47929)

An issue was discovered in the Linux kernel 5.10.x before 5.10.155. A use-after-free in io_sqpoll_wait_sq in fs/io_uring.c allows an attacker to crash the kernel, resulting in denial of service. finish_wait can be skipped. An attack can occur in some situations by forking a process and then quickly terminating it. NOTE: later kernel versions, such as the 5.15 longterm series, substantially changed the implementation of io_sqpoll_wait_sq. (CVE-2022-47946)

A NULL pointer dereference flaw was found in rawv6_push_pending_frames in net/ipv6/raw.c in the network subcomponent in the Linux kernel. This flaw causes the system to crash. (CVE-2023-0394)

A flaw NULL Pointer Dereference in the Linux kernel NTFS3 driver function attr_punch_hole() was found. A local user could use this flaw to crash the system. (CVE-2022-4842)

The Linux kernel does not correctly mitigate SMT attacks, as discovered through a strange pattern in the kernel API using STIBP as a mitigation, leaving the process exposed for a short period of time after a syscall. The kernel also does not issue an IBPB immediately during the syscall. (CVE-2023-0045)

A flaw found in the Linux Kernel. The tun/tap sockets have their socket UID hardcoded to 0 due to a type confusion in their initialization function. While it will be often correct, as tuntap devices require CAP_NET_ADMIN, it may not always be the case, e.g., a non-root user only having that capability. This would make tun/tap sockets being incorrectly treated in filtering/routing decisions, possibly bypassing network filters. (CVE-2023-1076)

A flaw possibility of memory leak in the Linux kernel cpu_entry_area mapping of X86 CPU data to memory was found in the way user can guess location of exception stack(s) or other important data. A local user could use this flaw to get access to some important data with expected location in memory. (CVE-2023-0597)

A use-after-free flaw was found in the Linux kernel’s SGI GRU driver in the way the first gru_file_unlocked_ioctl function is called by the user, where a fail pass occurs in the gru_check_chiplet_assignment function. This flaw allows a local user to crash or potentially escalate their privileges on the system. (CVE-2022-3424)

In the Linux kernel before 5.17, an error path in dwc3_qcom_acpi_register_core in drivers/usb/dwc3/dwc3-qcom.c lacks certain platform_device_put and kfree calls. (CVE-2023-22995)

atm_tc_enqueue in net/sched/sch_atm.c in the Linux kernel through 6.1.4 allows attackers to cause a denial of service because of type confusion (non-negative numbers can sometimes indicate a TC_ACT_SHOT condition rather than valid classification results). (CVE-2023-23455)

There is a use-after-free vulnerability in the Linux Kernel which can be exploited to achieve local privilege escalation. To reach the vulnerability kernel configuration flag CONFIG_TLS or CONFIG_XFRM_ESPINTCP has to be configured, but the operation does not require any privilege. There is a use-after-free bug of icsk_ulp_data of a struct inet_connection_sock. When CONFIG_TLS is enabled, user can install a tls context (struct tls_context) on a connected tcp socket. The context is not cleared if this socket is disconnected and reused as a listener. If a new socket is created from the listener, the context is inherited and vulnerable. The setsockopt TCP_ULP operation does not require any privilege. We recommend upgrading past commit 2c02d41d71f90a5168391b6a5f2954112ba2307c (CVE-2023-0461)

There exists a use-after-free vulnerability in the Linux kernel through io_uring and the IORING_OP_SPLICE operation. If IORING_OP_SPLICE is missing the IO_WQ_WORK_FILES flag, which signals that the operation won't use current-&gt;nsproxy, so its reference counter is not increased. This assumption is not always true as calling io_splice on specific files will call the get_uts function which will use current-&gt;nsproxy leading to invalidly decreasing its reference counter later causing the use-after-free vulnerability. We recommend upgrading to version 5.10.160 or above (CVE-2022-4696)

A memory corruption flaw was found in the Linux kernel’s human interface device (HID) subsystem in how a user inserts a malicious USB device. This flaw allows a local user to crash or potentially escalate their privileges on the system. (CVE-2023-1073)

cbq_classify in net/sched/sch_cbq.c in the Linux kernel through 6.1.4 allows attackers to cause a denial of service (slab-out-of-bounds read) because of type confusion (non-negative numbers can sometimes indicate a TC_ACT_SHOT condition rather than valid classification results). (CVE-2023-23454)

A use-after-free flaw was found in qdisc_graft in net/sched/sch_api.c in the Linux Kernel due to a race problem. This flaw leads to a denial of service issue. If patch ebda44da44f6 (&quot;net: sched: fix race condition in qdisc_graft()&quot;) not applied yet, then kernel could be affected. (CVE-2023-0590)

A memory leak flaw was found in the Linux kernel’s Stream Control Transmission Protocol. This issue may occur when a user starts a malicious networking service and someone connects to this service. This could allow a local user to starve resources, causing a denial of service. (CVE-2023-1074)

In binder_vma_close of binder.c, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-254837884References: Upstream kernel (CVE-2023-20928)

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 &quot;mirred&quot;) 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)

When SMT is enabled, certain AMD processors may speculatively execute instructions using a target from the sibling thread after an SMT mode switch potentially resulting in information disclosure. (CVE-2022-27672)

A double-free memory flaw was found in the Linux kernel. The Intel GVT-g graphics driver triggers VGA card system resource overload, causing a fail in the intel_gvt_dma_map_guest_page function. This issue could allow a local user to crash the system. (CVE-2022-3707)

A buffer overflow vulnerability was found in the Netfilter subsystem in the Linux Kernel. This issue could allow the leakage of both stack and heap addresses, and potentially allow Local Privilege Escalation to the root user via arbitrary code execution. (CVE-2023-0179)

A flaw use after free in the Linux kernel integrated infrared receiver/transceiver driver was found in the way user detaching rc device. A local user could use this flaw to crash the system or potentially escalate their privileges on the system. (CVE-2023-1118)

In drivers/media/dvb-core/dmxdev.c in the Linux kernel through 5.19.10, there is a use-after-free caused by refcount races, affecting dvb_demux_open and dvb_dmxdev_release. (CVE-2022-41218)

A flaw incorrect access control in the Linux kernel USB core subsystem was found in the way user attaches usb device. A local user could use this flaw to crash the system. (CVE-2022-4662)
</description>
    <pkglist>
      <collection short="HCE 2.0" package="kernel">
        <name>HCE 2.0</name>
        <package arch="aarch64" name="bpftool" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>bpftool-5.10.0-60.18.0.50.r865_35.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="kernel" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>kernel-5.10.0-60.18.0.50.r865_35.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="kernel-abi-stablelists" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>kernel-abi-stablelists-5.10.0-60.18.0.50.r865_35.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="kernel-tools" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>kernel-tools-5.10.0-60.18.0.50.r865_35.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="kernel-tools-libs" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>kernel-tools-libs-5.10.0-60.18.0.50.r865_35.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="kernel-tools-libs-devel" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>kernel-tools-libs-devel-5.10.0-60.18.0.50.r865_35.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="perf" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>perf-5.10.0-60.18.0.50.r865_35.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="python3-perf" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>python3-perf-5.10.0-60.18.0.50.r865_35.hce2.aarch64.rpm</filename>
        </package>
        <package arch="x86_64" name="bpftool" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>bpftool-5.10.0-60.18.0.50.r865_35.hce2.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="kernel" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>kernel-5.10.0-60.18.0.50.r865_35.hce2.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="kernel-abi-stablelists" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>kernel-abi-stablelists-5.10.0-60.18.0.50.r865_35.hce2.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="kernel-tools" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>kernel-tools-5.10.0-60.18.0.50.r865_35.hce2.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="kernel-tools-libs" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>kernel-tools-libs-5.10.0-60.18.0.50.r865_35.hce2.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="kernel-tools-libs-devel" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>kernel-tools-libs-devel-5.10.0-60.18.0.50.r865_35.hce2.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="perf" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>perf-5.10.0-60.18.0.50.r865_35.hce2.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="python3-perf" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>python3-perf-5.10.0-60.18.0.50.r865_35.hce2.x86_64.rpm</filename>
        </package>
        <package arch="aarch64" name="kernel-devel" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>kernel-devel-5.10.0-60.18.0.50.r865_35.hce2.aarch64.rpm</filename>
        </package>
        <package arch="x86_64" name="kernel-devel" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>kernel-devel-5.10.0-60.18.0.50.r865_35.hce2.x86_64.rpm</filename>
        </package>
        <package arch="aarch64" name="kernel-headers" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>kernel-headers-5.10.0-60.18.0.50.r865_35.hce2.aarch64.rpm</filename>
        </package>
        <package arch="x86_64" name="kernel-headers" version="5.10.0" release="60.18.0.50.r865_35.hce2">
          <filename>kernel-headers-5.10.0-60.18.0.50.r865_35.hce2.x86_64.rpm</filename>
        </package>
      </collection>
    </pkglist>
  </update>
