Описание
ELSA-2026-55764: kernel security, bug fix, and enhancement update (IMPORTANT)
[4.18.0-553.155.1]
- Update Oracle Linux certificates (Kevin Lyons)
- Disable signing for aarch64 (Ilya Okomin)
- Oracle Linux RHCK Module Signing Key was added to the kernel trusted keys list (olkmod_signing_key.pem) [Orabug: 29539237]
- Update x509.genkey [Orabug: 24817676]
- Conflict with shim-ia32 and shim-x64 <= 15.3-1.0.3
- Remove upstream reference during boot (Kevin Lyons) [Orabug: 34750652]
- Add new Oracle Linux Driver Signing (key 1) certificate [Orabug: 37985772]
- udf: fix partition descriptor append bookkeeping (Ravi Singh) [RHEL-179571] {CVE-2026-45991}
- ice: fix double-free of tx_buf skb (Michal Schmidt) [RHEL-192193] {CVE-2026-53009}
[4.18.0-553.156.1]
- drm/amdkfd: Fix out-of-bounds write in kfd_event_page_set() (CKI Backport Bot) [RHEL-221327] {CVE-2026-43206}
- drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async (CKI Backport Bot) [RHEL-222576] {CVE-2026-64219}
- drm/amdgpu: fix amdgpu_hmm_range_get_pages (CKI Backport Bot) [RHEL-222620] {CVE-2026-63879}
- drm/i915: Fix potential UAF in TTM object purge (CKI Backport Bot) [RHEL-222738] {CVE-2026-63884}
- drm/amd/display: Use krealloc_array() in dal_vector_reserve() (CKI Backport Bot) [RHEL-222662] {CVE-2026-53329}
- drm/amd/display: Clamp VBIOS HDMI retimer register count to array size (CKI Backport Bot) [RHEL-222680] {CVE-2026-53136}
- mm/slub: avoid accessing metadata when pointer is invalid in object_err() (Luiz Capitulino) [RHEL-226551] {CVE-2025-39902}
- drm/amdgpu: zero-initialize GART table on allocation (CKI Backport Bot) [RHEL-222656] {CVE-2026-53374}
- vhost: reset the vring metadata cache on vring reconfiguration (CKI Backport Bot) [RHEL-224556]
- can: bcm: extend bcm_tx_lock usage for data and timer updates (Guillaume Nault) [RHEL-216711] {CVE-2026-17523}
- can: bcm: add locking when updating filter and timer values (Guillaume Nault) [RHEL-216711] {CVE-2026-17523}
- can: bcm: fix locking for bcm_op runtime updates (Guillaume Nault) [RHEL-216711] {CVE-2026-17523}
- can: bcm: add locking for bcm_op runtime updates (Guillaume Nault) [RHEL-216711] {CVE-2026-17523}
- can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write (Guillaume Nault) [RHEL-216711] {CVE-2026-17523}
- can: bcm: check the result of can_send() in bcm_can_tx() (Guillaume Nault) [RHEL-216711] {CVE-2026-17523}
- can: bcm: Use hrtimer_forward_now() (Guillaume Nault) [RHEL-216711] {CVE-2026-17523}
- can: bcm: switch timer to HRTIMER_MODE_SOFT and remove hrtimer_tasklet (Guillaume Nault) [RHEL-216711] {CVE-2026-17523}
- sched/deadline: Update GRUB description in the documentation (Herton R. Krzesinski) [RHEL-189997]
- sched/deadline: fix kABI breakage after the introduction of max_bw on dl_rq (Herton R. Krzesinski) [RHEL-189997]
- sched/deadline: Fix bandwidth reclaim equation in GRUB (Herton R. Krzesinski) [RHEL-189997]
- crypto: ccp - copy IV using skcipher ivsize (CKI Backport Bot) [RHEL-188453] {CVE-2026-53016}
Обновленные пакеты
Oracle Linux 8
Oracle Linux aarch64
kernel-tools-libs-devel
4.18.0-553.156.1.el8_10
bpftool
4.18.0-553.156.1.el8_10
kernel-cross-headers
4.18.0-553.156.1.el8_10
kernel-headers
4.18.0-553.156.1.el8_10
kernel-tools
4.18.0-553.156.1.el8_10
kernel-tools-libs
4.18.0-553.156.1.el8_10
perf
4.18.0-553.156.1.el8_10
python3-perf
4.18.0-553.156.1.el8_10
Oracle Linux x86_64
kernel-tools-libs-devel
4.18.0-553.156.1.el8_10
bpftool
4.18.0-553.156.1.el8_10
kernel
4.18.0-553.156.1.el8_10
kernel-abi-stablelists
4.18.0-553.156.1.el8_10
kernel-core
4.18.0-553.156.1.el8_10
kernel-cross-headers
4.18.0-553.156.1.el8_10
kernel-debug
4.18.0-553.156.1.el8_10
kernel-debug-core
4.18.0-553.156.1.el8_10
kernel-debug-devel
4.18.0-553.156.1.el8_10
kernel-debug-modules
4.18.0-553.156.1.el8_10
kernel-debug-modules-extra
4.18.0-553.156.1.el8_10
kernel-devel
4.18.0-553.156.1.el8_10
kernel-doc
4.18.0-553.156.1.el8_10
kernel-headers
4.18.0-553.156.1.el8_10
kernel-modules
4.18.0-553.156.1.el8_10
kernel-modules-extra
4.18.0-553.156.1.el8_10
kernel-tools
4.18.0-553.156.1.el8_10
kernel-tools-libs
4.18.0-553.156.1.el8_10
perf
4.18.0-553.156.1.el8_10
python3-perf
4.18.0-553.156.1.el8_10
Ссылки на источники
Связанные уязвимости
In the Linux kernel, the following vulnerability has been resolved: mm/slub: avoid accessing metadata when pointer is invalid in object_err() object_err() reports details of an object for further debugging, such as the freelist pointer, redzone, etc. However, if the pointer is invalid, attempting to access object metadata can lead to a crash since it does not point to a valid object. One known path to the crash is when alloc_consistency_checks() determines the pointer to the allocated object is invalid because of a freelist corruption, and calls object_err() to report it. The debug code should report and handle the corruption gracefully and not crash in the process. In case the pointer is NULL or check_valid_pointer() returns false for the pointer, only print the pointer value and skip accessing metadata.
In the Linux kernel, the following vulnerability has been resolved: mm/slub: avoid accessing metadata when pointer is invalid in object_err() object_err() reports details of an object for further debugging, such as the freelist pointer, redzone, etc. However, if the pointer is invalid, attempting to access object metadata can lead to a crash since it does not point to a valid object. One known path to the crash is when alloc_consistency_checks() determines the pointer to the allocated object is invalid because of a freelist corruption, and calls object_err() to report it. The debug code should report and handle the corruption gracefully and not crash in the process. In case the pointer is NULL or check_valid_pointer() returns false for the pointer, only print the pointer value and skip accessing metadata.
In the Linux kernel, the following vulnerability has been resolved: mm/slub: avoid accessing metadata when pointer is invalid in object_err() object_err() reports details of an object for further debugging, such as the freelist pointer, redzone, etc. However, if the pointer is invalid, attempting to access object metadata can lead to a crash since it does not point to a valid object. One known path to the crash is when alloc_consistency_checks() determines the pointer to the allocated object is invalid because of a freelist corruption, and calls object_err() to report it. The debug code should report and handle the corruption gracefully and not crash in the process. In case the pointer is NULL or check_valid_pointer() returns false for the pointer, only print the pointer value and skip accessing metadata.
mm/slub: avoid accessing metadata when pointer is invalid in object_err()