An update for kernel is now available for openEuler-20.03-LTS-SP4 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2026-2929 Final 1.0 1.0 2026-07-09 Initial 2026-07-09 2026-07-09 openEuler SA Tool V1.0 2026-07-09 kernel security update An update for kernel is now available for openEuler-20.03-LTS-SP4 The Linux Kernel, the operating system core itself. Security Fix(es): In the Linux kernel, the following vulnerability has been resolved: ipc: limit next_id allocation to the valid ID range The checkpoint/restore sysctl path can request the next SysV IPC id through ids->next_id. ipc_idr_alloc() currently forwards that request to idr_alloc() with an open-ended upper bound. If the valid tail of the SysV IPC id space is full, the allocation can spill beyond ipc_mni. The returned SysV IPC id still uses the normal index encoding, so later lookup and removal can target the wrong slot. This leaves the real IDR entry behind and breaks the IDR state for the object. The bug is in ipc_idr_alloc() in the checkpoint/restore path. 1. ids->next_id is passed to: idr_alloc(&ids->ipcs_idr, new, ipcid_to_idx(next_id), 0, ...) 2. The zero upper bound makes the allocation effectively open-ended. Once the valid SysV IPC tail is occupied, idr_alloc() can spill past ipc_mni and allocate an entry beyond the valid IPC id range. 3. The new object id is still encoded with the narrower SysV IPC index width: new->id = (new->seq << ipcmni_seq_shift()) + idx 4. Later removal goes through ipc_rmid(), which uses: ipcid_to_idx(ipcp->id) That truncates the real IDR index. An object actually stored at a high index can then be removed as if it lived at a low in-range index. 5. For shared memory, shm_destroy() frees the current object anyway, but the real high IDR slot is left behind as a dangling pointer. 6. A subsequent walk of /proc/sysvipc/shm reaches the stale IDR entry and dereferences freed memory. Prevent this by bounding the requested allocation to ipc_mni so the checkpoint/restore path fails once the valid range is exhausted.(CVE-2026-52923) In the Linux kernel, the following vulnerability has been resolved: RDMA/umem: Fix truncation for block sizes >= 4G When the iommu is used the linearization of the mapping can give a single block that is very large split across multiple SG entries. When __rdma_block_iter_next() reassembles the split SG entries it is overflowing the 32 bit stack values and computed the wrong DMA addresses for blocks after the truncation. Use the right types to hold DMA addresses.(CVE-2026-53133) In the Linux kernel, the following vulnerability has been resolved: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN In drivers/infiniband/ulp/isert/ib_isert.c, isert_login_recv_done() computes the login request payload length as wc->byte_len minus ISER_HEADERS_LEN with no lower bound, and login_req_len is a signed int. A remote iSER initiator can post a login Send work request carrying fewer than ISER_HEADERS_LEN (76) bytes, so the subtraction underflows and login_req_len becomes negative. isert_rx_login_req() then reads that negative length back into a signed int, takes size = min(rx_buflen, MAX_KEY_VALUE_PAIRS), and because the min() is signed it keeps the negative value; the value is then passed as the memcpy() length and sign-extended to a multi-gigabyte size_t. The copy into the 8192-byte login->req_buf runs far out of bounds and faults, crashing the target node. The login phase precedes iSCSI authentication, so no credentials are required to reach this path. Reject any login PDU shorter than ISER_HEADERS_LEN before the subtraction, mirroring the existing early return on a failed work completion, so login_req_len can never go negative. The upper bound was already safe: a posted login buffer cannot deliver more than ISER_RX_PAYLOAD_SIZE, so the difference stays at or below MAX_KEY_VALUE_PAIRS and the existing min() clamps it; only the missing lower bound needs to be added.(CVE-2026-53176) In the Linux kernel, the following vulnerability has been resolved: USB: serial: kl5kusb105: fix bulk-out buffer overflow klsi_105_prepare_write_buffer() is called by the generic write path with the bulk-out buffer and its size (bulk_out_size, 64 bytes). It stores a two-byte length header at the start of the buffer and copies the payload from the write fifo starting at buf + KLSI_HDR_LEN, but passes the full buffer size as the number of bytes to copy: count = kfifo_out_locked(&port->write_fifo, buf + KLSI_HDR_LEN, size, &port->lock); When the fifo holds at least size bytes, size bytes are copied starting two bytes into the size-byte buffer, writing KLSI_HDR_LEN bytes past its end. Copy at most size - KLSI_HDR_LEN bytes instead, leaving room for the header as safe_serial already does. Writing bulk_out_size or more bytes to the tty triggers a slab out-of-bounds write, observed with KASAN by emulating the device with dummy_hcd and raw-gadget: BUG: KASAN: slab-out-of-bounds in kfifo_copy_out+0x83/0xc0 Write of size 64 at addr ffff888112c62202 by task python3 kfifo_copy_out klsi_105_prepare_write_buffer [kl5kusb105] usb_serial_generic_write_start [usbserial] Allocated by task 139: usb_serial_probe [usbserial] The buggy address is located 2 bytes inside of allocated 64-byte region The out-of-bounds write no longer occurs with this change applied.(CVE-2026-53194) An update for kernel is now available for openEuler-20.03-LTS-SP4/openEuler-22.03-LTS-SP4/openEuler-24.03-LTS-SP1/openEuler-24.03-LTS-SP3/openEuler-24.03-LTS-SP4/openEuler-22.03-LTS-SP3/openEuler-24.03-LTS/openEuler-24.03-LTS-SP2. 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://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2929 https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2026-52923 https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2026-53133 https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2026-53176 https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2026-53194 https://nvd.nist.gov/vuln/detail/CVE-2026-52923 https://nvd.nist.gov/vuln/detail/CVE-2026-53133 https://nvd.nist.gov/vuln/detail/CVE-2026-53176 https://nvd.nist.gov/vuln/detail/CVE-2026-53194 openEuler-20.03-LTS-SP4 bpftool-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm bpftool-debuginfo-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm kernel-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm kernel-debuginfo-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm kernel-debugsource-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm kernel-devel-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm kernel-source-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm kernel-tools-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm kernel-tools-debuginfo-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm kernel-tools-devel-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm perf-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm perf-debuginfo-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm python2-perf-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm python2-perf-debuginfo-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm python3-perf-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm python3-perf-debuginfo-4.19.90-2607.1.0.0379.oe2003sp4.aarch64.rpm bpftool-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm bpftool-debuginfo-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm kernel-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm kernel-debuginfo-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm kernel-debugsource-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm kernel-devel-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm kernel-source-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm kernel-tools-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm kernel-tools-debuginfo-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm kernel-tools-devel-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm perf-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm perf-debuginfo-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm python2-perf-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm python2-perf-debuginfo-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm python3-perf-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm python3-perf-debuginfo-4.19.90-2607.1.0.0379.oe2003sp4.x86_64.rpm kernel-4.19.90-2607.1.0.0379.oe2003sp4.src.rpm In the Linux kernel, the following vulnerability has been resolved: ipc: limit next_id allocation to the valid ID range The checkpoint/restore sysctl path can request the next SysV IPC id through ids->next_id. ipc_idr_alloc() currently forwards that request to idr_alloc() with an open-ended upper bound. If the valid tail of the SysV IPC id space is full, the allocation can spill beyond ipc_mni. The returned SysV IPC id still uses the normal index encoding, so later lookup and removal can target the wrong slot. This leaves the real IDR entry behind and breaks the IDR state for the object. The bug is in ipc_idr_alloc() in the checkpoint/restore path. 1. ids->next_id is passed to: idr_alloc(&ids->ipcs_idr, new, ipcid_to_idx(next_id), 0, ...) 2. The zero upper bound makes the allocation effectively open-ended. Once the valid SysV IPC tail is occupied, idr_alloc() can spill past ipc_mni and allocate an entry beyond the valid IPC id range. 3. The new object id is still encoded with the narrower SysV IPC index width: new->id = (new->seq << ipcmni_seq_shift()) + idx 4. Later removal goes through ipc_rmid(), which uses: ipcid_to_idx(ipcp->id) That truncates the real IDR index. An object actually stored at a high index can then be removed as if it lived at a low in-range index. 5. For shared memory, shm_destroy() frees the current object anyway, but the real high IDR slot is left behind as a dangling pointer. 6. A subsequent walk of /proc/sysvipc/shm reaches the stale IDR entry and dereferences freed memory. Prevent this by bounding the requested allocation to ipc_mni so the checkpoint/restore path fails once the valid range is exhausted. 2026-07-09 CVE-2026-52923 openEuler-20.03-LTS-SP4 High 7.0 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H kernel security update 2026-07-09 https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2929 In the Linux kernel, the following vulnerability has been resolved: RDMA/umem: Fix truncation for block sizes >= 4G When the iommu is used the linearization of the mapping can give a single block that is very large split across multiple SG entries. When __rdma_block_iter_next() reassembles the split SG entries it is overflowing the 32 bit stack values and computed the wrong DMA addresses for blocks after the truncation. Use the right types to hold DMA addresses. 2026-07-09 CVE-2026-53133 openEuler-20.03-LTS-SP4 High 7.8 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H kernel security update 2026-07-09 https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2929 In the Linux kernel, the following vulnerability has been resolved: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN In drivers/infiniband/ulp/isert/ib_isert.c, isert_login_recv_done() computes the login request payload length as wc->byte_len minus ISER_HEADERS_LEN with no lower bound, and login_req_len is a signed int. A remote iSER initiator can post a login Send work request carrying fewer than ISER_HEADERS_LEN (76) bytes, so the subtraction underflows and login_req_len becomes negative. isert_rx_login_req() then reads that negative length back into a signed int, takes size = min(rx_buflen, MAX_KEY_VALUE_PAIRS), and because the min() is signed it keeps the negative value; the value is then passed as the memcpy() length and sign-extended to a multi-gigabyte size_t. The copy into the 8192-byte login->req_buf runs far out of bounds and faults, crashing the target node. The login phase precedes iSCSI authentication, so no credentials are required to reach this path. Reject any login PDU shorter than ISER_HEADERS_LEN before the subtraction, mirroring the existing early return on a failed work completion, so login_req_len can never go negative. The upper bound was already safe: a posted login buffer cannot deliver more than ISER_RX_PAYLOAD_SIZE, so the difference stays at or below MAX_KEY_VALUE_PAIRS and the existing min() clamps it; only the missing lower bound needs to be added. 2026-07-09 CVE-2026-53176 openEuler-20.03-LTS-SP4 Medium 6.5 AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H kernel security update 2026-07-09 https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2929 In the Linux kernel, the following vulnerability has been resolved: USB: serial: kl5kusb105: fix bulk-out buffer overflow klsi_105_prepare_write_buffer() is called by the generic write path with the bulk-out buffer and its size (bulk_out_size, 64 bytes). It stores a two-byte length header at the start of the buffer and copies the payload from the write fifo starting at buf + KLSI_HDR_LEN, but passes the full buffer size as the number of bytes to copy: count = kfifo_out_locked(&port->write_fifo, buf + KLSI_HDR_LEN, size, &port->lock); When the fifo holds at least size bytes, size bytes are copied starting two bytes into the size-byte buffer, writing KLSI_HDR_LEN bytes past its end. Copy at most size - KLSI_HDR_LEN bytes instead, leaving room for the header as safe_serial already does. Writing bulk_out_size or more bytes to the tty triggers a slab out-of-bounds write, observed with KASAN by emulating the device with dummy_hcd and raw-gadget: BUG: KASAN: slab-out-of-bounds in kfifo_copy_out+0x83/0xc0 Write of size 64 at addr ffff888112c62202 by task python3 kfifo_copy_out klsi_105_prepare_write_buffer [kl5kusb105] usb_serial_generic_write_start [usbserial] Allocated by task 139: usb_serial_probe [usbserial] The buggy address is located 2 bytes inside of allocated 64-byte region The out-of-bounds write no longer occurs with this change applied. 2026-07-09 CVE-2026-53194 openEuler-20.03-LTS-SP4 Medium 5.3 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H kernel security update 2026-07-09 https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2929