VYPR

rpm package

almalinux/kernel-rt-debug-modules

pkg:rpm/almalinux/kernel-rt-debug-modules

Vulnerabilities (1,421)

  • 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-39841CriSep 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-39840HigSep 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-53401MedSep 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-53386HigSep 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-53373HigSep 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-50386HigSep 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-50367HigSep 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-53305HigSep 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-39825HigSep 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-39818HigSep 16, 2025
    affected < 5.14.0-611.41.1.el9_7fixed 5.14.0-611.41.1.el9_7

    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

  • 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-2023-53297HigSep 16, 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 "bad unlock balance" in l2cap_disconnect_rsp conn->chan_lock isn't acquired before l2cap_get_chan_by_scid, if l2cap_get_chan_by_scid returns NULL, then 'bad unlock balance' is triggered.

  • CVE-2023-53257HigSep 15, 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: mac80211: check S1G action frame size Before checking the action code, check that it even exists in the frame.

  • CVE-2023-53226HigSep 15, 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: mwifiex: Fix OOB and integer underflow when rx packets Make sure mwifiex_process_mgmt_packet, mwifiex_process_sta_rx_packet and mwifiex_process_uap_rx_packet, mwifiex_uap_queue_bridged_pkt and mwifiex_pro

  • CVE-2023-53178HigSep 15, 2025
    affected < 4.18.0-553.83.1.rt7.424.el8_10fixed 4.18.0-553.83.1.rt7.424.el8_10

    In the Linux kernel, the following vulnerability has been resolved: mm: fix zswap writeback race condition The zswap writeback mechanism can cause a race condition resulting in memory corruption, where a swapped out page gets swapped in with data that was written to a different

  • CVE-2025-39797HigSep 12, 2025
    affected < 5.14.0-687.31.1.el9_8fixed 5.14.0-687.31.1.el9_8

    In the Linux kernel, the following vulnerability has been resolved: xfrm: Duplicate SPI Handling The issue originates when Strongswan initiates an XFRM_MSG_ALLOCSPI Netlink message, which triggers the kernel function xfrm_alloc_spi(). This function is expected to ensure uniquen

  • CVE-2025-40300MedSep 11, 2025
    affected < 5.14.0-570.62.1.el9_6fixed 5.14.0-570.62.1.el9_6

    In the Linux kernel, the following vulnerability has been resolved: x86/vmscape: Add conditional IBPB mitigation VMSCAPE is a vulnerability that exploits insufficient branch predictor isolation between a guest and a userspace hypervisor (like QEMU). Existing mitigations already

Page 22 of 72