RHSA-2024:5363
Vulnerability from csaf_redhat - Published: 2024-08-15 05:34 - Updated: 2026-09-01 11:55In the Linux kernel, the following vulnerability has been resolved: net: netlink: af_netlink: Prevent empty skb by adding a check on len. Adding a check on len parameter to avoid empty skb. This prevents a division error in netem_enqueue function which is caused when skb->len=0 and skb->data_len=0 in the randomized corruption step as shown below. skb->data[prandom_u32() % skb_headlen(skb)] ^= 1<<(prandom_u32() % 8); Crash Report: [ 343.170349] netdevsim netdevsim0 netdevsim3: set [1, 0] type 2 family 0 port 6081 - 0 [ 343.216110] netem: version 1.3 [ 343.235841] divide error: 0000 [#1] PREEMPT SMP KASAN NOPTI [ 343.236680] CPU: 3 PID: 4288 Comm: reproducer Not tainted 5.16.0-rc1+ [ 343.237569] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.0-2.el7 04/01/2014 [ 343.238707] RIP: 0010:netem_enqueue+0x1590/0x33c0 [sch_netem] [ 343.239499] Code: 89 85 58 ff ff ff e8 5f 5d e9 d3 48 8b b5 48 ff ff ff 8b 8d 50 ff ff ff 8b 85 58 ff ff ff 48 8b bd 70 ff ff ff 31 d2 2b 4f 74 <f7> f1 48 b8 00 00 00 00 00 fc ff df 49 01 d5 4c 89 e9 48 c1 e9 03 [ 343.241883] RSP: 0018:ffff88800bcd7368 EFLAGS: 00010246 [ 343.242589] RAX: 00000000ba7c0a9c RBX: 0000000000000001 RCX: 0000000000000000 [ 343.243542] RDX: 0000000000000000 RSI: ffff88800f8edb10 RDI: ffff88800f8eda40 [ 343.244474] RBP: ffff88800bcd7458 R08: 0000000000000000 R09: ffffffff94fb8445 [ 343.245403] R10: ffffffff94fb8336 R11: ffffffff94fb8445 R12: 0000000000000000 [ 343.246355] R13: ffff88800a5a7000 R14: ffff88800a5b5800 R15: 0000000000000020 [ 343.247291] FS: 00007fdde2bd7700(0000) GS:ffff888109780000(0000) knlGS:0000000000000000 [ 343.248350] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 343.249120] CR2: 00000000200000c0 CR3: 000000000ef4c000 CR4: 00000000000006e0 [ 343.250076] Call Trace: [ 343.250423] <TASK> [ 343.250713] ? memcpy+0x4d/0x60 [ 343.251162] ? netem_init+0xa0/0xa0 [sch_netem] [ 343.251795] ? __sanitizer_cov_trace_pc+0x21/0x60 [ 343.252443] netem_enqueue+0xe28/0x33c0 [sch_netem] [ 343.253102] ? stack_trace_save+0x87/0xb0 [ 343.253655] ? filter_irq_stacks+0xb0/0xb0 [ 343.254220] ? netem_init+0xa0/0xa0 [sch_netem] [ 343.254837] ? __kasan_check_write+0x14/0x20 [ 343.255418] ? _raw_spin_lock+0x88/0xd6 [ 343.255953] dev_qdisc_enqueue+0x50/0x180 [ 343.256508] __dev_queue_xmit+0x1a7e/0x3090 [ 343.257083] ? netdev_core_pick_tx+0x300/0x300 [ 343.257690] ? check_kcov_mode+0x10/0x40 [ 343.258219] ? _raw_spin_unlock_irqrestore+0x29/0x40 [ 343.258899] ? __kasan_init_slab_obj+0x24/0x30 [ 343.259529] ? setup_object.isra.71+0x23/0x90 [ 343.260121] ? new_slab+0x26e/0x4b0 [ 343.260609] ? kasan_poison+0x3a/0x50 [ 343.261118] ? kasan_unpoison+0x28/0x50 [ 343.261637] ? __kasan_slab_alloc+0x71/0x90 [ 343.262214] ? memcpy+0x4d/0x60 [ 343.262674] ? write_comp_data+0x2f/0x90 [ 343.263209] ? __kasan_check_write+0x14/0x20 [ 343.263802] ? __skb_clone+0x5d6/0x840 [ 343.264329] ? __sanitizer_cov_trace_pc+0x21/0x60 [ 343.264958] dev_queue_xmit+0x1c/0x20 [ 343.265470] netlink_deliver_tap+0x652/0x9c0 [ 343.266067] netlink_unicast+0x5a0/0x7f0 [ 343.266608] ? netlink_attachskb+0x860/0x860 [ 343.267183] ? __sanitizer_cov_trace_pc+0x21/0x60 [ 343.267820] ? write_comp_data+0x2f/0x90 [ 343.268367] netlink_sendmsg+0x922/0xe80 [ 343.268899] ? netlink_unicast+0x7f0/0x7f0 [ 343.269472] ? __sanitizer_cov_trace_pc+0x21/0x60 [ 343.270099] ? write_comp_data+0x2f/0x90 [ 343.270644] ? netlink_unicast+0x7f0/0x7f0 [ 343.271210] sock_sendmsg+0x155/0x190 [ 343.271721] ____sys_sendmsg+0x75f/0x8f0 [ 343.272262] ? kernel_sendmsg+0x60/0x60 [ 343.272788] ? write_comp_data+0x2f/0x90 [ 343.273332] ? write_comp_data+0x2f/0x90 [ 343.273869] ___sys_sendmsg+0x10f/0x190 [ 343.274405] ? sendmsg_copy_msghdr+0x80/0x80 [ 343.274984] ? slab_post_alloc_hook+0x70/0x230 [ 343.275597] ? futex_wait_setup+0x240/0x240 [ 343.276175] ? security_file_alloc+0x3e/0x170 [ 343.276779] ? write_comp_d ---truncated---
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:bpftool-debuginfo-0:7.3.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:bpftool-debuginfo-0:7.3.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:bpftool-debuginfo-0:7.3.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:bpftool-debuginfo-0:7.3.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-64k-debug-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-64k-debug-devel-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-64k-debug-devel-matched-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-64k-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-64k-devel-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-64k-devel-matched-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debug-devel-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debug-devel-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debug-devel-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debug-devel-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debug-devel-matched-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debug-devel-matched-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debug-devel-matched-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debug-devel-matched-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debuginfo-common-aarch64-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debuginfo-common-ppc64le-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debuginfo-common-s390x-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-debuginfo-common-x86_64-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-devel-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-devel-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-devel-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-devel-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-devel-matched-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-devel-matched-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-devel-matched-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-devel-matched-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-doc-0:5.14.0-427.31.1.el9_4.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-rt-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-rt-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-zfcpdump-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-zfcpdump-devel-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-zfcpdump-devel-matched-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:libperf-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:libperf-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:libperf-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:libperf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:perf-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:perf-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:perf-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:perf-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:perf-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:perf-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:perf-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:perf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:python3-perf-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:python3-perf-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:python3-perf-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:python3-perf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:rtla-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:rtla-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:rtla-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:rtla-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:rv-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:rv-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:rv-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:rv-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:bpftool-0:7.3.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:bpftool-0:7.3.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:bpftool-0:7.3.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:bpftool-0:7.3.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:bpftool-debuginfo-0:7.3.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:bpftool-debuginfo-0:7.3.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:bpftool-debuginfo-0:7.3.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:bpftool-debuginfo-0:7.3.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-0:5.14.0-427.31.1.el9_4.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-64k-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-64k-core-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-64k-debug-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-64k-debug-core-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-64k-debug-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-64k-debug-modules-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-64k-debug-modules-core-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-64k-debug-modules-extra-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-64k-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-64k-modules-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-64k-modules-core-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-64k-modules-extra-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-abi-stablelists-0:5.14.0-427.31.1.el9_4.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-core-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-core-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-core-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-core-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-core-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-core-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-core-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-core-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-modules-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-modules-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-modules-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-modules-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-modules-core-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-modules-core-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-modules-core-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-modules-core-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-modules-extra-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-modules-extra-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-modules-extra-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-modules-extra-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debug-uki-virt-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debuginfo-common-aarch64-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debuginfo-common-ppc64le-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debuginfo-common-s390x-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-debuginfo-common-x86_64-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-modules-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-modules-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-modules-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-modules-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-modules-core-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-modules-core-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-modules-core-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-modules-core-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-modules-extra-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-modules-extra-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-modules-extra-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-modules-extra-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-rt-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-rt-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-tools-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-tools-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-tools-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-tools-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-tools-libs-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-tools-libs-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-tools-libs-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-uki-virt-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-zfcpdump-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-zfcpdump-core-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-zfcpdump-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-zfcpdump-modules-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-zfcpdump-modules-core-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:kernel-zfcpdump-modules-extra-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:libperf-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:libperf-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:libperf-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:libperf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:perf-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:perf-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:perf-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:perf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:python3-perf-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:python3-perf-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:python3-perf-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:python3-perf-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:python3-perf-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:python3-perf-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:python3-perf-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.MAIN.EUS:python3-perf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:bpftool-debuginfo-0:7.3.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:bpftool-debuginfo-0:7.3.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:bpftool-debuginfo-0:7.3.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:bpftool-debuginfo-0:7.3.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-64k-debug-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-64k-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-debuginfo-common-aarch64-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-debuginfo-common-ppc64le-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-debuginfo-common-s390x-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-debuginfo-common-x86_64-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-rt-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-rt-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-tools-libs-devel-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-tools-libs-devel-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-tools-libs-devel-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-zfcpdump-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:libperf-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:libperf-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:libperf-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:libperf-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:libperf-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:libperf-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:libperf-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:libperf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:perf-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:perf-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:perf-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:perf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:python3-perf-debuginfo-0:5.14.0-427.31.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:python3-perf-debuginfo-0:5.14.0-427.31.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:python3-perf-debuginfo-0:5.14.0-427.31.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:python3-perf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:bpftool-debuginfo-0:7.3.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-debuginfo-common-x86_64-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-core-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-debug-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-debug-core-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-debug-devel-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-debug-kvm-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-debug-modules-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-debug-modules-core-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-debug-modules-extra-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-devel-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-kvm-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-modules-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-modules-core-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-rt-modules-extra-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:libperf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:perf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.MAIN.EUS:python3-perf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:bpftool-debuginfo-0:7.3.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-debuginfo-common-x86_64-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-rt-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-rt-core-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-rt-debug-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-rt-debug-core-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-rt-debug-devel-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-rt-debug-modules-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-rt-debug-modules-core-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-rt-debug-modules-extra-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-rt-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-rt-devel-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-rt-modules-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-rt-modules-core-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-rt-modules-extra-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:libperf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:perf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.MAIN.EUS:python3-perf-debuginfo-0:5.14.0-427.31.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-headers-0:5.14.0-427.31.1.el9_4.aarch64 | — | ||
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-headers-0:5.14.0-427.31.1.el9_4.ppc64le | — | ||
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-headers-0:5.14.0-427.31.1.el9_4.s390x | — | ||
| Unresolved product id: AppStream-9.4.0.Z.MAIN.EUS:kernel-headers-0:5.14.0-427.31.1.el9_4.x86_64 | — | ||
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-cross-headers-0:5.14.0-427.31.1.el9_4.aarch64 | — | ||
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-cross-headers-0:5.14.0-427.31.1.el9_4.ppc64le | — | ||
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-cross-headers-0:5.14.0-427.31.1.el9_4.s390x | — | ||
| Unresolved product id: CRB-9.4.0.Z.MAIN.EUS:kernel-cross-headers-0:5.14.0-427.31.1.el9_4.x86_64 | — |
A potential NULL pointer dereference flaw was found in ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev() in the Linux kernel. This issue may lead to a crash.
In the Linux kernel, the following vulnerability has been resolved: ipvlan: add ipvlan_route_v6_outbound() helper Inspired by syzbot reports using a stack of multiple ipvlan devices. Reduce stack size needed in ipvlan_process_v6_outbound() by moving the flowi6 struct used for the route lookup in an non inlined helper. ipvlan_route_v6_outbound() needs 120 bytes on the stack, immediately reclaimed. Also make sure ipvlan_process_v4_outbound() is not inlined. We might also have to lower MAX_NEST_DEV, because only syzbot uses setups with more than four stacked devices. BUG: TASK stack guard page was hit at ffffc9000e803ff8 (stack is ffffc9000e804000..ffffc9000e808000) stack guard page: 0000 [#1] SMP KASAN CPU: 0 PID: 13442 Comm: syz-executor.4 Not tainted 6.1.52-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023 RIP: 0010:kasan_check_range+0x4/0x2a0 mm/kasan/generic.c:188 Code: 48 01 c6 48 89 c7 e8 db 4e c1 03 31 c0 5d c3 cc 0f 0b eb 02 0f 0b b8 ea ff ff ff 5d c3 cc 00 00 cc cc 00 00 cc cc 55 48 89 e5 <41> 57 41 56 41 55 41 54 53 b0 01 48 85 f6 0f 84 a4 01 00 00 48 89 RSP: 0018:ffffc9000e804000 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff817e5bf2 RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff887c6568 RBP: ffffc9000e804000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92001d0080c R13: dffffc0000000000 R14: ffffffff87e6b100 R15: 0000000000000000 FS: 00007fd0c55826c0(0000) GS:ffff8881f6800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffc9000e803ff8 CR3: 0000000170ef7000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <#DF> </#DF> <TASK> [<ffffffff81f281d1>] __kasan_check_read+0x11/0x20 mm/kasan/shadow.c:31 [<ffffffff817e5bf2>] instrument_atomic_read include/linux/instrumented.h:72 [inline] [<ffffffff817e5bf2>] _test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline] [<ffffffff817e5bf2>] cpumask_test_cpu include/linux/cpumask.h:506 [inline] [<ffffffff817e5bf2>] cpu_online include/linux/cpumask.h:1092 [inline] [<ffffffff817e5bf2>] trace_lock_acquire include/trace/events/lock.h:24 [inline] [<ffffffff817e5bf2>] lock_acquire+0xe2/0x590 kernel/locking/lockdep.c:5632 [<ffffffff8563221e>] rcu_lock_acquire+0x2e/0x40 include/linux/rcupdate.h:306 [<ffffffff8561464d>] rcu_read_lock include/linux/rcupdate.h:747 [inline] [<ffffffff8561464d>] ip6_pol_route+0x15d/0x1440 net/ipv6/route.c:2221 [<ffffffff85618120>] ip6_pol_route_output+0x50/0x80 net/ipv6/route.c:2606 [<ffffffff856f65b5>] pol_lookup_func include/net/ip6_fib.h:584 [inline] [<ffffffff856f65b5>] fib6_rule_lookup+0x265/0x620 net/ipv6/fib6_rules.c:116 [<ffffffff85618009>] ip6_route_output_flags_noref+0x2d9/0x3a0 net/ipv6/route.c:2638 [<ffffffff8561821a>] ip6_route_output_flags+0xca/0x340 net/ipv6/route.c:2651 [<ffffffff838bd5a3>] ip6_route_output include/net/ip6_route.h:100 [inline] [<ffffffff838bd5a3>] ipvlan_process_v6_outbound drivers/net/ipvlan/ipvlan_core.c:473 [inline] [<ffffffff838bd5a3>] ipvlan_process_outbound drivers/net/ipvlan/ipvlan_core.c:529 [inline] [<ffffffff838bd5a3>] ipvlan_xmit_mode_l3 drivers/net/ipvlan/ipvlan_core.c:602 [inline] [<ffffffff838bd5a3>] ipvlan_queue_xmit+0xc33/0x1be0 drivers/net/ipvlan/ipvlan_core.c:677 [<ffffffff838c2909>] ipvlan_start_xmit+0x49/0x100 drivers/net/ipvlan/ipvlan_main.c:229 [<ffffffff84d03900>] netdev_start_xmit include/linux/netdevice.h:4966 [inline] [<ffffffff84d03900>] xmit_one net/core/dev.c:3644 [inline] [<ffffffff84d03900>] dev_hard_start_xmit+0x320/0x980 net/core/dev.c:3660 [<ffffffff84d080e2>] __dev_queue_xmit+0x16b2/0x3370 net/core/dev.c:4324 [<ffffffff855ce4cd>] dev_queue_xmit include/linux/netdevice.h:3067 [inline] [<ffffffff855ce4cd>] neigh_hh_output include/net/neighbour.h:529 [inline] [<f ---truncated---
In the Linux kernel, the following vulnerability has been resolved: platform/x86: wmi: Fix opening of char device Since commit fa1f68db6ca7 ("drivers: misc: pass miscdevice pointer via file private data"), the miscdevice stores a pointer to itself inside filp->private_data, which means that private_data will not be NULL when wmi_char_open() is called. This might cause memory corruption should wmi_char_open() be unable to find its driver, something which can happen when the associated WMI device is deleted in wmi_free_devices(). Fix the problem by using the miscdevice pointer to retrieve the WMI device data associated with a char device using container_of(). This also avoids wmi_char_open() picking a wrong WMI device bound to a driver with the same name as the original driver.
Hardware logic with insecure de-synchronization in Intel(R) DSA and Intel(R) IAA for some Intel(R) 4th or 5th generation Xeon(R) processors may allow an authorized user to potentially enable escalation of privilege local access
A NULL pointer dereference flaw was found in the Linux kernel in the phy-omap-usb2 driver. This issue arises when the external PHY used with phy-omap-usb2 does not implement the send_srp() function. If this function is called without proper implementation, it can result in a system crash, especially during operations like waking up an idle Ethernet gadget.
A vulnerability was found in the Linux kernel's netfilter subsystem, related to the nft_chain_filter feature. This issue occurs when a NETDEV_UNREGISTER event is reported, which can leave a stale reference to a network device in the ingress basechain. If this issue is not addressed, this stale reference could result in lingering issues with network device handling.
In the Linux kernel, the following vulnerability has been resolved: cifs: fix underflow in parse_server_interfaces() In this loop, we step through the buffer and after each item we check if the size_left is greater than the minimum size we need. However, the problem is that "bytes_left" is type ssize_t while sizeof() is type size_t. That means that because of type promotion, the comparison is done as an unsigned and if we have negative bytes left the loop continues instead of ending.
A memory corruption flaw was found in the Linux kernel’s Intel(R) Ethernet Controller I225-LM/I225-V driver in how a user generates a high amount of packets. This flaw allows a local user to crash the system.
A vulnerability was found in the ff_layout_cancel_io() function in the Linux kernel. Improper error checking with the mirror_ds structure fails to check if it is NULL, leading to a potential NULL pointer dereference. This issue could lead to crashes.
A flaw was found in the Linux kernel. This vulnerability affects the ath9k wireless driver in the Linux kernel, specifically used with ath9k_htc devices. The issue arises from a race condition where certain initialization processes are incomplete when the system begins handling WiFi-related events. The problem occurs because the device is exposed to the USB subsystem before the ath9k driver finishes initializing critical data structures. This can lead to NULL pointer dereferences, which cause system crashes, particularly when running specific commands or handling events during WiFi operations. A partial fix had been applied earlier to prevent one aspect of this issue, but further problems were identified. The final resolution was to delay all event handling in the ath9k_wmi_event_tasklet() function until initialization is fully complete, ensuring stability.
A use-after-free flaw was found in free_irq() in the Linux kernel.
A vulnerability was found in the Linux kernel's net rtl8xxxu_core.c driver, where a race condition can lead to a use-after-free situation in the rtl8xxxu_stop() function. This occurs when the workqueue is still running but the driver has been stopped and can lead to c2hcmd_work attempting to access memory that has been freed. This issue can lead to memory corruption or crashes.
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: do not compare internal table flags on updates Restore skipping transaction if table update does not modify flags.
A flaw was discovered in the Linux kernel's IPv6 implementation, specifically within the inet6_rtm_getaddr() function. The issue arises when user space provides a valid IFA_TARGET_NETNSID value but omits the IFA_ADDRESS and IFA_LOCAL attributes. In such cases, the function returns an -EINVAL error while inadvertently increasing the reference count of the struct net object, leading to a potential memory leak. This flaw has been addressed by ensuring that the reference count is properly managed, preventing unintended resource retention. Users are advised to update their Linux kernel to a version that includes this fix to maintain system stability and prevent resource leaks.
CVE-2024-27434 is a flaw in the Linux kernel’s iwlwifi driver related to handling Management Frame Protection (MFP) in certain Wi-Fi configurations. When connecting to an access point using TKIP as the group cipher, the driver incorrectly applies the MFP flag to the Group Temporal Key (GTK), which is not supported in this context. This can result in firmware crashes and instability. The issue has been fixed by ensuring the driver does not set the MFP flag for incompatible group ciphers like TKIP. Updating to a patched kernel version is recommended to resolve this vulnerability.
In the Linux kernel, the following vulnerability has been resolved: ipvlan: Dont Use skb->sk in ipvlan_process_v{4,6}_outbound Raw packet from PF_PACKET socket ontop of an IPv6-backed ipvlan device will hit WARN_ON_ONCE() in sk_mc_loop() through sch_direct_xmit() path. WARNING: CPU: 2 PID: 0 at net/core/sock.c:775 sk_mc_loop+0x2d/0x70 Modules linked in: sch_netem ipvlan rfkill cirrus drm_shmem_helper sg drm_kms_helper CPU: 2 PID: 0 Comm: swapper/2 Kdump: loaded Not tainted 6.9.0+ #279 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:sk_mc_loop+0x2d/0x70 Code: fa 0f 1f 44 00 00 65 0f b7 15 f7 96 a3 4f 31 c0 66 85 d2 75 26 48 85 ff 74 1c RSP: 0018:ffffa9584015cd78 EFLAGS: 00010212 RAX: 0000000000000011 RBX: ffff91e585793e00 RCX: 0000000002c6a001 RDX: 0000000000000000 RSI: 0000000000000040 RDI: ffff91e589c0f000 RBP: ffff91e5855bd100 R08: 0000000000000000 R09: 3d00545216f43d00 R10: ffff91e584fdcc50 R11: 00000060dd8616f4 R12: ffff91e58132d000 R13: ffff91e584fdcc68 R14: ffff91e5869ce800 R15: ffff91e589c0f000 FS: 0000000000000000(0000) GS:ffff91e898100000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f788f7c44c0 CR3: 0000000008e1a000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <IRQ> ? __warn (kernel/panic.c:693) ? sk_mc_loop (net/core/sock.c:760) ? report_bug (lib/bug.c:201 lib/bug.c:219) ? handle_bug (arch/x86/kernel/traps.c:239) ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) ? asm_exc_invalid_op (./arch/x86/include/asm/idtentry.h:621) ? sk_mc_loop (net/core/sock.c:760) ip6_finish_output2 (net/ipv6/ip6_output.c:83 (discriminator 1)) ? nf_hook_slow (net/netfilter/core.c:626) ip6_finish_output (net/ipv6/ip6_output.c:222) ? __pfx_ip6_finish_output (net/ipv6/ip6_output.c:215) ipvlan_xmit_mode_l3 (drivers/net/ipvlan/ipvlan_core.c:602) ipvlan ipvlan_start_xmit (drivers/net/ipvlan/ipvlan_main.c:226) ipvlan dev_hard_start_xmit (net/core/dev.c:3594) sch_direct_xmit (net/sched/sch_generic.c:343) __qdisc_run (net/sched/sch_generic.c:416) net_tx_action (net/core/dev.c:5286) handle_softirqs (kernel/softirq.c:555) __irq_exit_rcu (kernel/softirq.c:589) sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1043) The warning triggers as this: packet_sendmsg packet_snd //skb->sk is packet sk __dev_queue_xmit __dev_xmit_skb //q->enqueue is not NULL __qdisc_run sch_direct_xmit dev_hard_start_xmit ipvlan_start_xmit ipvlan_xmit_mode_l3 //l3 mode ipvlan_process_outbound //vepa flag ipvlan_process_v6_outbound ip6_local_out __ip6_finish_output ip6_finish_output2 //multicast packet sk_mc_loop //sk->sk_family is AF_PACKET Call ip{6}_local_out() with NULL sk in ipvlan as other tunnels to fix this.
CWE-20 - Improper Input ValidationCVE-2024-35789 is a vulnerability in the Linux kernel’s Wi-Fi subsystem (mac80211). It occurs when a station is moved out of a VLAN, and the VLAN is subsequently deleted. A reference to the deleted VLAN’s network device may remain, leading to a use-after-free condition. This can result in system instability or crashes. The issue has been resolved by ensuring that outdated references are cleared when a station changes VLANs.
In the Linux kernel, the following vulnerability has been resolved: efi: fix panic in kdump kernel The Linux kernel CVE team has assigned CVE-2024-35800 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024051738-CVE-2024-35800-219a@gregkh/T
A vulnerability as found in the Linux kernel’s virtual terminal (VT) subsystem, which could lead to unicode buffer corruption when deleting characters. This issue arises from improper handling of unicode data, which can corrupt memory or lead to unintended behavior.
In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: dbg-tlv: ensure NUL termination The Linux kernel CVE team has assigned CVE-2024-35845 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024051718-CVE-2024-35845-65bd@gregkh/T
CVE-2024-35848 is a vulnerability in the Linux kernel's EEPROM driver (at24) that can lead to memory corruption. The issue arises when an EEPROM device is inaccessible: the system registers an nvmem device, the read operation fails, and the device is subsequently torn down. If another driver attempts to access the nvmem device after this teardown, it may reference invalid memory, causing potential system instability. The problem has been resolved by adjusting the failure handling to occur before the nvmem device is registered, preventing access to invalid memory. Users should update their Linux kernel to a version that includes this fix to ensure system reliability.
CVE-2024-35852 addresses a memory leak in the Linux kernel's mlxsw driver, specifically within the Spectrum ACL TCAM module. The issue occurs when rehash work is canceled while pending, leading to allocated hints not being freed properly. This results in a memory leak that can degrade system performance over time. The problem has been resolved by ensuring that any associated hints are freed when the rehash work is canceled. Users should update their Linux kernel to a version that includes this fix to maintain optimal system performance.
A vulnerability was found in the Linux kernel's Netfilter framework, specifically within the nf_tables component. The issue arises from a race condition between the exit_net function and the destroy work queue, which can lead to use-after-free errors and potential system instability. This vulnerability has been addressed by making sure that any pending destroy work is flushed before releasing network namespaces, thereby preventing the race condition. Users are advised to update their Linux kernel to a version that includes this fix to maintain system stability and security.
This is a flaw in the Linux kernel's ICE driver for Intel Ethernet controllers. The problem arises when the system enters a suspended state, and the driver frees queue vectors without resetting the num_q_vectors variable. This oversight causes the ice_rebuild() function to allocate an incorrectly sized buffer, leading to memory corruption and potential system crashes. During suspension, the driver fails to restore the num_q_vectors value after freeing queue vectors, resulting in invalid memory operations during system rebuilds. Kernel crashes or instability can occur, especially when resuming from suspension, due to buffer mismanagement.
In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: check A-MSDU format more carefully If it looks like there's another subframe in the A-MSDU but the header isn't fully there, we can end up reading data out of bounds, only to discard later. Make this a bit more careful and check if the subframe header can even be present.
This CVE addresses a race condition in the Linux kernel's IPv6 subsystem, specifically between the ipv6_get_ifaddr and ipv6_del_addr functions. This race condition can lead to use-after-free scenarios, potentially causing system instability or crashes.
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: honor table dormant flag from netdev release event path The Linux kernel CVE team has assigned CVE-2024-36005 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024052024-CVE-2024-36005-2336@gregkh/T
In the Linux kernel, the following vulnerability has been resolved: rtnetlink: Correct nested IFLA_VF_VLAN_LIST attribute validation Each attribute inside a nested IFLA_VF_VLAN_LIST is assumed to be a struct ifla_vf_vlan_info so the size of such attribute needs to be at least of sizeof(struct ifla_vf_vlan_info) which is 14 bytes. The current size validation in do_setvfinfo is against NLA_HDRLEN (4 bytes) which is less than sizeof(struct ifla_vf_vlan_info) so this validation is not enough and a too small attribute might be cast to a struct ifla_vf_vlan_info, this might result in an out of bands read access when accessing the saved (casted) entry in ivvl.
A flaw was found in the Linux kernel’s Ethernet Controller XL710 family driver. This flaw allows a local user to crash the system.
In the Linux kernel, the following vulnerability has been resolved: tls: fix missing memory barrier in tls_init In tls_init(), a write memory barrier is missing, and store-store reordering may cause NULL dereference in tls_{setsockopt,getsockopt}. CPU0 CPU1 ----- ----- // In tls_init() // In tls_ctx_create() ctx = kzalloc() ctx->sk_proto = READ_ONCE(sk->sk_prot) -(1) // In update_sk_prot() WRITE_ONCE(sk->sk_prot, tls_prots) -(2) // In sock_common_setsockopt() READ_ONCE(sk->sk_prot)->setsockopt() // In tls_{setsockopt,getsockopt}() ctx->sk_proto->setsockopt() -(3) In the above scenario, when (1) and (2) are reordered, (3) can observe the NULL value of ctx->sk_proto, causing NULL dereference. To fix it, we rely on rcu_assign_pointer() which implies the release barrier semantic. By moving rcu_assign_pointer() after ctx->sk_proto is initialized, we can ensure that ctx->sk_proto are visible when changing sk->sk_prot.
In the Linux kernel, the following vulnerability has been resolved: ipv6: Fix potential uninit-value access in __ip6_make_skb() As it was done in commit fc1092f51567 ("ipv4: Fix uninit-value access in __ip_make_skb()") for IPv4, check FLOWI_FLAG_KNOWN_NH on fl6->flowi6_flags instead of testing HDRINCL on the socket to avoid a race condition which causes uninit-value access.
An out-of-bounds memory access flaw was found in the Linux kernel’s Wireless WiFi Link Next-Gen AGN driver in how a user removes it. This flaw allows a local user to crash or potentially escalate their privileges on the system.
In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: read txq->read_ptr under lock If we read txq->read_ptr without lock, we can read the same value twice, then obtain the lock, and reclaim from there to two different places, but crucially reclaim the same entry twice, resulting in the WARN_ONCE() a little later. Fix that by reading txq->read_ptr under lock.
In the Linux kernel, the following vulnerability has been resolved: net: core: reject skb_copy(_expand) for fraglist GSO skbs SKB_GSO_FRAGLIST skbs must not be linearized, otherwise they become invalid. Return NULL if such an skb is passed to skb_copy or skb_copy_expand, in order to prevent a crash on a potential later call to skb_gso_segment.
A possible NULL pointer dereference was observed in the Linux kernel, in net/wireless/nl80211.c. This may lead to a crash.
A use-after-free flaw was found in the Linux kernel's network route management. This flaw allows an attacker to alter the behavior of certain network connections.
No description is available for this CVE.
CWE-415 - Double FreeA security vulnerability has been identified in the TCP networking implementation of the Linux kernel. Specifically, the dctcp_update_alpha() function is susceptible to a shift-out-of-bounds condition. This flaw could potentially be exploited to cause unexpected behavior or a denial-of-service.
No description is available for this CVE.
CWE-402 - Transmission of Private Resources into a New Sphere ('Resource Leak')In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix overwriting ct original tuple for ICMPv6 OVS_PACKET_CMD_EXECUTE has 3 main attributes: - OVS_PACKET_ATTR_KEY - Packet metadata in a netlink format. - OVS_PACKET_ATTR_PACKET - Binary packet content. - OVS_PACKET_ATTR_ACTIONS - Actions to execute on the packet. OVS_PACKET_ATTR_KEY is parsed first to populate sw_flow_key structure with the metadata like conntrack state, input port, recirculation id, etc. Then the packet itself gets parsed to populate the rest of the keys from the packet headers. Whenever the packet parsing code starts parsing the ICMPv6 header, it first zeroes out fields in the key corresponding to Neighbor Discovery information even if it is not an ND packet. It is an 'ipv6.nd' field. However, the 'ipv6' is a union that shares the space between 'nd' and 'ct_orig' that holds the original tuple conntrack metadata parsed from the OVS_PACKET_ATTR_KEY. ND packets should not normally have conntrack state, so it's fine to share the space, but normal ICMPv6 Echo packets or maybe other types of ICMPv6 can have the state attached and it should not be overwritten. The issue results in all but the last 4 bytes of the destination address being wiped from the original conntrack tuple leading to incorrect packet matching and potentially executing wrong actions in case this packet recirculates within the datapath or goes back to userspace. ND fields should not be accessed in non-ND packets, so not clearing them should be fine. Executing memset() only for actual ND packets to avoid the issue. Initializing the whole thing before parsing is needed because ND packet may not contain all the options. The issue only affects the OVS_PACKET_CMD_EXECUTE path and doesn't affect packets entering OVS datapath from network interfaces, because in this case CT metadata is populated from skb after the packet is already parsed.
in linux kernel wifi, the kzalloc() in brcmf_pcie_download_fw_nvram() will return null if the physical memory has run out. Thereafter if get_random_bytes() is used, a null pointer dereference is triggered, causing allocation failure.
In the Linux kernel, the following vulnerability has been resolved: bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() In function bond_option_arp_ip_targets_set(), if newval->string is an empty string, newval->string+1 will point to the byte after the string, causing an out-of-bound read. BUG: KASAN: slab-out-of-bounds in strlen+0x7d/0xa0 lib/string.c:418 Read of size 1 at addr ffff8881119c4781 by task syz-executor665/8107 CPU: 1 PID: 8107 Comm: syz-executor665 Not tainted 6.7.0-rc7 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:364 [inline] print_report+0xc1/0x5e0 mm/kasan/report.c:475 kasan_report+0xbe/0xf0 mm/kasan/report.c:588 strlen+0x7d/0xa0 lib/string.c:418 __fortify_strlen include/linux/fortify-string.h:210 [inline] in4_pton+0xa3/0x3f0 net/core/utils.c:130 bond_option_arp_ip_targets_set+0xc2/0x910 drivers/net/bonding/bond_options.c:1201 __bond_opt_set+0x2a4/0x1030 drivers/net/bonding/bond_options.c:767 __bond_opt_set_notify+0x48/0x150 drivers/net/bonding/bond_options.c:792 bond_opt_tryset_rtnl+0xda/0x160 drivers/net/bonding/bond_options.c:817 bonding_sysfs_store_option+0xa1/0x120 drivers/net/bonding/bond_sysfs.c:156 dev_attr_store+0x54/0x80 drivers/base/core.c:2366 sysfs_kf_write+0x114/0x170 fs/sysfs/file.c:136 kernfs_fop_write_iter+0x337/0x500 fs/kernfs/file.c:334 call_write_iter include/linux/fs.h:2020 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x96a/0xd80 fs/read_write.c:584 ksys_write+0x122/0x250 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b ---[ end trace ]--- Fix it by adding a check of string length before using it.
A vulnerability was found in the Linux kernel's ethtool implementation in the ethtool_get_phy_stats_ethtool() function, where the issue arises when a null function pointer is dereferenced if the 'ops->get_ethtool_phy_stats' is NULL, potentially leading to a crash.
A vulnerability was found in the Linux kernel's networking component in the __sock_release() function, where a dangling pointer can occur when socket creation fails. This happens when a reference to the socket is not cleared, leading to a use-after-free condition.
A vulnerability was found in the Linux kernel's netns in the get_net_ns() function. This vulnerability occurs when a network namespace reference count is zero, leading to a use-after-free condition that can trigger a kernel panic.
A vulnerability was found in the Linux kernel's IPv6 routing component, where a NULL dereference occurs in the fib6_nh_init() function, this issue arises when the function attempts to initialize a network interface without verifying its availability, potentially leading to a DoS.
Loading 4.1 MB of JSON…
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.