p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-fips · Seite 200

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für linux-fips: 321. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 6627

  1. CVE-2023-53078

    Mittel · CVSS 5.5EPSS 0,2%Keine Korrektur veröffentlicht

    scsi: scsi_dh_alua: Fix memleak for 'qdata' in alua_activate()

    In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_dh_alua: Fix memleak for 'qdata' in alua_activate() If alua_rtpg_queue() failed from alua_activate(), then 'qdata' is not freed, which will cause following memleak: unreferenced object 0xffff88810b2c6980 (size 32): comm "kworker/u16:2", pid 635322, jiffies 4355801099 (age 1216426.076s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40 39 24 c1 ff ff ff ff 00 f8 ea 0a 81 88 ff ff @9$............. backtrace: [<0000000098f3a26d>] alua_activate+0xb0/0x320 [<000000003b529641>] scsi_dh_activate+0xb2/

    Veröffentlicht Aktualisiert
  2. CVE-2023-53075

    Hoch · CVSS 7.8EPSS 0,21%Keine Korrektur veröffentlicht

    ftrace: Fix invalid address access in lookup_rec() when index is 0

    In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix invalid address access in lookup_rec() when index is 0 KASAN reported follow problem: BUG: KASAN: use-after-free in lookup_rec Read of size 8 at addr ffff000199270ff0 by task modprobe CPU: 2 Comm: modprobe Call trace: kasan_report __asan_load8 lookup_rec ftrace_location arch_check_ftrace_location check_kprobe_address_safe register_kprobe When checking pg->records[pg->index - 1].ip in lookup_rec(), it can get a pg which is newly added to ftrace_pages_start in ftrace_process_locs(). Before the first pg->index++, index is 0 and accessing pg->rec

    Veröffentlicht Aktualisiert
  3. CVE-2023-53068

    Mittel · CVSS 5.5EPSS 0,2%Keine Korrektur veröffentlicht

    net: usb: lan78xx: Limit packet length to skb->len

    In the Linux kernel, the following vulnerability has been resolved: net: usb: lan78xx: Limit packet length to skb->len Packet length retrieved from descriptor may be larger than the actual socket buffer length. In such case the cloned skb passed up the network stack will leak kernel memory contents. Additionally prevent integer underflow when size is less than ETH_FCS_LEN.

    Veröffentlicht Aktualisiert
  4. CVE-2023-53066

    Mittel · CVSS 6.7EPSS 0,22%Keine Korrektur veröffentlicht

    qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info

    In the Linux kernel, the following vulnerability has been resolved: qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info We have to make sure that the info returned by the helper is valid before using it. Found by Linux Verification Center (linuxtesting.org) with the SVACE static analysis tool.

    Veröffentlicht Aktualisiert
  5. CVE-2023-53062

    Mittel · CVSS 5.5EPSS 0,2%Keine Korrektur veröffentlicht

    net: usb: smsc95xx: Limit packet length to skb->len

    In the Linux kernel, the following vulnerability has been resolved: net: usb: smsc95xx: Limit packet length to skb->len Packet length retrieved from descriptor may be larger than the actual socket buffer length. In such case the cloned skb passed up the network stack will leak kernel memory contents.

    Veröffentlicht Aktualisiert
  6. CVE-2023-53051

    Mittel · CVSS 6.8EPSS 0,22%Keine Korrektur veröffentlicht

    dm crypt: add cond_resched() to dmcrypt_write()

    In the Linux kernel, the following vulnerability has been resolved: dm crypt: add cond_resched() to dmcrypt_write() The loop in dmcrypt_write may be running for unbounded amount of time, thus we need cond_resched() in it. This commit fixes the following warning: [ 3391.153255][ C12] watchdog: BUG: soft lockup - CPU#12 stuck for 23s! [dmcrypt_write/2:2897] ... [ 3391.387210][ C12] Call trace: [ 3391.390338][ C12] blk_attempt_bio_merge.part.6+0x38/0x158 [ 3391.395970][ C12] blk_attempt_plug_merge+0xc0/0x1b0 [ 3391.401085][ C12] blk_mq_submit_bio+0x398/0x550 [ 3391.405856][ C12] submit_bio_noacct+0x308/0x380 [ 3391.410630][

    Veröffentlicht Aktualisiert
  7. CVE-2023-53045

    Mittel · CVSS 5.5EPSS 0,15%Keine Korrektur veröffentlicht

    usb: gadget: u_audio: don't let userspace block driver unbind

    In the Linux kernel, the following vulnerability has been resolved: usb: gadget: u_audio: don't let userspace block driver unbind In the unbind callback for f_uac1 and f_uac2, a call to snd_card_free() via g_audio_cleanup() will disconnect the card and then wait for all resources to be released, which happens when the refcount falls to zero. Since userspace can keep the refcount incremented by not closing the relevant file descriptor, the call to unbind may block indefinitely. This can cause a deadlock during reboot, as evidenced by the following blocked task observed on my machine: task:reboot state:D stack:0 pid:2827 ppid:569 fl

    Veröffentlicht Aktualisiert
  8. CVE-2023-53044

    Mittel · CVSS 5.5EPSS 0,2%Keine Korrektur veröffentlicht

    dm stats: check for and propagate alloc_percpu failure

    In the Linux kernel, the following vulnerability has been resolved: dm stats: check for and propagate alloc_percpu failure Check alloc_precpu()'s return value and return an error from dm_stats_init() if it fails. Update alloc_dev() to fail if dm_stats_init() does. Otherwise, a NULL pointer dereference will occur in dm_stats_cleanup() even if dm-stats isn't being actively used.

    Veröffentlicht Aktualisiert
  9. CVE-2023-53039

    Hoch · CVSS 7.8EPSS 0,21%Keine Korrektur veröffentlicht

    HID: intel-ish-hid: ipc: Fix potential use-after-free in work function

    In the Linux kernel, the following vulnerability has been resolved: HID: intel-ish-hid: ipc: Fix potential use-after-free in work function When a reset notify IPC message is received, the ISR schedules a work function and passes the ISHTP device to it via a global pointer ishtp_dev. If ish_probe() fails, the devm-managed device resources including ishtp_dev are freed, but the work is not cancelled, causing a use-after-free when the work function tries to access ishtp_dev. Use devm_work_autocancel() instead, so that the work is automatically cancelled if probe fails.

    Veröffentlicht Aktualisiert
  10. CVE-2023-53035

    Hoch · CVSS 7.1EPSS 0,22%Keine Korrektur veröffentlicht

    nilfs2: fix kernel-infoleak in nilfs_ioctl_wrap_copy()

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix kernel-infoleak in nilfs_ioctl_wrap_copy() The ioctl helper function nilfs_ioctl_wrap_copy(), which exchanges a metadata array to/from user space, may copy uninitialized buffer regions to user space memory for read-only ioctl commands NILFS_IOCTL_GET_SUINFO and NILFS_IOCTL_GET_CPINFO. This can occur when the element size of the user space metadata given by the v_size member of the argument nilfs_argv structure is larger than the size of the metadata element (nilfs_suinfo structure or nilfs_cpinfo structure) on the file system side. KMSAN-enabled kernels detect

    Veröffentlicht Aktualisiert
  11. CVE-2022-49932

    Mittel · CVSS 5.6EPSS 0,21%Keine Korrektur veröffentlicht

    KVM: VMX: Do _all_ initialization before exposing /dev/kvm to userspace

    In the Linux kernel, the following vulnerability has been resolved: KVM: VMX: Do _all_ initialization before exposing /dev/kvm to userspace Call kvm_init() only after _all_ setup is complete, as kvm_init() exposes /dev/kvm to userspace and thus allows userspace to create VMs (and call other ioctls). E.g. KVM will encounter a NULL pointer when attempting to add a vCPU to the per-CPU loaded_vmcss_on_cpu list if userspace is able to create a VM before vmx_init() configures said list. BUG: kernel NULL pointer dereference, address: 0000000000000008 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0

    Veröffentlicht Aktualisiert
  12. CVE-2025-37798

    Hoch · CVSS 7.8EPSS 0,23%Keine Korrektur veröffentlicht

    codel: remove sch->q.qlen check before qdisc_tree_reduce_backlog()

    In the Linux kernel, the following vulnerability has been resolved: codel: remove sch->q.qlen check before qdisc_tree_reduce_backlog() After making all ->qlen_notify() callbacks idempotent, now it is safe to remove the check of qlen!=0 from both fq_codel_dequeue() and codel_qdisc_dequeue().

    Veröffentlicht Aktualisiert
  13. CVE-2025-37797

    Hoch · CVSS 7.8EPSS 0,22%Keine Korrektur veröffentlicht

    net_sched: hfsc: Fix a UAF vulnerability in class handling

    In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Fix a UAF vulnerability in class handling This patch fixes a Use-After-Free vulnerability in the HFSC qdisc class handling. The issue occurs due to a time-of-check/time-of-use condition in hfsc_change_class() when working with certain child qdiscs like netem or codel. The vulnerability works as follows: 1. hfsc_change_class() checks if a class has packets (q.qlen != 0) 2. It then calls qdisc_peek_len(), which for certain qdiscs (e.g., codel, netem) might drop packets and empty the queue 3. The code continues assuming the queue is still non-empty, adding

    Veröffentlicht Aktualisiert
  14. CVE-2022-49927

    Mittel · CVSS 5.5EPSS 0,2%Keine Korrektur veröffentlicht

    nfs4: Fix kmemleak when allocate slot failed

    In the Linux kernel, the following vulnerability has been resolved: nfs4: Fix kmemleak when allocate slot failed If one of the slot allocate failed, should cleanup all the other allocated slots, otherwise, the allocated slots will leak: unreferenced object 0xffff8881115aa100 (size 64): comm ""mount.nfs"", pid 679, jiffies 4294744957 (age 115.037s) hex dump (first 32 bytes): 00 cc 19 73 81 88 ff ff 00 a0 5a 11 81 88 ff ff ...s......Z..... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<000000007a4c434a>] nfs4_find_or_create_slot+0x8e/0x130 [<000000005472a39c>] nfs4_reallo

    Veröffentlicht Aktualisiert
  15. CVE-2022-49926

    Mittel · CVSS 5.5EPSS 0,19%Keine Korrektur veröffentlicht

    net: dsa: Fix possible memory leaks in dsa_loop_init()

    In the Linux kernel, the following vulnerability has been resolved: net: dsa: Fix possible memory leaks in dsa_loop_init() kmemleak reported memory leaks in dsa_loop_init(): kmemleak: 12 new suspected memory leaks unreferenced object 0xffff8880138ce000 (size 2048): comm "modprobe", pid 390, jiffies 4295040478 (age 238.976s) backtrace: [<000000006a94f1d5>] kmalloc_trace+0x26/0x60 [<00000000a9c44622>] phy_device_create+0x5d/0x970 [<00000000d0ee2afc>] get_phy_device+0xf3/0x2b0 [<00000000dca0c71f>] __fixed_phy_register.part.0+0x92/0x4e0 [<000000008a834798>] fixed_phy_register+0x84/0xb0 [<0000000055223fcb>] dsa_loop

    Veröffentlicht Aktualisiert
  16. CVE-2022-49925

    Mittel · CVSS 5.5EPSS 0,2%Keine Korrektur veröffentlicht

    RDMA/core: Fix null-ptr-deref in ib_core_cleanup()

    In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix null-ptr-deref in ib_core_cleanup() KASAN reported a null-ptr-deref error: KASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f] CPU: 1 PID: 379 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) RIP: 0010:destroy_workqueue+0x2f/0x740 RSP: 0018:ffff888016137df8 EFLAGS: 00000202 ... Call Trace: ib_core_cleanup+0xa/0xa1 [ib_core] __do_sys_delete_module.constprop.0+0x34f/0x5b0 do_syscall_64+0x3a/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fa1a0d221b7 ... It is because the fail of roce_gid_mgmt_in

    Veröffentlicht Aktualisiert
  17. CVE-2022-49924

    Mittel · CVSS 5.5EPSS 0,19%Keine Korrektur veröffentlicht

    nfc: fdp: Fix potential memory leak in fdp_nci_send()

    In the Linux kernel, the following vulnerability has been resolved: nfc: fdp: Fix potential memory leak in fdp_nci_send() fdp_nci_send() will call fdp_nci_i2c_write that will not free skb in the function. As a result, when fdp_nci_i2c_write() finished, the skb will memleak. fdp_nci_send() should free skb after fdp_nci_i2c_write() finished.

    Veröffentlicht Aktualisiert
  18. CVE-2022-49923

    Mittel · CVSS 5.5EPSS 0,19%Keine Korrektur veröffentlicht

    nfc: nxp-nci: Fix potential memory leak in nxp_nci_send()

    In the Linux kernel, the following vulnerability has been resolved: nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() nxp_nci_send() will call nxp_nci_i2c_write(), and only free skb when nxp_nci_i2c_write() failed. However, even if the nxp_nci_i2c_write() run succeeds, the skb will not be freed in nxp_nci_i2c_write(). As the result, the skb will memleak. nxp_nci_send() should also free the skb when nxp_nci_i2c_write() succeeds.

    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →