An update for kernel is now available for openEuler-24.03-LTS-SP1 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2026-2751 Final 1.0 1.0 2026-06-24 Initial 2026-06-24 2026-06-24 openEuler SA Tool V1.0 2026-06-24 kernel security update An update for kernel is now available for openEuler-24.03-LTS-SP1 The Linux Kernel, the operating system core itself. Security Fix(es): In the Linux kernel, the following vulnerability has been resolved: pstore/ram: fix buffer overflow in persistent_ram_save_old() persistent_ram_save_old() can be called multiple times for the same persistent_ram_zone (e.g., via ramoops_pstore_read -> ramoops_get_next_prz for PSTORE_TYPE_DMESG records). Currently, the function only allocates prz->old_log when it is NULL, but it unconditionally updates prz->old_log_size to the current buffer size and then performs memcpy_fromio() using this new size. If the buffer size has grown since the first allocation (which can happen across different kernel boot cycles), this leads to: 1. A heap buffer overflow (OOB write) in the memcpy_fromio() calls 2. A subsequent OOB read when ramoops_pstore_read() accesses the buffer using the incorrect (larger) old_log_size The KASAN splat would look similar to: BUG: KASAN: slab-out-of-bounds in ramoops_pstore_read+0x... Read of size N at addr ... by task ... The conditions are likely extremely hard to hit: 0. Crash with a ramoops write of less-than-record-max-size bytes. 1. Reboot: ramoops registers, pstore_get_records(0) reads old crash, allocates old_log with size X 2. Crash handler registered, timer started (if pstore_update_ms >= 0) 3. Oops happens (non-fatal, system continues) 4. pstore_dump() writes oops via ramoops_pstore_write() size Y (>X) 5. pstore_new_entry = 1, pstore_timer_kick() called 6. System continues running (not a panic oops) 7. Timer fires after pstore_update_ms milliseconds 8. pstore_timefunc() → schedule_work() → pstore_dowork() → pstore_get_records(1) 9. ramoops_get_next_prz() → persistent_ram_save_old() 10. buffer_size() returns Y, but old_log is X bytes 11. Y > X: memcpy_fromio() overflows heap Requirements: - a prior crash record exists that did not fill the record size (almost impossible since the crash handler writes as much as it can possibly fit into the record, capped by max record size and the kmsg buffer almost always exceeds the max record size) - pstore_update_ms >= 0 (disabled by default) - Non-fatal oops (system survives) Free and reallocate the buffer when the new size differs from the previously allocated size. This ensures old_log always has sufficient space for the data being copied. The Linux kernel CVE team has assigned CVE-2026-46253 to this issue.(CVE-2026-46253) In the Linux kernel, the following vulnerability has been resolved: net/sched: fix pedit partial COW leading to page cache corruption tcf_pedit_act() computes the COW range for skb_ensure_writable() once before the key loop using tcfp_off_max_hint, but the hint does not account for the runtime header offset added by typed keys. This can leave part of the write region un-COW'd. Fix by moving skb_ensure_writable() inside the per-key loop where the actual write offset is known, and add overflow checking on the offset arithmetic. For negative offsets (e.g. Ethernet header edits at ingress), use skb_cow() to COW the headroom instead. Guard offset_valid() against INT_MIN, where negation is undefined.(CVE-2026-46331) An update for kernel is now available for openEuler-24.03-LTS-SP1/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-2751 https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2026-46253 https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2026-46331 https://nvd.nist.gov/vuln/detail/CVE-2026-46253 https://nvd.nist.gov/vuln/detail/CVE-2026-46331 openEuler-24.03-LTS-SP1 bpftool-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm bpftool-debuginfo-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm kernel-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm kernel-debuginfo-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm kernel-debugsource-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm kernel-devel-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm kernel-headers-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm kernel-source-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm kernel-tools-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm kernel-tools-debuginfo-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm kernel-tools-devel-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm perf-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm perf-debuginfo-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm python3-perf-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm python3-perf-debuginfo-6.6.0-145.1.16.154.oe2403sp1.aarch64.rpm bpftool-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm bpftool-debuginfo-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm kernel-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm kernel-debuginfo-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm kernel-debugsource-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm kernel-devel-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm kernel-headers-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm kernel-source-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm kernel-tools-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm kernel-tools-debuginfo-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm kernel-tools-devel-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm perf-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm perf-debuginfo-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm python3-perf-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm python3-perf-debuginfo-6.6.0-145.1.16.154.oe2403sp1.x86_64.rpm kernel-6.6.0-145.1.16.154.oe2403sp1.src.rpm In the Linux kernel, the following vulnerability has been resolved: pstore/ram: fix buffer overflow in persistent_ram_save_old() persistent_ram_save_old() can be called multiple times for the same persistent_ram_zone (e.g., via ramoops_pstore_read -> ramoops_get_next_prz for PSTORE_TYPE_DMESG records). Currently, the function only allocates prz->old_log when it is NULL, but it unconditionally updates prz->old_log_size to the current buffer size and then performs memcpy_fromio() using this new size. If the buffer size has grown since the first allocation (which can happen across different kernel boot cycles), this leads to: 1. A heap buffer overflow (OOB write) in the memcpy_fromio() calls 2. A subsequent OOB read when ramoops_pstore_read() accesses the buffer using the incorrect (larger) old_log_size The KASAN splat would look similar to: BUG: KASAN: slab-out-of-bounds in ramoops_pstore_read+0x... Read of size N at addr ... by task ... The conditions are likely extremely hard to hit: 0. Crash with a ramoops write of less-than-record-max-size bytes. 1. Reboot: ramoops registers, pstore_get_records(0) reads old crash, allocates old_log with size X 2. Crash handler registered, timer started (if pstore_update_ms >= 0) 3. Oops happens (non-fatal, system continues) 4. pstore_dump() writes oops via ramoops_pstore_write() size Y (>X) 5. pstore_new_entry = 1, pstore_timer_kick() called 6. System continues running (not a panic oops) 7. Timer fires after pstore_update_ms milliseconds 8. pstore_timefunc() → schedule_work() → pstore_dowork() → pstore_get_records(1) 9. ramoops_get_next_prz() → persistent_ram_save_old() 10. buffer_size() returns Y, but old_log is X bytes 11. Y > X: memcpy_fromio() overflows heap Requirements: - a prior crash record exists that did not fill the record size (almost impossible since the crash handler writes as much as it can possibly fit into the record, capped by max record size and the kmsg buffer almost always exceeds the max record size) - pstore_update_ms >= 0 (disabled by default) - Non-fatal oops (system survives) Free and reallocate the buffer when the new size differs from the previously allocated size. This ensures old_log always has sufficient space for the data being copied. The Linux kernel CVE team has assigned CVE-2026-46253 to this issue. 2026-06-24 CVE-2026-46253 openEuler-24.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 2026-06-24 https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2751 In the Linux kernel, the following vulnerability has been resolved: net/sched: fix pedit partial COW leading to page cache corruption tcf_pedit_act() computes the COW range for skb_ensure_writable() once before the key loop using tcfp_off_max_hint, but the hint does not account for the runtime header offset added by typed keys. This can leave part of the write region un-COW'd. Fix by moving skb_ensure_writable() inside the per-key loop where the actual write offset is known, and add overflow checking on the offset arithmetic. For negative offsets (e.g. Ethernet header edits at ingress), use skb_cow() to COW the headroom instead. Guard offset_valid() against INT_MIN, where negation is undefined. 2026-06-24 CVE-2026-46331 openEuler-24.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 2026-06-24 https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2751