kernel-5.14.0-687.60.1.el9_8

エラータID: AXSA:2026-2319:128

Release date: 
Tuesday, November 17, 2026 - 14:16
Subject: 
kernel-5.14.0-687.60.1.el9_8
Affected Channels: 
MIRACLE LINUX 9 for x86_64
Severity: 
High
Description: 

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

* kernel: netlabel: Fix NULL pointer exception caused by CALIPSO on IPv4 sockets (CVE-2025-22063)
* kernel: calipso: Don't call calipso functions for AF_INET sk. (CVE-2025-38147)
* kernel: ALSA: hda/cs35l41: Fix firmware load work teardown (CVE-2026-64481)
* kernel: ALSA: seq: close a re-opened queue timer in the destructor (CVE-2026-68202)
* kernel: vmxnet3: fix BUG_ON in vmxnet3_get_hdr_len() for Geneve packets (CVE-2026-68299)
* kernel: ovl: check access to copy_file_range source with src mounter creds (CVE-2026-68448)
* kernel: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN (CVE-2026-80530)
* kernel: xfs: bounds-check buffer log item's dirty bitmap (CVE-2026-80536)

Bug Fix(es) and Enhancement(s):

* RTLA segfaults on freed memory access on double SIGINT [rhel-9.8.z] (JIRA:RHEL-193029)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

