VYPR

rpm package

almalinux/kernel-debug-modules-extra

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

Vulnerabilities (2,016)

  • CVE-2023-53494HigOct 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-39925MedOct 1, 2025
    affected < 5.14.0-611.13.1.el9_7fixed 5.14.0-611.13.1.el9_7

    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-39918HigOct 1, 2025
    affected < 5.14.0-611.11.1.el9_7fixed 5.14.0-611.11.1.el9_7

    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-39905HigOct 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-39902HigOct 1, 2025
    affected < 4.18.0-553.156.1.el8_10fixed 4.18.0-553.156.1.el8_10

    In the Linux kernel, the following vulnerability has been resolved: mm/slub: avoid accessing metadata when pointer is invalid in object_err() object_err() reports details of an object for further debugging, such as the freelist pointer, redzone, etc. However, if the pointer is

  • CVE-2025-39898Oct 1, 2025
    affected < 4.18.0-553.87.1.el8_10fixed 4.18.0-553.87.1.el8_10

    Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

  • CVE-2025-39883HigSep 23, 2025
    affected < 4.18.0-553.87.1.el8_10fixed 4.18.0-553.87.1.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-39866HigSep 19, 2025
    affected < 5.14.0-687.5.1.el9_8fixed 5.14.0-687.5.1.el9_8

    In the Linux kernel, the following vulnerability has been resolved: fs: writeback: fix use-after-free in __mark_inode_dirty() An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching. CPU: 1 PID: 562 Comm: systemd-r

  • CVE-2025-39864HigSep 19, 2025
    affected < 4.18.0-553.82.1.el8_10fixed 4.18.0-553.82.1.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-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.el8_10fixed 4.18.0-553.89.1.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.el8_10fixed 4.18.0-553.81.1.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.el8_10fixed 4.18.0-553.81.1.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.el8_10fixed 4.18.0-553.79.1.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-2022-50341HigSep 16, 2025
    affected < 4.18.0-553.27.1.el8_10fixed 4.18.0-553.27.1.el8_10

    In the Linux kernel, the following vulnerability has been resolved: cifs: fix oops during encryption When running xfstests against Azure the following oops occurred on an arm64 system Unable to handle kernel write to read-only memory at virtual address ffff0001221cf000 M

Page 38 of 101