almalinux/kernel-rt-debug-modules-extra

Vulnerabilities (1,061)

• CVE-2023-53494Oct 1, 2025
  affected < 5.14.0-570.60.1.el9_6fixed 5.14.0-570.60.1.el9_6

  In the Linux kernel, the following vulnerability has been resolved: crypto: xts - Handle EBUSY correctly As it is xts only handles the special return value of EINPROGRESS, which means that in all other cases it will free data related to the request. However, as the caller of x

• CVE-2025-39925Oct 1, 2025
  affected < 6.12.0-124.20.1.el10_1fixed 6.12.0-124.20.1.el10_1

  In the Linux kernel, the following vulnerability has been resolved: can: j1939: implement NETDEV_UNREGISTER notification handler syzbot is reporting unregister_netdevice: waiting for vcan0 to become free. Usage count = 2 problem, for j1939 protocol did not have NETDEV_UNREG

• CVE-2025-39918Oct 1, 2025
  affected < 6.12.0-124.16.1.el10_1fixed 6.12.0-124.16.1.el10_1

  In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: fix linked list corruption Never leave scheduled wcid entries on the temporary on-stack list

• CVE-2025-39905Oct 1, 2025
  affected < 6.12.0-124.27.1.el10_1fixed 6.12.0-124.27.1.el10_1

  In the Linux kernel, the following vulnerability has been resolved: net: phylink: add lock for serializing concurrent pl->phydev writes with resolver Currently phylink_resolve() protects itself against concurrent phylink_bringup_phy() or phylink_disconnect_phy() calls which mod

• CVE-2025-39883Sep 23, 2025
  affected < 4.18.0-553.87.1.rt7.428.el8_10fixed 4.18.0-553.87.1.rt7.428.el8_10

  In the Linux kernel, the following vulnerability has been resolved: mm/memory-failure: fix VM_BUG_ON_PAGE(PagePoisoned(page)) when unpoison memory When I did memory failure tests, below panic occurs: page dumped because: VM_BUG_ON_PAGE(PagePoisoned(page)) kernel BUG at include

• CVE-2025-39864HigSep 19, 2025
  affected < 4.18.0-553.82.1.rt7.423.el8_10fixed 4.18.0-553.82.1.rt7.423.el8_10

  In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: fix use-after-free in cmp_bss() Following bss_free() quirk introduced in commit 776b3580178f ("cfg80211: track hidden SSID networks properly"), adjust cfg80211_update_known_bss() to free the las

• CVE-2025-39849HigSep 19, 2025
  affected < 5.14.0-570.55.1.el9_6fixed 5.14.0-570.55.1.el9_6

  In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: sme: cap SSID length in __cfg80211_connect_result() If the ssid->datalen is more than IEEE80211_MAX_SSID_LEN (32) it would lead to memory corruption so add some bounds checking.

• CVE-2025-39843MedSep 19, 2025
  affected < 6.12.0-124.27.1.el10_1fixed 6.12.0-124.27.1.el10_1

  In the Linux kernel, the following vulnerability has been resolved: mm: slub: avoid wake up kswapd in set_track_prepare set_track_prepare() can incur lock recursion. The issue is that it is called from hrtimer_start_range_ns holding the per_cpu(hrtimer_bases)[n].lock, but when

• CVE-2025-39841HigSep 19, 2025
  affected < 5.14.0-570.55.1.el9_6fixed 5.14.0-570.55.1.el9_6

  In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix buffer free/clear order in deferred receive path Fix a use-after-free window by correcting the buffer release sequence in the deferred receive path. The code freed the RQ buffer first and only t

• CVE-2025-39840Sep 19, 2025
  affected < 5.14.0-611.20.1.el9_7fixed 5.14.0-611.20.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: audit: fix out-of-bounds read in audit_compare_dname_path() When a watch on dir=/ is combined with an fsnotify event for a single-character name directly under / (e.g., creating /a), an out-of-bounds read can o