CVE-2025-22063
In the Linux kernel, the following vulnerability has been resolved: netlabel: Fix NULL pointer exception caused by CALIPSO on IPv4 sockets When calling netlbl_conn_setattr(), addr->sa_family is used to determine the function behavior. If sk is an IPv4 socket, but the connect function is called with an IPv6 address, the function calipso_sock_setattr() is triggered. Inside this function, the following code is executed: sk_fullsock(__sk) ? inet_sk(__sk)->pinet6 : NULL; Since sk is an IPv4 socket, pinet6 is NULL, leading to a null pointer dereference. This patch fixes the issue by checking if inet6_sk(sk) returns a NULL pointer before accessing pinet6.
CVE-2025-38147
In the Linux kernel, the following vulnerability has been resolved: calipso: Don't call calipso functions for AF_INET sk. syzkaller reported a null-ptr-deref in txopt_get(). [0] The offset 0x70 was of struct ipv6_txoptions in struct ipv6_pinfo, so struct ipv6_pinfo was NULL there. However, this never happens for IPv6 sockets as inet_sk(sk)->pinet6 is always set in inet6_create(), meaning the socket was not IPv6 one. The root cause is missing validation in netlbl_conn_setattr(). netlbl_conn_setattr() switches branches based on struct sockaddr.sa_family, which is passed from userspace. However, netlbl_conn_setattr() does not check if the address family matches the socket. The syzkaller must have called connect() for an IPv6 address on an IPv4 socket. We have a proper validation in tcp_v[46]_connect(), but security_socket_connect() is called in the earlier stage. Let's copy the validation to netlbl_conn_setattr(). [0]: Oops: general protection fault, probably for non-canonical address 0xdffffc000000000e: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000070-0x0000000000000077] CPU: 2 UID: 0 PID: 12928 Comm: syz.9.1677 Not tainted 6.12.0 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:txopt_get include/net/ipv6.h:390 [inline] RIP: 0010: Code: 02 00 00 49 8b ac 24 f8 02 00 00 e8 84 69 2a fd e8 ff 00 16 fd 48 8d 7d 70 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 53 02 00 00 48 8b 6d 70 48 85 ed 0f 84 ab 01 00 RSP: 0018:ffff88811b8afc48 EFLAGS: 00010212 RAX: dffffc0000000000 RBX: 1ffff11023715f8a RCX: ffffffff841ab00c RDX: 000000000000000e RSI: ffffc90007d9e000 RDI: 0000000000000070 RBP: 0000000000000000 R08: ffffed1023715f9d R09: ffffed1023715f9e R10: ffffed1023715f9d R11: 0000000000000003 R12: ffff888123075f00 R13: ffff88810245bd80 R14: ffff888113646780 R15: ffff888100578a80 FS: 00007f9019bd7640(0000) GS:ffff8882d2d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f901b927bac CR3: 0000000104788003 CR4: 0000000000770ef0 PKRU: 80000000 Call Trace: calipso_sock_setattr+0x56/0x80 net/netlabel/netlabel_calipso.c:557 netlbl_conn_setattr+0x10c/0x280 net/netlabel/netlabel_kapi.c:1177 selinux_netlbl_socket_connect_helper+0xd3/0x1b0 security/selinux/netlabel.c:569 selinux_netlbl_socket_connect_locked security/selinux/netlabel.c:597 [inline] selinux_netlbl_socket_connect+0xb6/0x100 security/selinux/netlabel.c:615 selinux_socket_connect+0x5f/0x80 security/selinux/hooks.c:4931 security_socket_connect+0x50/0xa0 security/security.c:4598 __sys_connect_file+0xa4/0x190 net/socket.c:2067 __sys_connect+0x12c/0x170 net/socket.c:2088 __do_sys_connect net/socket.c:2098 [inline] __se_sys_connect net/socket.c:2095 [inline] __x64_sys_connect+0x73/0xb0 net/socket.c:2095 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xaa/0x1b0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f901b61a12d Code: 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f9019bd6fa8 EFLAGS: 00000246 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 00007f901b925fa0 RCX: 00007f901b61a12d RDX: 000000000000001c RSI: 0000200000000140 RDI: 0000000000000003 RBP: 00007f901b701505 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f901b5b62a0 R15: 00007f9019bb7000 Modules linked in:
CVE-2026-64481
In the Linux kernel, the following vulnerability has been resolved: ALSA: hda/cs35l41: Fix firmware load work teardown cs35l41_hda creates ALSA controls whose private data points at the cs35l41_hda object. The firmware load control can also queue fw_load_work. Those controls are not removed on component unbind, and device remove only cancels fw_load_work through cs35l41_remove_dsp(). That helper is skipped when halo_initialized is false. With firmware_autostart disabled, a firmware load can be requested before the DSP has been initialized. If the component or device is removed before the queued work runs, the worker can run after teardown and dereference driver state that is no longer valid. Track the created controls and remove them on unbind so no new control callback can reach the driver data or queue more work. Then cancel fw_load_work to drain any request that was already queued. Also cancel the work unconditionally during device remove before runtime PM teardown.
CVE-2026-68202
In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: close a re-opened queue timer in the destructor queue_delete() closes the queue timer, then frees it. snd_seq_timer_close() clears q->timer->timeri. snd_use_lock_sync() then drains borrowers, and snd_seq_timer_delete() frees q->timer. A borrower can re-open the timer inside that window. A SET_QUEUE_CLIENT that took a queueptr() use_lock reference before the queue was unlinked runs snd_seq_timer_open() after the close. Open refuses re-open only while timeri is set, and the close just cleared it, so it re-opens timeri. snd_seq_timer_delete() does not close that instance. Its snd_seq_timer_stop() is a no-op, because running was cleared first. So it frees q->timer with the instance still live. The queue is freed next. The instance stays on the global timer with callback_data pointing at the freed queue. A non-owner START on the unlocked queue arms it. The next tick derefs the freed queue in snd_seq_timer_interrupt(). Reachable by an unprivileged user with access to /dev/snd/seq. No CAP and no queue ownership required. Close any lingering instance in the destructor. There, ->timeri can no longer change: the queue is unlinked and all use_lock borrowers have drained, so no snd_seq_queue_use() can re-open it. Close it before clearing q->timer. snd_timer_close() waits for any in-flight snd_seq_timer_interrupt() to finish, and that callback still reads q->timer (via snd_seq_check_queue()), so q->timer must stay valid until it drains.
CVE-2026-68299
In the Linux kernel, the following vulnerability has been resolved: vmxnet3: fix BUG_ON in vmxnet3_get_hdr_len() for Geneve packets vmxnet3_get_hdr_len() assumes gdesc->rcd.v4/v6/tcp always describe the outer header, but for a Geneve-encapsulated packet the device can set them based on the inner header instead, signalled by the VMXNET3_RCD_HDR_INNER_SHIFT bit in the completion descriptor. Since the function never skips the outer encapsulation, this mismatch triggers: - BUG_ON(hdr.ipv4->protocol != IPPROTO_TCP), because the outer protocol is UDP (Geneve), not TCP. - BUG_ON(hdr.eth->h_proto != ...), when the tunnel's outer and inner IP versions differ (e.g. outer IPv6/inner IPv4 or vice versa). Check VMXNET3_RCD_HDR_INNER_SHIFT up front and bail out, since the function cannot locate the inner header it would need to parse. Also convert the remaining BUG_ON()s in this function to return 0 defensively.
CVE-2026-68448
In the Linux kernel, the following vulnerability has been resolved: ovl: check access to copy_file_range source with src mounter creds Commit 5dae222a5ff0c ("vfs: allow copy_file_range to copy across devices") allowed filesystems that implement the copy_file_range() f_op to decide if they want to access cross-sb copy from/to the same fs type. The same commit added checks to verify same sb copy for filesystems that implement ->copy_file_range() and do not support cross-sb copy at the time, namely, to ceph, fuse and nfs. The two remaining fs which implement ->copy_file_range(), cifs and overlayfs started to support cross-sb copy from this time. While overlayfs does support cross-sb copy when the two underlying files are on the same base fs, the copy operation on the two real files from two different overalyfs filesystems is performed with the mounter creds of the destination overlayfs and the read permission access hook for the source file was called with the wrong creds. This could cause either deny of access to copy which would otherwise be allowed (e.g. with splice) or allow read access to file which would otherwise be denied. Fix the latter case by explicitly verifying read access to source file with the source overlayfs mounter creds. The former case remains a quirk of cross-sb overlayfs copy, but userspace could fall back to regular copy so no harm done.
CVE-2026-80530
In the Linux kernel, the following vulnerability has been resolved: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN When exchanging two full-file ranges, xmi_can_exchange_reflink_flags() can move the reflink inode flag from the file that currently has it to the other file, as long as exactly one side is marked. This assumes that the file contents, and therefore all shared extents, are exchanged. That assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set. xfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings from file1, so an exchange can complete without moving every mapping that the earlier flag-swap decision accounted for. In that case the post-operation cleanup can clear the reflink flag from an inode that still owns shared written extents. Later writes then take the non-reflink write path and may update blocks that should still have been protected by CoW, which shows up as data corruption between reflink-related files. Fix this by disabling the reflink flag exchange whenever XFS_EXCHMAPS_INO1_WRITTEN is requested. The contents exchange can still proceed; the conservative outcome is that both inodes keep the reflink flag. The regular reflink flag cleanup path can drop the extra flag later once the inode no longer has shared extents.
CVE-2026-80536
In the Linux kernel, the following vulnerability has been resolved: xfs: bounds-check buffer log item's dirty bitmap xlog_recover_do_reg_buffer() replays each dirty region described by a buffer log item's bitmap into the buffer read for that item: memcpy(xfs_buf_offset(bp, (uint)bit << XFS_BLF_SHIFT), item->ri_buf[i].iov_base, nbits << XFS_BLF_SHIFT); The destination offset (bit/nbits, from the logged dirty bitmap) and the buffer size (from the logged blf_len) are both attacker-controlled and otherwise unrelated, yet the only thing bounding the copy is an ASSERT(), which compiles away on production kernels. A crafted image logging a small blf_len together with a bitmap bit past the end of that buffer drives the memcpy() past the buffer's allocation, corrupting adjacent kernel heap during mount-time log recovery. This is reachable by anyone who can get a crafted image mounted -- the malicious-filesystem threat model XFS already guards against elsewhere. Turn the ASSERT() into a real XFS_IS_CORRUPT() check that aborts recovery of the buffer with -EFSCORRUPTED, consistent with the validate-and-fail idiom already used in xlog_recover_do_inode_buffer() and xfs_dquot_item_recover.c. xlog_recover_do_reg_buffer() therefore becomes STATIC int and its three callers propagate the error. Found and confirmed with KASAN on a CONFIG_XFS_DEBUG=n build: the crafted image trips a slab-out-of-bounds write before this change and fails recovery cleanly with -EFSCORRUPTED after it.

