almalinux/kernel

Vulnerabilities (1,228)

• CVE-2024-26853Apr 17, 2024
  affected < 5.14.0-427.31.1.el9_4fixed 5.14.0-427.31.1.el9_4

  In the Linux kernel, the following vulnerability has been resolved: igc: avoid returning frame twice in XDP_REDIRECT When a frame can not be transmitted in XDP_REDIRECT (e.g. due to a full queue), it is necessary to free it by calling xdp_return_frame_rx_napi. However, this is

• CVE-2024-26846Apr 17, 2024
  affected < 4.18.0-553.22.1.el8_10fixed 4.18.0-553.22.1.el8_10

  In the Linux kernel, the following vulnerability has been resolved: nvme-fc: do not wait in vain when unloading module The module exit path has race between deleting all controllers and freeing 'left over IDs'. To prevent double free a synchronization between nvme_delete_ctrl a

• CVE-2024-26843Apr 17, 2024
  affected < 4.18.0-553.16.1.el8_10fixed 4.18.0-553.16.1.el8_10

  In the Linux kernel, the following vulnerability has been resolved: efi: runtime: Fix potential overflow of soft-reserved region size md_size will have been narrowed if we have >= 4GB worth of pages in a soft-reserved region.

• CVE-2024-26828Apr 17, 2024
  affected < 5.14.0-427.31.1.el9_4fixed 5.14.0-427.31.1.el9_4

  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 "b

• CVE-2024-26826Apr 17, 2024
  affected < 4.18.0-553.8.1.el8_10fixed 4.18.0-553.8.1.el8_10

  In the Linux kernel, the following vulnerability has been resolved: mptcp: fix data re-injection from stale subflow When the MPTCP PM detects that a subflow is stale, all the packet scheduler must re-inject all the mptcp-level unacked data. To avoid acquiring unneeded locks, it

• CVE-2021-47185Apr 10, 2024
  affected < 4.18.0-553.5.1.el8_10fixed 4.18.0-553.5.1.el8_10

  In the Linux kernel, the following vulnerability has been resolved: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc When running ltp testcase(ltp/testcases/kernel/pty/pty04.c) with arm64, there is a soft lockup, which look like this one: Workqueue: events_unbound

• CVE-2024-26810MedApr 5, 2024
  affected < 5.14.0-427.33.1.el9_4fixed 5.14.0-427.33.1.el9_4

  In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Lock external INTx masking ops Mask operations through config space changes to DisINTx may race INTx configuration changes via ioctl. Create wrappers that add locking for paths outside of the core in

• CVE-2024-26808Apr 4, 2024
  affected < 5.14.0-427.31.1.el9_4fixed 5.14.0-427.31.1.el9_4

  In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain Remove netdevice from inet/ingress basechain in case NETDEV_UNREGISTER event is reported, otherwise a stale reference to netdevic

• CVE-2024-26804Apr 4, 2024
  affected < 5.14.0-427.18.1.el9_4fixed 5.14.0-427.18.1.el9_4

  In the Linux kernel, the following vulnerability has been resolved: net: ip_tunnel: prevent perpetual headroom growth syzkaller triggered following kasan splat: BUG: KASAN: use-after-free in __skb_flow_dissect+0x19d1/0x7a50 net/core/flow_dissector.c:1170 Read of size 1 at addr

• CVE-2024-26802Apr 4, 2024
  affected < 4.18.0-553.16.1.el8_10fixed 4.18.0-553.16.1.el8_10

  In the Linux kernel, the following vulnerability has been resolved: stmmac: Clear variable when destroying workqueue Currently when suspending driver and stopping workqueue it is checked whether workqueue is not NULL and if so, it is destroyed. Function destroy_workqueue() does

• CVE-2024-26801Apr 4, 2024
  affected < 5.14.0-427.24.1.el9_4fixed 5.14.0-427.24.1.el9_4

  In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Avoid potential use-after-free in hci_error_reset While handling the HCI_EV_HARDWARE_ERROR event, if the underlying BT controller is not responding, the GPIO reset mechanism would free the hci_dev an

• CVE-2024-26783Apr 4, 2024
  affected < 5.14.0-427.26.1.el9_4fixed 5.14.0-427.26.1.el9_4

  In the Linux kernel, the following vulnerability has been resolved: mm/vmscan: fix a bug calling wakeup_kswapd() with a wrong zone index With numa balancing on, when a numa system is running where a numa node doesn't have its local memory so it has no managed zones, the followi

• CVE-2024-26779Apr 3, 2024
  affected < 4.18.0-553.5.1.el8_10fixed 4.18.0-553.5.1.el8_10

  In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix race condition on enabling fast-xmit fast-xmit must only be enabled after the sta has been uploaded to the driver, otherwise it could end up passing the not-yet-uploaded sta via drv_tx calls

• CVE-2024-26773Apr 3, 2024
  affected < 5.14.0-427.28.1.el9_4fixed 5.14.0-427.28.1.el9_4

  In the Linux kernel, the following vulnerability has been resolved: ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found() Determine if the group block bitmap is corrupted before using ac_b_ex in ext4_mb_try_best_found() to avoid allocating blocks from a

• CVE-2024-26769Apr 3, 2024
  affected < 4.18.0-553.22.1.el8_10fixed 4.18.0-553.22.1.el8_10

  In the Linux kernel, the following vulnerability has been resolved: nvmet-fc: avoid deadlock on delete association path When deleting an association the shutdown path is deadlocking because we try to flush the nvmet_wq nested. Avoid this by deadlock by deferring the put work in

• CVE-2024-26766Apr 3, 2024
  affected < 4.18.0-553.100.1.el8_10fixed 4.18.0-553.100.1.el8_10

  In the Linux kernel, the following vulnerability has been resolved: IB/hfi1: Fix sdma.h tx->num_descs off-by-one error Unfortunately the commit `fd8958efe877` introduced another error causing the `descs` array to overflow. This reults in further crashes easily reproducible by `

• CVE-2024-26759Apr 3, 2024
  affected < 4.18.0-553.8.1.el8_10fixed 4.18.0-553.8.1.el8_10

  In the Linux kernel, the following vulnerability has been resolved: mm/swap: fix race when skipping swapcache When skipping swapcache for SWP_SYNCHRONOUS_IO, if two or more threads swapin the same entry at the same time, they get different pages (A, B). Before one thread (T0)

• CVE-2024-26744Apr 3, 2024
  affected < 4.18.0-553.5.1.el8_10fixed 4.18.0-553.5.1.el8_10

  In the Linux kernel, the following vulnerability has been resolved: RDMA/srpt: Support specifying the srpt_service_guid parameter Make loading ib_srpt with this parameter set work. The current behavior is that setting that parameter while loading the ib_srpt kernel module trigg

• CVE-2024-26743Apr 3, 2024
  affected < 4.18.0-553.5.1.el8_10fixed 4.18.0-553.5.1.el8_10

  In the Linux kernel, the following vulnerability has been resolved: RDMA/qedr: Fix qedr_create_user_qp error flow Avoid the following warning by making sure to free the allocated resources in case that qedr_init_user_queue() fail. -----------[ cut here ]----------- WARNING: CP

• CVE-2024-26739Apr 3, 2024
  affected < 5.14.0-427.37.1.el9_4fixed 5.14.0-427.37.1.el9_4

  In the Linux kernel, the following vulnerability has been resolved: net/sched: act_mirred: don't override retval if we already lost the skb If we're redirecting the skb, and haven't called tcf_mirred_forward(), yet, we need to tell the core to drop the skb by setting the retcod