• CVE-2023-53401Sep 18, 2025
  affected < 4.18.0-553.89.1.rt7.430.el8_10fixed 4.18.0-553.89.1.rt7.430.el8_10

  In the Linux kernel, the following vulnerability has been resolved: mm: kmem: fix a NULL pointer dereference in obj_stock_flush_required() KCSAN found an issue in obj_stock_flush_required(): stock->cached_objcg can be reset between the check and dereference: ==================

• CVE-2023-53386Sep 18, 2025
  affected < 4.18.0-553.81.1.rt7.422.el8_10fixed 4.18.0-553.81.1.rt7.422.el8_10

  In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix potential use-after-free when clear keys Similar to commit c5d2b6fa26b5 ("Bluetooth: Fix use-after-free in hci_remove_ltk/hci_remove_irk"). We can not access k after kfree_rcu() call.

• CVE-2023-53373Sep 18, 2025
  affected < 5.14.0-570.52.1.el9_6fixed 5.14.0-570.52.1.el9_6

  In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Handle EBUSY correctly As it is seqiv only handles the special return value of EINPROGERSS, which means that in all other cases it will free data related to the request. However, as the caller

• CVE-2022-50386Sep 18, 2025
  affected < 4.18.0-553.81.1.rt7.422.el8_10fixed 4.18.0-553.81.1.rt7.422.el8_10

  In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix user-after-free This uses l2cap_chan_hold_unless_zero() after calling __l2cap_get_chan_blah() to prevent the following trace: Bluetooth: l2cap_core.c:static void l2cap_chan_destroy(struct

• CVE-2022-50367Sep 17, 2025
  affected < 5.14.0-570.60.1.el9_6fixed 5.14.0-570.60.1.el9_6

  In the Linux kernel, the following vulnerability has been resolved: fs: fix UAF/GPF bug in nilfs_mdt_destroy In alloc_inode, inode_init_always() could return -ENOMEM if security_inode_alloc() fails, which causes inode->i_private uninitialized. Then nilfs_is_metadata_file_inode(

• CVE-2023-53305Sep 16, 2025
  affected < 4.18.0-553.79.1.rt7.420.el8_10fixed 4.18.0-553.79.1.rt7.420.el8_10

  In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free Fix potential use-after-free in l2cap_le_command_rej.

• CVE-2025-39825MedSep 16, 2025
  affected < 4.18.0-553.87.1.rt7.428.el8_10fixed 4.18.0-553.87.1.rt7.428.el8_10

  In the Linux kernel, the following vulnerability has been resolved: smb: client: fix race with concurrent opens in rename(2) Besides sending the rename request to the server, the rename process also involves closing any deferred close, waiting for outstanding I/O to complete as

• CVE-2025-39817HigSep 16, 2025
  affected < 5.14.0-570.55.1.el9_6fixed 5.14.0-570.55.1.el9_6

  In the Linux kernel, the following vulnerability has been resolved: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare Observed on kernel 6.6 (present on master as well): BUG: KASAN: slab-out-of-bounds in memcmp+0x98/0xd0 Call trace: kasan_check_range+0xe8/0x190

• CVE-2025-39806HigSep 16, 2025
  affected < 5.14.0-611.20.1.el9_7fixed 5.14.0-611.20.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: HID: multitouch: fix slab out-of-bounds access in mt_report_fixup() A malicious HID device can trigger a slab out-of-bounds during mt_report_fixup() by passing in report descriptor smaller than 607 bytes. mt_re

• CVE-2025-39818Sep 16, 2025
  affected < 6.12.0-124.43.1.el10_1fixed 6.12.0-124.43.1.el10_1

  In the Linux kernel, the following vulnerability has been resolved: HID: intel-thc-hid: intel-thc: Fix incorrect pointer arithmetic in I2C regs save Improper use of secondary pointer (&dev->i2c_subip_regs) caused kernel crash and out-of-bounds error: BUG: KASAN: slab-out-of-b