Solution: 

Update packages.

Additional Info: 

N/A

Download: 

SRPMS
  1. kernel-5.14.0-687.60.1.el9_8.src.rpm
    MD5: 9fd76353f88513087ffa110504514ce6
    SHA-256: 8c6e95fd8d514a0de7ef22a1ba552faf11ad56ad9a3099667413e3d8fe085d4b
    Size: 145.69 MB

Asianux Server 9 for x86_64
  1. kernel-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: ba479fbc5f1899ede339482ac5d90217
    SHA-256: e4dbeef2718c3e8917f02571176be37e3c7bcce3ca2c8f54207c3e6e8e716e2a
    Size: 1.05 MB
  2. kernel-abi-stablelists-5.14.0-687.60.1.el9_8.noarch.rpm
    MD5: d85e853d8f0093b72c6c318433bd7512
    SHA-256: ac8ea5f89a5467a2d54e46f17bc12351170bde5abb8ffe0db453e519c3120b1d
    Size: 1.08 MB
  3. kernel-core-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 83394941412be65054b82e740a446295
    SHA-256: 49c21f91f355e54b60e54c4b9ccc1d9a36854dc8bd47cb0c126a4ddfac56ebb6
    Size: 17.37 MB
  4. kernel-cross-headers-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: fd6c180d6ba7f5a16718cad754940d37
    SHA-256: 9afcf24caee3fad58916e2e95ee57bf66c09398d443354f43818fe50d59923bc
    Size: 8.11 MB
  5. kernel-debug-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: bc2fe131069c416d7a7b3ca10b4ed0b0
    SHA-256: b24ba0b3e5c07f58ebac78bca0c9a272065e52ce335cf9b13492fb9ab0fa5885
    Size: 1.05 MB
  6. kernel-debug-core-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: cb313e9a5f60d28f7ad37d3794380e20
    SHA-256: a0948445e50aace16f282ddb34c6485da8c1a4d0120d2b41903cd177966cb796
    Size: 31.25 MB
  7. kernel-debug-devel-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 5a97d39b3415081e0dadfd4ff012da8f
    SHA-256: 958daaf4969ed2a544cd03e147e9692caba4e07fe611ac120bd1b7e62f302e41
    Size: 21.47 MB
  8. kernel-debug-devel-matched-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: a9267e6c284e57896dc2b2717f5d017c
    SHA-256: 1c5686880a9c3e231e866a7723ff092607939f0a4063f6e25a8cfb4a3cbfb61b
    Size: 1.05 MB
  9. kernel-debug-modules-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 982c5aae50ae8244a36e8f47294586ed
    SHA-256: 4f21775469603be15cb0ac7f1f4d6e0e0af2e5ea38b84534ae7d2ebe972d01f1
    Size: 70.24 MB
  10. kernel-debug-modules-core-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 733b39421630556d24bf9099812fe816
    SHA-256: 8914fdbe3a2e295ef50c38a8874ed0fd704d6f4301420f003b59c1bfd56c38cc
    Size: 49.97 MB
  11. kernel-debug-modules-extra-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: ac6ca4987edcfa03360566d0d85c21b9
    SHA-256: a350ae473dfc2cf9dcb28cfacc919bee2a053db174daa47d22e416e8f8645017
    Size: 1.85 MB
  12. kernel-debug-uki-virt-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: d1a5373d6399f367bb76d2bc0181726e
    SHA-256: 8c82fba739b085794dac8d0b3292a5ad30515ec6c64e02b04d9ba5733f06ff69
    Size: 88.20 MB
  13. kernel-devel-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 974a28b30f3f189eb8b1dd40f831d8d2
    SHA-256: b9a374b77434af3e65b55c4139b9093b887c3c346ca5f99b137edbc77c5bd2ca
    Size: 21.28 MB
  14. kernel-devel-matched-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 53725259f93dde7c261bfcae7c500e3c
    SHA-256: 6c47cf91620424887a572f20a7213d732317a964d4a27185ec2e74caaebb80ce
    Size: 1.05 MB
  15. kernel-doc-5.14.0-687.60.1.el9_8.noarch.rpm
    MD5: b34b52fb2ceca5ee921c0738d7496973
    SHA-256: 7ef0ab7838fcb883b91fe63dd2a00998f7b979bf895517a1301f45f759f4f6c6
    Size: 39.07 MB
  16. kernel-headers-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 37cd5fe3b060f0d5e390d7aebcc203fb
    SHA-256: 270de3a152c4950d60e457d7792129528de9c3820b0dd4eb665ff10d31d67f31
    Size: 2.84 MB
  17. kernel-modules-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 665aaf25b5b3f5f239537b1bc095583c
    SHA-256: 843cbe7e483e93210206fcac7ac719a45dbefea03e6145c77bf40514d8a613d2
    Size: 40.06 MB
  18. kernel-modules-core-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: edc0ecbb5fabb326c8167872e7648d03
    SHA-256: 8f137816e5c32311f003146dd8b8000d218c64c66b02ec03bb7d9d323de402cc
    Size: 31.12 MB
  19. kernel-modules-extra-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: a57060049d6bf4c0a36eb5c459c3c480
    SHA-256: af8dde6ce58f7e26de28fa215db1193fd9ebc86f5a07cd2c315c8b0036ff684e
    Size: 1.49 MB
  20. kernel-rt-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: b5fca5adccd0c3bd9621f710623326cf
    SHA-256: 1405e55942b91d44735fd3f111a3179e055c906ff579e3a59dd88090d5f2865c
    Size: 1.05 MB
  21. kernel-rt-core-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 5dfe4a3f4a5be83d79ee3a5c8ed14a83
    SHA-256: 27b9da318130a21babb7e3311c8f430653363df914beac7508c9dbf529d54dd6
    Size: 17.28 MB
  22. kernel-rt-debug-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 0fadef1f9f713b689da3028134f14077
    SHA-256: a887047a250280ed1c15e60d5b270b6a89a626c4d5a7e5e21ca8efb3ddc7cafc
    Size: 1.05 MB
  23. kernel-rt-debug-core-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 6937126de35838dd5d82608a897853e7
    SHA-256: 6e89aedaa4149915ccc2fa2c41de4190a8cc8349e6967a3482cf1bd287fe207f
    Size: 18.74 MB
  24. kernel-rt-debug-devel-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: b1cfcbed0ef7a89c6e6c67a2d8d35711
    SHA-256: 62384d003cdc5706d688b75217ce0ef54f8b2dd1af80c9433d84500bb63fa3d3
    Size: 21.41 MB
  25. kernel-rt-debug-modules-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: ba4a9b1241e84fbda99d18994573298d
    SHA-256: da2cd02cb17931437f8f9783a987c0eeaa55de0a554c08a1a818930ad2630a19
    Size: 41.63 MB
  26. kernel-rt-debug-modules-core-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: fd09fce071744af35a619250d0b88e3f
    SHA-256: 350d3a7cda67d9f346ed9fe67c5e9e5b6f75bce53f03cb5c30fb9a3b7cfb2266
    Size: 32.30 MB
  27. kernel-rt-debug-modules-extra-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: baf29a3b4272c1f7759acad03f582a4b
    SHA-256: 1a90846aa044e823d3e613174abff9974b9c57385af62e5f089fe8d7fb534aff
    Size: 1.52 MB
  28. kernel-rt-devel-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: aaaa698e0bdf1c83a8756ab69647dda8
    SHA-256: 3b3aece8f9e13f7293a9ddbe9d04a0d97c2d8b1f44260a5a5867fcf7ec11cd72
    Size: 21.26 MB
  29. kernel-rt-modules-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 9362e59acb83aade5440d69e6854bcb8
    SHA-256: 944b784d53211ea4074b712ac4e9b3c83cf8c2153ee57cc4e244044f07b5f065
    Size: 40.10 MB
  30. kernel-rt-modules-core-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 8de6b9fa5fbff15135ac8228869a33e7
    SHA-256: 0ec067345831cc5b4d857b3942205eb4bf52669871a09cef8b1a3e73e52fcd8e
    Size: 31.19 MB
  31. kernel-rt-modules-extra-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: ea3a3a3432c4ab4c3207bc71be5352ad
    SHA-256: d6ce82193c7213aa863e5d3b361124299ca735c2dc6e8be8dcafa057f4255478
    Size: 1.49 MB
  32. kernel-tools-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 3798520360a2204d6cdf281a0aa1f965
    SHA-256: d9455be2742805aff4667062e37605fa90e889aa5c4e6a08d9fa78c1841a35f3
    Size: 1.34 MB
  33. kernel-tools-libs-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 8e52df2c3f484ebb80b0732cbe49b83f
    SHA-256: 0111c6b90210999128463d141618bf2309ae3aa93cde84664a526733f27c0054
    Size: 1.06 MB
  34. kernel-tools-libs-devel-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 6eacb0553197c41c1c396c88965a19e9
    SHA-256: c62481bd1564ba7e75e93e2644099cd12998d0b1c8b37ec5df03047138da72b5
    Size: 1.05 MB
  35. kernel-uki-virt-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 7cc01edf5814d89d260db0155fe3de67
    SHA-256: c79fa328f0b56262b8d767fbce8648e67dc5bbec132972c7152b500ffd347c5b
    Size: 66.06 MB
  36. kernel-uki-virt-addons-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 7539d6591a5763457a9bc24fa52ff082
    SHA-256: b40deff0f4ff1220f71cda1ee1591bbe69540944f814d5bc40808412104902b9
    Size: 1.07 MB
  37. libperf-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 3cde1362f48d1634a004a33a97f706bf
    SHA-256: 27e7352d2be119bf8370bdce4b8f20a8031719810474d9a0352d23f3f38dc329
    Size: 1.07 MB
  38. perf-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 405ea7be95dde5e43d41572c3fd8a08e
    SHA-256: 260d3f333f14b3a58a5091e0603969534b69f0e5594ddaf322f2cd4c6b053c48
    Size: 3.46 MB
  39. python3-perf-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 31fcddd3767e98d5cdbab75f841890d4
    SHA-256: a303ab2778b00d9fe40485a30832c53cdd51de73aa28b8815e116f88d60ab134
    Size: 2.64 MB
  40. rtla-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: c2eba10c550718a61a6d934a6dfc2008
    SHA-256: 5585c4e75859e31ae1909eee0ac86cafd48945f8d3c0cfa48d669d588de783c5
    Size: 1.12 MB
  41. rv-5.14.0-687.60.1.el9_8.x86_64.rpm
    MD5: 37371cb963c92b47599d4417bdf13f5a
    SHA-256: 344aab7c23372f464d4891224e766c7fbf28bf7a204af959b26b642e8de90224
    Size: 1.06 MB