almalinux/kernel-uki-virt-addons

Vulnerabilities (400)

• CVE-2024-50223Nov 9, 2024
  affected < 5.14.0-503.19.1.el9_5fixed 5.14.0-503.19.1.el9_5

  In the Linux kernel, the following vulnerability has been resolved: sched/numa: Fix the potential null pointer dereference in task_numa_work() When running stress-ng-vm-segv test, we found a null pointer dereference error in task_numa_work(). Here is the backtrace: [323676.0

• CVE-2024-50208Nov 8, 2024
  affected < 5.14.0-503.21.1.el9_5fixed 5.14.0-503.21.1.el9_5

  In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages Avoid memory corruption while setting up Level-2 PBL pages for the non MR resources when num_pages > 256K. There will be a single PDE page address (co

• CVE-2024-50195Nov 8, 2024
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: posix-clock: Fix missing timespec64 check in pc_clock_settime() As Andrew pointed out, it will make sense that the PTP core checked timespec64 struct's tv_sec and tv_nsec range before calling ptp->info->settime

• CVE-2024-50192Nov 8, 2024
  affected < 5.14.0-503.19.1.el9_5fixed 5.14.0-503.19.1.el9_5

  In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v4: Don't allow a VMOVP on a dying VPE Kunkun Jiang reported that there is a small window of opportunity for userspace to force a change of affinity for a VPE while the VPE has already been unmapped

• CVE-2024-50148MedNov 7, 2024
  affected < 5.14.0-503.19.1.el9_5fixed 5.14.0-503.19.1.el9_5

  In the Linux kernel, the following vulnerability has been resolved: Bluetooth: bnep: fix wild-memory-access in proto_unregister There's issue as follows: KASAN: maybe wild-memory-access in range [0xdead...108-0xdead...10f] CPU: 3 UID: 0 PID: 2805 Comm: rmmod Tainted: G

• CVE-2024-50142MedNov 7, 2024
  affected < 5.14.0-503.19.1.el9_5fixed 5.14.0-503.19.1.el9_5

  In the Linux kernel, the following vulnerability has been resolved: xfrm: validate new SA's prefixlen using SA family when sel.family is unset This expands the validation introduced in commit 07bf7908950a ("xfrm: Validate address prefix lengths in the xfrm selector.") syzbot c

• CVE-2024-50154Nov 7, 2024
  affected < 5.14.0-503.22.1.el9_5fixed 5.14.0-503.22.1.el9_5

  In the Linux kernel, the following vulnerability has been resolved: tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). Martin KaFai Lau reported use-after-free [0] in reqsk_timer_handler(). """ We are seeing a use-after-free from a bpf prog attached to trace_tc

• CVE-2024-50125Nov 5, 2024
  affected < 5.14.0-503.19.1.el9_5fixed 5.14.0-503.19.1.el9_5

  In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: Fix UAF on sco_sock_timeout conn->sk maybe have been unlinked/freed while waiting for sco_conn_lock so this checks if the conn->sk is still valid by checking if it part of sco_sk_list.

• CVE-2024-50124Nov 5, 2024
  affected < 5.14.0-503.19.1.el9_5fixed 5.14.0-503.19.1.el9_5

  In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: Fix UAF on iso_sock_timeout conn->sk maybe have been unlinked/freed while waiting for iso_conn_lock so this checks if the conn->sk is still valid by checking if it part of iso_sk_list.

• CVE-2024-50115Nov 5, 2024
  affected < 5.14.0-503.19.1.el9_5fixed 5.14.0-503.19.1.el9_5

  In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory Ignore nCR3[4:0] when loading PDPTEs from memory for nested SVM, as bits 4:0 of CR3 are ignored when PAE paging is used, and thus VMRUN doesn't enforc

• CVE-2024-50110Nov 5, 2024
  affected < 5.14.0-503.19.1.el9_5fixed 5.14.0-503.19.1.el9_5

  In the Linux kernel, the following vulnerability has been resolved: xfrm: fix one more kernel-infoleak in algo dumping During fuzz testing, the following issue was discovered: BUG: KMSAN: kernel-infoleak in _copy_to_iter+0x598/0x2a30 _copy_to_iter+0x598/0x2a30 __skb_datagram

• CVE-2024-50099Nov 5, 2024
  affected < 5.14.0-503.19.1.el9_5fixed 5.14.0-503.19.1.el9_5

  In the Linux kernel, the following vulnerability has been resolved: arm64: probes: Remove broken LDR (literal) uprobe support The simulate_ldr_literal() and simulate_ldrsw_literal() functions are unsafe to use for uprobes. Both functions were originally written for use with kpr

• CVE-2022-49024Oct 21, 2024
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods In m_can_pci_remove() and error handling path of m_can_pci_probe(), m_can_class_free_dev() should be called to free resource allocated

• CVE-2024-50060Oct 21, 2024
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: io_uring: check if we need to reschedule during overflow flush In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it'll have a few entries. However,

• CVE-2024-49949MedOct 21, 2024
  affected < 5.14.0-503.16.1.el9_5fixed 5.14.0-503.16.1.el9_5

  In the Linux kernel, the following vulnerability has been resolved: net: avoid potential underflow in qdisc_pkt_len_init() with UFO After commit 7c6d2ecbda83 ("net: be more gentle about silly gso requests coming from user") virtio_net_hdr_to_skb() had sanity check to detect mal

• CVE-2024-49888Oct 21, 2024
  affected < 5.14.0-503.19.1.el9_5fixed 5.14.0-503.19.1.el9_5

  In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a sdiv overflow issue Zac Ecob reported a problem where a bpf program may cause kernel crash due to the following error: Oops: divide error: 0000 [#1] PREEMPT SMP KASAN PTI The failure is due to the

• CVE-2024-49864Oct 21, 2024
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix a race between socket set up and I/O thread creation In rxrpc_open_socket(), it sets up the socket and then sets up the I/O thread that will handle it. This is a problem, however, as there's a gap b

• CVE-2024-47727Oct 21, 2024
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: x86/tdx: Fix "in-kernel MMIO" check TDX only supports kernel-initiated MMIO operations. The handle_mmio() function checks if the #VE exception occurred in the kernel and rejects the operation if it did not. Ho

• CVE-2024-47679Oct 21, 2024
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: vfs: fix race between evice_inodes() and find_inode()&iput() Hi, all Recently I noticed a bug[1] in btrfs, after digged it into and I believe it'a race in vfs. Let's assume there's a inode (ie ino 261) with i

• CVE-2024-47675Oct 21, 2024
  affected < 5.14.0-503.19.1.el9_5fixed 5.14.0-503.19.1.el9_5

  In the Linux kernel, the following vulnerability has been resolved: bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() If bpf_link_prime() fails, bpf_uprobe_multi_link_attach() goes to the error_free label and frees the array of bpf_uprobe's without calling bpf_uprobe_un