An update for kernel is now available for openEuler-20.03-LTS and openEuler-20.03-LTS-SP1 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2021-1111 Final 1.0 1.0 2021-04-07 Initial 2021-04-07 2021-04-07 openEuler SA Tool V1.0 2021-04-07 kernel security update An update for kernel is now available for openEuler-20.03-LTS and openEuler-20.03-LTS-SP1. The kernel package contains the Linux kernel (vmlinuz), the core of any Linux operating system. The kernel handles the basic functions of the operating system: memory allocation, process allocation, device input and output, etc. Security Fix(es): An issue was discovered in the Linux kernel 2.6.39 through 5.10.16, as used in Xen. Block, net, and SCSI backends consider certain errors a plain bug, deliberately causing a kernel crash. For errors potentially being at least under the influence of guests (such as out of memory conditions), it isn't correct to assume a plain bug. Memory allocations potentially causing such crashes occur only when Linux is running in PV mode, though. This affects drivers/block/xen-blkback/blkback.c and drivers/xen/xen-scsiback.c.(CVE-2021-26931) An issue was discovered in the Linux kernel 3.11 through 5.10.16, as used by Xen. To service requests to the PV backend, the driver maps grant references provided by the frontend. In this process, errors may be encountered. In one case, an error encountered earlier might be discarded by later processing, resulting in the caller assuming successful mapping, and hence subsequent operations trying to access space that wasn't mapped. In another case, internal state would be insufficiently updated, preventing safe recovery from the error. This affects drivers/block/xen-blkback/blkback.c.(CVE-2021-26930) An issue was discovered in the Linux kernel 3.2 through 5.10.16, as used by Xen. Grant mapping operations often occur in batch hypercalls, where a number of operations are done in a single hypercall, the success or failure of each one is reported to the backend driver, and the backend driver then loops over the results, performing follow-up actions based on the success or failure of each operation. Unfortunately, when running in PV mode, the Linux backend drivers mishandle this: Some errors are ignored, effectively implying their success from the success of related batch elements. In other cases, errors resulting from one batch element lead to further batch elements not being inspected, and hence successful ones to not be possible to properly unmap upon error recovery. Only systems with Linux backends running in PV mode are vulnerable. Linux backends run in HVM / PVH modes are not vulnerable. This affects arch/*/xen/p2m.c and drivers/xen/gntdev.c.(CVE-2021-26932) An issue was discovered in the Linux kernel through 5.11.3, as used with Xen PV. A certain part of the netback driver lacks necessary treatment of errors such as failed memory allocations (as a result of changes to the handling of grant mapping errors). A host OS denial of service may occur during misbehavior of a networking frontend driver. NOTE: this issue exists because of an incomplete fix for CVE-2021-26931.(CVE-2021-28038) An issue was discovered in the Linux kernel through 5.11.3. A kernel pointer leak can be used to determine the address of the iscsi_transport structure. When an iSCSI transport is registered with the iSCSI subsystem, the transport's handle is available to unprivileged users via the sysfs file system, at /sys/class/iscsi_transport/$TRANSPORT_NAME/handle. When read, the show_transport_handle function (in drivers/scsi/scsi_transport_iscsi.c) is called, which leaks the handle. This handle is actually the pointer to an iscsi_transport struct in the kernel module's global variables.(CVE-2021-27363) An issue was discovered in the Linux kernel through 5.11.3. drivers/scsi/scsi_transport_iscsi.c is adversely affected by the ability of an unprivileged user to craft Netlink messages.(CVE-2021-27364) An issue was discovered in the Linux kernel through 5.11.3. Certain iSCSI data structures do not have appropriate length constraints or checks, and can exceed the PAGE_SIZE value. An unprivileged user can send a Netlink message that is associated with iSCSI, and has a length up to the maximum length of a Netlink message.(CVE-2021-27365) An update for kernel is now available for openEuler-20.03-LTS and openEuler-20.03-LTS-SP1. openEuler Security has rated this update as having a security impact of high. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section. High kernel https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1111 https://openeuler.org/en/security/cve/detail.html?id=CVE-2021-26931 https://openeuler.org/en/security/cve/detail.html?id=CVE-2021-26930 https://openeuler.org/en/security/cve/detail.html?id=CVE-2021-26932 https://openeuler.org/en/security/cve/detail.html?id=CVE-2021-28038 https://openeuler.org/en/security/cve/detail.html?id=CVE-2021-27363 https://openeuler.org/en/security/cve/detail.html?id=CVE-2021-27364 https://openeuler.org/en/security/cve/detail.html?id=CVE-2021-27365 https://nvd.nist.gov/vuln/detail/CVE-2021-26931 https://nvd.nist.gov/vuln/detail/CVE-2021-26930 https://nvd.nist.gov/vuln/detail/CVE-2021-26932 https://nvd.nist.gov/vuln/detail/CVE-2021-28038 https://nvd.nist.gov/vuln/detail/CVE-2021-27363 https://nvd.nist.gov/vuln/detail/CVE-2021-27364 https://nvd.nist.gov/vuln/detail/CVE-2021-27365 openEuler-20.03-LTS openEuler-20.03-LTS-SP1 bpftool-debuginfo-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-debuginfo-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-devel-4.19.90-2103.3.0.0061.oe1.aarch64.rpm python3-perf-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-tools-debuginfo-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-tools-devel-4.19.90-2103.3.0.0061.oe1.aarch64.rpm bpftool-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-source-4.19.90-2103.3.0.0061.oe1.aarch64.rpm python2-perf-4.19.90-2103.3.0.0061.oe1.aarch64.rpm python3-perf-debuginfo-4.19.90-2103.3.0.0061.oe1.aarch64.rpm python2-perf-debuginfo-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-debugsource-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-4.19.90-2103.3.0.0061.oe1.aarch64.rpm perf-debuginfo-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-tools-4.19.90-2103.3.0.0061.oe1.aarch64.rpm perf-4.19.90-2103.3.0.0061.oe1.aarch64.rpm bpftool-debuginfo-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-debugsource-4.19.90-2103.3.0.0061.oe1.aarch64.rpm python2-perf-debuginfo-4.19.90-2103.3.0.0061.oe1.aarch64.rpm python3-perf-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-source-4.19.90-2103.3.0.0061.oe1.aarch64.rpm python2-perf-4.19.90-2103.3.0.0061.oe1.aarch64.rpm python3-perf-debuginfo-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-debuginfo-4.19.90-2103.3.0.0061.oe1.aarch64.rpm perf-debuginfo-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-tools-devel-4.19.90-2103.3.0.0061.oe1.aarch64.rpm bpftool-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-devel-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-tools-4.19.90-2103.3.0.0061.oe1.aarch64.rpm perf-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-tools-debuginfo-4.19.90-2103.3.0.0061.oe1.aarch64.rpm kernel-4.19.90-2103.3.0.0061.oe1.src.rpm kernel-4.19.90-2103.3.0.0061.oe1.src.rpm python3-perf-4.19.90-2103.3.0.0061.oe1.x86_64.rpm bpftool-4.19.90-2103.3.0.0061.oe1.x86_64.rpm perf-debuginfo-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-tools-4.19.90-2103.3.0.0061.oe1.x86_64.rpm python3-perf-debuginfo-4.19.90-2103.3.0.0061.oe1.x86_64.rpm python2-perf-debuginfo-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-debuginfo-4.19.90-2103.3.0.0061.oe1.x86_64.rpm perf-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-tools-devel-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-source-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-devel-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-debugsource-4.19.90-2103.3.0.0061.oe1.x86_64.rpm python2-perf-4.19.90-2103.3.0.0061.oe1.x86_64.rpm bpftool-debuginfo-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-tools-debuginfo-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-debugsource-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-tools-debuginfo-4.19.90-2103.3.0.0061.oe1.x86_64.rpm python2-perf-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-source-4.19.90-2103.3.0.0061.oe1.x86_64.rpm perf-debuginfo-4.19.90-2103.3.0.0061.oe1.x86_64.rpm python2-perf-debuginfo-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-debuginfo-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-tools-devel-4.19.90-2103.3.0.0061.oe1.x86_64.rpm bpftool-4.19.90-2103.3.0.0061.oe1.x86_64.rpm bpftool-debuginfo-4.19.90-2103.3.0.0061.oe1.x86_64.rpm perf-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-devel-4.19.90-2103.3.0.0061.oe1.x86_64.rpm kernel-tools-4.19.90-2103.3.0.0061.oe1.x86_64.rpm python3-perf-debuginfo-4.19.90-2103.3.0.0061.oe1.x86_64.rpm python3-perf-4.19.90-2103.3.0.0061.oe1.x86_64.rpm An issue was discovered in the Linux kernel 2.6.39 through 5.10.16, as used in Xen. Block, net, and SCSI backends consider certain errors a plain bug, deliberately causing a kernel crash. For errors potentially being at least under the influence of guests (such as out of memory conditions), it isn't correct to assume a plain bug. Memory allocations potentially causing such crashes occur only when Linux is running in PV mode, though. This affects drivers/block/xen-blkback/blkback.c and drivers/xen/xen-scsiback.c. 2021-04-07 CVE-2021-26931 openEuler-20.03-LTS openEuler-20.03-LTS-SP1 Medium 5.5 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H kernel security update 2021-04-07 https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1111 An issue was discovered in the Linux kernel 3.11 through 5.10.16, as used by Xen. To service requests to the PV backend, the driver maps grant references provided by the frontend. In this process, errors may be encountered. In one case, an error encountered earlier might be discarded by later processing, resulting in the caller assuming successful mapping, and hence subsequent operations trying to access space that wasn't mapped. In another case, internal state would be insufficiently updated, preventing safe recovery from the error. This affects drivers/block/xen-blkback/blkback.c. 2021-04-07 CVE-2021-26930 openEuler-20.03-LTS openEuler-20.03-LTS-SP1 High 7.8 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H kernel security update 2021-04-07 https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1111 An issue was discovered in the Linux kernel 3.2 through 5.10.16, as used by Xen. Grant mapping operations often occur in batch hypercalls, where a number of operations are done in a single hypercall, the success or failure of each one is reported to the backend driver, and the backend driver then loops over the results, performing follow-up actions based on the success or failure of each operation. Unfortunately, when running in PV mode, the Linux backend drivers mishandle this: Some errors are ignored, effectively implying their success from the success of related batch elements. In other cases, errors resulting from one batch element lead to further batch elements not being inspected, and hence successful ones to not be possible to properly unmap upon error recovery. Only systems with Linux backends running in PV mode are vulnerable. Linux backends run in HVM / PVH modes are not vulnerable. This affects arch/*/xen/p2m.c and drivers/xen/gntdev.c. 2021-04-07 CVE-2021-26932 openEuler-20.03-LTS openEuler-20.03-LTS-SP1 Medium 5.5 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H kernel security update 2021-04-07 https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1111 An issue was discovered in the Linux kernel through 5.11.3, as used with Xen PV. A certain part of the netback driver lacks necessary treatment of errors such as failed memory allocations (as a result of changes to the handling of grant mapping errors). A host OS denial of service may occur during misbehavior of a networking frontend driver. NOTE: this issue exists because of an incomplete fix for CVE-2021-26931. 2021-04-07 CVE-2021-28038 openEuler-20.03-LTS openEuler-20.03-LTS-SP1 Medium 6.5 AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H kernel security update 2021-04-07 https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1111 An issue was discovered in the Linux kernel through 5.11.3. A kernel pointer leak can be used to determine the address of the iscsi_transport structure. When an iSCSI transport is registered with the iSCSI subsystem, the transport's handle is available to unprivileged users via the sysfs file system, at /sys/class/iscsi_transport/$TRANSPORT_NAME/handle. When read, the show_transport_handle function (in drivers/scsi/scsi_transport_iscsi.c) is called, which leaks the handle. This handle is actually the pointer to an iscsi_transport struct in the kernel module's global variables. 2021-04-07 CVE-2021-27363 openEuler-20.03-LTS openEuler-20.03-LTS-SP1 Low 3.6 AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:L kernel security update 2021-04-07 https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1111 An issue was discovered in the Linux kernel through 5.11.3. drivers/scsi/scsi_transport_iscsi.c is adversely affected by the ability of an unprivileged user to craft Netlink messages. 2021-04-07 CVE-2021-27364 openEuler-20.03-LTS openEuler-20.03-LTS-SP1 Medium 6.3 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H kernel security update 2021-04-07 https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1111 An issue was discovered in the Linux kernel through 5.11.3. Certain iSCSI data structures do not have appropriate length constraints or checks, and can exceed the PAGE_SIZE value. An unprivileged user can send a Netlink message that is associated with iSCSI, and has a length up to the maximum length of a Netlink message. 2021-04-07 CVE-2021-27365 openEuler-20.03-LTS openEuler-20.03-LTS-SP1 High 7.0 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H kernel security update 2021-04-07 https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1111