Описание
ELSA-2026-92209: kernel security, bug fix, and enhancement update (IMPORTANT)
[4.18.0-553.180.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]
[4.18.0-553.180.1]
- KVM: arm64: vgic: Check the interrupt is still ours before migrating it (Mohammadfaiz Bawa) [RHEL-252475] {CVE-2026-72289}
- KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling (Mohammadfaiz Bawa) [RHEL-243811] {CVE-2026-72288}
- scsi: target: iscsi: Reserve a terminator byte for the login payload (CKI Backport Bot) [RHEL-285567] {CVE-2026-90011}
- KEYS: encrypted: fix integer overflow of datablob_len (Bruno Meneguele) [RHEL-279488] {CVE-2026-98222}
- arp: do not assume dev_hard_header() does not change skb->head (Guillaume Nault) [RHEL-271136]
- ip6_gre: make ip6gre_header() robust (Guillaume Nault) [RHEL-271136]
- ipv4: ip_gre: make ipgre_header() robust (Guillaume Nault) [RHEL-271135]
Обновленные пакеты
Oracle Linux 8
Oracle Linux aarch64
kernel-tools-libs-devel
4.18.0-553.180.1.el8_10
bpftool
4.18.0-553.180.1.el8_10
kernel-cross-headers
4.18.0-553.180.1.el8_10
kernel-headers
4.18.0-553.180.1.el8_10
kernel-tools
4.18.0-553.180.1.el8_10
kernel-tools-libs
4.18.0-553.180.1.el8_10
perf
4.18.0-553.180.1.el8_10
python3-perf
4.18.0-553.180.1.el8_10
Oracle Linux x86_64
kernel-tools-libs-devel
4.18.0-553.180.1.el8_10
kernel-modules-extra
4.18.0-553.180.1.el8_10
kernel-tools
4.18.0-553.180.1.el8_10
kernel-tools-libs
4.18.0-553.180.1.el8_10
perf
4.18.0-553.180.1.el8_10
python3-perf
4.18.0-553.180.1.el8_10
bpftool
4.18.0-553.180.1.el8_10
kernel
4.18.0-553.180.1.el8_10
kernel-abi-stablelists
4.18.0-553.180.1.el8_10
kernel-core
4.18.0-553.180.1.el8_10
kernel-cross-headers
4.18.0-553.180.1.el8_10
kernel-debug
4.18.0-553.180.1.el8_10
kernel-debug-core
4.18.0-553.180.1.el8_10
kernel-debug-devel
4.18.0-553.180.1.el8_10
kernel-debug-modules
4.18.0-553.180.1.el8_10
kernel-debug-modules-extra
4.18.0-553.180.1.el8_10
kernel-devel
4.18.0-553.180.1.el8_10
kernel-doc
4.18.0-553.180.1.el8_10
kernel-headers
4.18.0-553.180.1.el8_10
kernel-modules
4.18.0-553.180.1.el8_10
Связанные уязвимости
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling Hyunwoo Kim reports some really bad races should the following situation occur: - LPI-I is pending in vcpu-B's AP list - vcpu-A writes to vcpu-B's RD to disable its LPIs - vcpu-C moves I from B to C If the last two race nicely enough, vgic_prune_ap_list() can drop the irq and AP list locks, reacquire them, and in the interval the irq has been freed. UAF follows. The fix is two-fold: - Before dropping the irq and ap_list locks, take a reference on the irq - Do not try to handle migration of the pending bit: there is no expectation that this state is retained, as per the architecture With that, we're sure that the interrupt is still around, and we safely remove it from the AP list as it has no target at this stage (unless another interrupt fires, but that's another story).
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling Hyunwoo Kim reports some really bad races should the following situation occur: - LPI-I is pending in vcpu-B's AP list - vcpu-A writes to vcpu-B's RD to disable its LPIs - vcpu-C moves I from B to C If the last two race nicely enough, vgic_prune_ap_list() can drop the irq and AP list locks, reacquire them, and in the interval the irq has been freed. UAF follows. The fix is two-fold: - Before dropping the irq and ap_list locks, take a reference on the irq - Do not try to handle migration of the pending bit: there is no expectation that this state is retained, as per the architecture With that, we're sure that the interrupt is still around, and we safely remove it from the AP list as it has no target at this stage (unless another interrupt fires, but that's another story).
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling Hyunwoo Kim reports some really bad races should the following situation occur: - LPI-I is pending in vcpu-B's AP list - vcpu-A writes to vcpu-B's RD to disable its LPIs - vcpu-C moves I from B to C If the last two race nicely enough, vgic_prune_ap_list() can drop the irq and AP list locks, reacquire them, and in the interval the irq has been freed. UAF follows. The fix is two-fold: - Before dropping the irq and ap_list locks, take a reference on the irq - Do not try to handle migration of the pending bit: there is no expectation that this state is retained, as per the architecture With that, we're sure that the interrupt is still around, and we safely remove it from the AP list as it has no target at this stage (unless another interrupt fires, but that's another story).
In the Linux kernel, the following vulnerability has been resolved: K ...