Описание
ELSA-2025-16904: kernel security update (MODERATE)
[6.12.0-55.37.1.0.1]
- nvme-pci: remove two deallocate zeroes quirks [Orabug: 37756650]
- Add new Oracle Linux Driver Signing (key 1) certificate [Orabug: 37985782]
- Disable UKI signing [Orabug: 36571828]
- 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.5.el9
- Remove upstream reference during boot (Kevin Lyons) [Orabug: 34729535]
- Add Oracle Linux IMA certificates
- Update module name for cryptographic module [Orabug: 37400433]
Обновленные пакеты
Oracle Linux 10
Oracle Linux aarch64
kernel-cross-headers
6.12.0-55.37.1.0.1.el10_0
kernel-headers
6.12.0-55.37.1.0.1.el10_0
kernel-tools
6.12.0-55.37.1.0.1.el10_0
kernel-tools-libs
6.12.0-55.37.1.0.1.el10_0
kernel-tools-libs-devel
6.12.0-55.37.1.0.1.el10_0
libperf
6.12.0-55.37.1.0.1.el10_0
perf
6.12.0-55.37.1.0.1.el10_0
python3-perf
6.12.0-55.37.1.0.1.el10_0
rtla
6.12.0-55.37.1.0.1.el10_0
rv
6.12.0-55.37.1.0.1.el10_0
Oracle Linux x86_64
kernel
6.12.0-55.37.1.0.1.el10_0
kernel-abi-stablelists
6.12.0-55.37.1.0.1.el10_0
kernel-core
6.12.0-55.37.1.0.1.el10_0
kernel-cross-headers
6.12.0-55.37.1.0.1.el10_0
kernel-debug
6.12.0-55.37.1.0.1.el10_0
kernel-debug-core
6.12.0-55.37.1.0.1.el10_0
kernel-debug-devel
6.12.0-55.37.1.0.1.el10_0
kernel-debug-devel-matched
6.12.0-55.37.1.0.1.el10_0
kernel-debug-modules
6.12.0-55.37.1.0.1.el10_0
kernel-debug-modules-core
6.12.0-55.37.1.0.1.el10_0
kernel-debug-modules-extra
6.12.0-55.37.1.0.1.el10_0
kernel-debug-uki-virt
6.12.0-55.37.1.0.1.el10_0
kernel-devel
6.12.0-55.37.1.0.1.el10_0
kernel-devel-matched
6.12.0-55.37.1.0.1.el10_0
kernel-doc
6.12.0-55.37.1.0.1.el10_0
kernel-headers
6.12.0-55.37.1.0.1.el10_0
kernel-modules
6.12.0-55.37.1.0.1.el10_0
kernel-modules-core
6.12.0-55.37.1.0.1.el10_0
kernel-modules-extra
6.12.0-55.37.1.0.1.el10_0
kernel-tools
6.12.0-55.37.1.0.1.el10_0
kernel-tools-libs
6.12.0-55.37.1.0.1.el10_0
kernel-tools-libs-devel
6.12.0-55.37.1.0.1.el10_0
kernel-uki-virt
6.12.0-55.37.1.0.1.el10_0
kernel-uki-virt-addons
6.12.0-55.37.1.0.1.el10_0
libperf
6.12.0-55.37.1.0.1.el10_0
perf
6.12.0-55.37.1.0.1.el10_0
python3-perf
6.12.0-55.37.1.0.1.el10_0
rtla
6.12.0-55.37.1.0.1.el10_0
rv
6.12.0-55.37.1.0.1.el10_0
Ссылки на источники
Связанные уязвимости
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-after-free in cifs_oplock_break A race condition can occur in cifs_oplock_break() leading to a use-after-free of the cinode structure when unmounting: cifs_oplock_break() _cifsFileInfo_put(cfile) cifsFileInfo_put_final() cifs_sb_deactive() [last ref, start releasing sb] kill_sb() kill_anon_super() generic_shutdown_super() evict_inodes() dispose_list() evict() destroy_inode() call_rcu(&inode->i_rcu, i_callback) spin_lock(&cinode->open_file_lock) <- OK [later] i_callback() cifs_free_inode() kmem_cache_free(cinode) spin_unlock(&cinode->open_file_lock) <- UAF cifs_done_oplock_break(cinode) <- UAF The issue occurs when umount has already released its reference to the superblock. When _cifsFileInfo_put() calls cifs_sb_deactive(), this releases the last reference, triggering the immediate cleanup of all inodes under RCU. However, cifs_oplock_break() continues to access the cinode after this poi...
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-after-free in cifs_oplock_break A race condition can occur in cifs_oplock_break() leading to a use-after-free of the cinode structure when unmounting: cifs_oplock_break() _cifsFileInfo_put(cfile) cifsFileInfo_put_final() cifs_sb_deactive() [last ref, start releasing sb] kill_sb() kill_anon_super() generic_shutdown_super() evict_inodes() dispose_list() evict() destroy_inode() call_rcu(&inode->i_rcu, i_callback) spin_lock(&cinode->open_file_lock) <- OK [later] i_callback() cifs_free_inode() kmem_cache_free(cinode) spin_unlock(&cinode->open_file_lock) <- UAF cifs_done_oplock_break(cinode) <- UAF The issue occurs when umount has already released its reference to the superblock. When _cifsFileInfo_put() calls cifs_sb_deactive(), this releases the last reference, triggering the immediate cleanup of all inodes under RCU. However, cifs_oplock_break() continues to access the cinode after this poi...
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-after-free in cifs_oplock_break A race condition can occur in cifs_oplock_break() leading to a use-after-free of the cinode structure when unmounting: cifs_oplock_break() _cifsFileInfo_put(cfile) cifsFileInfo_put_final() cifs_sb_deactive() [last ref, start releasing sb] kill_sb() kill_anon_super() generic_shutdown_super() evict_inodes() dispose_list() evict() destroy_inode() call_rcu(&inode->i_rcu, i_callback) spin_lock(&cinode->open_file_lock) <- OK [later] i_callback() cifs_free_inode() kmem_cache_free(cinode) spin_unlock(&cinode->open_file_lock) <- UAF cifs_done_oplock_break(cinode) <- UAF The issue occur