Описание
ELSA-2025-16354: kernel security update (MODERATE)
[6.12.0-55.34.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-headers
6.12.0-55.34.1.0.1.el10_0
perf
6.12.0-55.34.1.0.1.el10_0
python3-perf
6.12.0-55.34.1.0.1.el10_0
rtla
6.12.0-55.34.1.0.1.el10_0
rv
6.12.0-55.34.1.0.1.el10_0
kernel-tools
6.12.0-55.34.1.0.1.el10_0
kernel-tools-libs
6.12.0-55.34.1.0.1.el10_0
kernel-cross-headers
6.12.0-55.34.1.0.1.el10_0
kernel-tools-libs-devel
6.12.0-55.34.1.0.1.el10_0
libperf
6.12.0-55.34.1.0.1.el10_0
Oracle Linux x86_64
kernel-debug-devel
6.12.0-55.34.1.0.1.el10_0
kernel-debug-devel-matched
6.12.0-55.34.1.0.1.el10_0
kernel-devel
6.12.0-55.34.1.0.1.el10_0
kernel-devel-matched
6.12.0-55.34.1.0.1.el10_0
kernel-doc
6.12.0-55.34.1.0.1.el10_0
kernel-headers
6.12.0-55.34.1.0.1.el10_0
perf
6.12.0-55.34.1.0.1.el10_0
python3-perf
6.12.0-55.34.1.0.1.el10_0
rtla
6.12.0-55.34.1.0.1.el10_0
rv
6.12.0-55.34.1.0.1.el10_0
kernel
6.12.0-55.34.1.0.1.el10_0
kernel-abi-stablelists
6.12.0-55.34.1.0.1.el10_0
kernel-core
6.12.0-55.34.1.0.1.el10_0
kernel-debug
6.12.0-55.34.1.0.1.el10_0
kernel-debug-core
6.12.0-55.34.1.0.1.el10_0
kernel-debug-modules
6.12.0-55.34.1.0.1.el10_0
kernel-debug-modules-core
6.12.0-55.34.1.0.1.el10_0
kernel-debug-modules-extra
6.12.0-55.34.1.0.1.el10_0
kernel-debug-uki-virt
6.12.0-55.34.1.0.1.el10_0
kernel-modules
6.12.0-55.34.1.0.1.el10_0
kernel-modules-core
6.12.0-55.34.1.0.1.el10_0
kernel-modules-extra
6.12.0-55.34.1.0.1.el10_0
kernel-tools
6.12.0-55.34.1.0.1.el10_0
kernel-tools-libs
6.12.0-55.34.1.0.1.el10_0
kernel-uki-virt
6.12.0-55.34.1.0.1.el10_0
kernel-uki-virt-addons
6.12.0-55.34.1.0.1.el10_0
kernel-cross-headers
6.12.0-55.34.1.0.1.el10_0
kernel-tools-libs-devel
6.12.0-55.34.1.0.1.el10_0
libperf
6.12.0-55.34.1.0.1.el10_0
Связанные CVE
Связанные уязвимости
In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix handling of server side tls alerts Scott Mayhew discovered a security exploit in NFS over TLS in tls_alert_recv() due to its assumption it can read data from the msg iterator's kvec.. kTLS implementation splits TLS non-data record payload between the control message buffer (which includes the type such as TLS aler or TLS cipher change) and the rest of the payload (say TLS alert's level/description) which goes into the msg payload buffer. This patch proposes to rework how control messages are setup and used by sock_recvmsg(). If no control message structure is setup, kTLS layer will read and process TLS data record types. As soon as it encounters a TLS control message, it would return an error. At that point, NFS can setup a kvec backed msg buffer and read in the control message such as a TLS alert. Msg iterator can advance the kvec pointer as a part of the copy process thus we need to revert the iterator...
In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix handling of server side tls alerts Scott Mayhew discovered a security exploit in NFS over TLS in tls_alert_recv() due to its assumption it can read data from the msg iterator's kvec.. kTLS implementation splits TLS non-data record payload between the control message buffer (which includes the type such as TLS aler or TLS cipher change) and the rest of the payload (say TLS alert's level/description) which goes into the msg payload buffer. This patch proposes to rework how control messages are setup and used by sock_recvmsg(). If no control message structure is setup, kTLS layer will read and process TLS data record types. As soon as it encounters a TLS control message, it would return an error. At that point, NFS can setup a kvec backed msg buffer and read in the control message such as a TLS alert. Msg iterator can advance the kvec pointer as a part of the copy process thus we need to revert the iterator...
In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix handling of server side tls alerts Scott Mayhew discovered a security exploit in NFS over TLS in tls_alert_recv() due to its assumption it can read data from the msg iterator's kvec.. kTLS implementation splits TLS non-data record payload between the control message buffer (which includes the type such as TLS aler or TLS cipher change) and the rest of the payload (say TLS alert's level/description) which goes into the msg payload buffer. This patch proposes to rework how control messages are setup and used by sock_recvmsg(). If no control message structure is setup, kTLS layer will read and process TLS data record types. As soon as it encounters a TLS control message, it would return an error. At that point, NFS can setup a kvec backed msg buffer and read in the control message such as a TLS alert. Msg iterator can advance the kvec pointer as a part of the copy process thus we need to revert the iterat
In the Linux kernel, the following vulnerability has been resolved: s ...
In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: gadget: check that event count does not exceed event buffer length The event count is read from register DWC3_GEVNTCOUNT. There is a check for the count being zero, but not for exceeding the event buffer length. Check that event count does not exceed event buffer length, avoiding an out-of-bounds access when memcpy'ing the event. Crash log: Unable to handle kernel paging request at virtual address ffffffc0129be000 pc : __memcpy+0x114/0x180 lr : dwc3_check_event_buf+0xec/0x348 x3 : 0000000000000030 x2 : 000000000000dfc4 x1 : ffffffc0129be000 x0 : ffffff87aad60080 Call trace: __memcpy+0x114/0x180 dwc3_interrupt+0x24/0x34