VYPR

rpm package

suse/kernel-default&distro=SUSE Linux Enterprise Live Patching 15 SP6

pkg:rpm/suse/kernel-default&distro=SUSE%20Linux%20Enterprise%20Live%20Patching%2015%20SP6

Vulnerabilities (4,170)

  • CVE-2025-21653MedJan 19, 2025
    affected < 6.4.0-150600.23.38.1fixed 6.4.0-150600.23.38.1

    In the Linux kernel, the following vulnerability has been resolved: net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute syzbot found that TCA_FLOW_RSHIFT attribute was not validated. Right shitfing a 32bit integer is undefined for large shift values. UBSAN: shift-out-of-bo

  • CVE-2025-21652HigJan 19, 2025
    affected < 6.4.0-150600.23.38.1fixed 6.4.0-150600.23.38.1

    In the Linux kernel, the following vulnerability has been resolved: ipvlan: Fix use-after-free in ipvlan_get_iflink(). syzbot presented an use-after-free report [0] regarding ipvlan and linkwatch. ipvlan does not hold a refcnt of the lower device unlike vlan and macvlan. If t

  • CVE-2025-21651MedJan 19, 2025
    affected < 6.4.0-150600.23.38.1fixed 6.4.0-150600.23.38.1

    In the Linux kernel, the following vulnerability has been resolved: net: hns3: don't auto enable misc vector Currently, there is a time window between misc irq enabled and service task inited. If an interrupte is reported at this time, it will cause warning like below: [ 16.

  • CVE-2025-21650HigJan 19, 2025
    affected < 6.4.0-150600.23.38.1fixed 6.4.0-150600.23.38.1

    In the Linux kernel, the following vulnerability has been resolved: net: hns3: fixed hclge_fetch_pf_reg accesses bar space out of bounds issue The TQP BAR space is divided into two segments. TQPs 0-1023 and TQPs 1024-1279 are in different BAR space addresses. However, hclge_fet

  • CVE-2025-21649MedJan 19, 2025
    affected < 6.4.0-150600.23.38.1fixed 6.4.0-150600.23.38.1

    In the Linux kernel, the following vulnerability has been resolved: net: hns3: fix kernel crash when 1588 is sent on HIP08 devices Currently, HIP08 devices does not register the ptp devices, so the hdev->ptp is NULL. But the tx process would still try to set hardware time stamp

  • CVE-2025-21648MedJan 19, 2025
    affected < 6.4.0-150600.23.53.1fixed 6.4.0-150600.23.53.1

    In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: clamp maximum hashtable size to INT_MAX Use INT_MAX as maximum size for the conntrack hashtable. Otherwise, it is possible to hit WARN_ON_ONCE in __kvmalloc_node_noprof() when resizing has

  • CVE-2025-21647HigJan 19, 2025
    affected < 6.4.0-150600.23.42.2fixed 6.4.0-150600.23.42.2

    In the Linux kernel, the following vulnerability has been resolved: sched: sch_cake: add bounds checks to host bulk flow fairness counts Even though we fixed a logic error in the commit cited below, syzbot still managed to trigger an underflow of the per-host bulk flow counters

  • CVE-2025-21646HigJan 19, 2025
    affected < 6.4.0-150600.23.38.1fixed 6.4.0-150600.23.38.1

    In the Linux kernel, the following vulnerability has been resolved: afs: Fix the maximum cell name length The kafs filesystem limits the maximum length of a cell to 256 bytes, but a problem occurs if someone actually does that: kafs tries to create a directory under /proc/net/a

  • CVE-2025-21645MedJan 19, 2025
    affected < 6.4.0-150600.23.38.1fixed 6.4.0-150600.23.38.1

    In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it Wakeup for IRQ1 should be disabled only in cases where i8042 had actually enabled it, otherwise "wake_depth" for this IRQ will try

  • CVE-2025-21640HigJan 19, 2025
    affected < 6.4.0-150600.23.42.2fixed 6.4.0-150600.23.42.2

    In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: cookie_hmac_alg: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency:

  • CVE-2025-21639MedJan 19, 2025
    affected < 6.4.0-150600.23.42.2fixed 6.4.0-150600.23.42.2

    In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: rto_min/max: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: gett

  • CVE-2025-21638HigJan 19, 2025
    affected < 6.4.0-150600.23.42.2fixed 6.4.0-150600.23.42.2

    In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: auth_enable: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: gett

  • CVE-2025-21637HigJan 19, 2025
    affected < 6.4.0-150600.23.42.2fixed 6.4.0-150600.23.42.2

    In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: udp_port: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting

  • CVE-2025-21636MedJan 19, 2025
    affected < 6.4.0-150600.23.42.2fixed 6.4.0-150600.23.42.2

    In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: plpmtud_probe_interval: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsis

  • CVE-2025-21635MedJan 19, 2025
    affected < 6.4.0-150600.23.47.2fixed 6.4.0-150600.23.47.2

    In the Linux kernel, the following vulnerability has been resolved: rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsisten

  • CVE-2025-21632MedJan 19, 2025
    affected < 6.4.0-150600.23.38.1fixed 6.4.0-150600.23.38.1

    In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Ensure shadow stack is active before "getting" registers The x86 shadow stack support has its own set of registers. Those registers are XSAVE-managed, but they are "supervisor state components" which m

  • CVE-2025-21631HigJan 19, 2025
    affected < 6.4.0-150600.23.47.2fixed 6.4.0-150600.23.47.2

    In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix waker_bfqq UAF after bfq_split_bfqq() Our syzkaller report a following UAF for v6.6: BUG: KASAN: slab-use-after-free in bfq_init_rq+0x175d/0x17a0 block/bfq-iosched.c:6958 Read of size 8 at addr

  • CVE-2025-21629HigJan 15, 2025
    affected < 6.4.0-150600.23.53.1fixed 6.4.0-150600.23.53.1

    In the Linux kernel, the following vulnerability has been resolved: net: reenable NETIF_F_IPV6_CSUM offload for BIG TCP packets The blamed commit disabled hardware offoad of IPv6 packets with extension headers on devices that advertise NETIF_F_IPV6_CSUM, based on the definition

  • CVE-2024-57903MedJan 15, 2025
    affected < 6.4.0-150600.23.38.1fixed 6.4.0-150600.23.38.1

    In the Linux kernel, the following vulnerability has been resolved: net: restrict SO_REUSEPORT to inet sockets After blamed commit, crypto sockets could accidentally be destroyed from RCU call back, as spotted by zyzbot [1]. Trying to acquire a mutex in RCU callback is not all

  • CVE-2024-57900HigJan 15, 2025
    affected < 6.4.0-150600.23.47.2fixed 6.4.0-150600.23.47.2

    In the Linux kernel, the following vulnerability has been resolved: ila: serialize calls to nf_register_net_hooks() syzbot found a race in ila_add_mapping() [1] commit 031ae72825ce ("ila: call nf_unregister_net_hooks() sooner") attempted to fix a similar issue. Looking at the

Page 98 of 209