p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux · Seite 101

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 4292

  1. CVE-2025-39973

    Hoch · CVSS 8.8EPSS 0,15%Keine Korrektur veröffentlicht

    i40e: add validation for ring_len param

    In the Linux kernel, the following vulnerability has been resolved: i40e: add validation for ring_len param The `ring_len` parameter provided by the virtual function (VF) is assigned directly to the hardware memory context (HMC) without any validation. To address this, introduce an upper boundary check for both Tx and Rx queue lengths. The maximum number of descriptors supported by the hardware is 8k-32. Additionally, enforce alignment constraints: Tx rings must be a multiple of 8, and Rx rings must be a multiple of 32.

    Veröffentlicht Aktualisiert
  2. CVE-2025-39964

    Hoch · CVSS 7.8EPSS 1,61%Im KEV-KatalogÖffentlicher ExploitKeine Korrektur veröffentlicht

    crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg

    In the Linux kernel, the following vulnerability has been resolved: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg Issuing two writes to the same af_alg socket is bogus as the data will be interleaved in an unpredictable fashion. Furthermore, concurrent writes may create inconsistencies in the internal socket state. Disallow this by adding a new ctx->write field that indiciates exclusive ownership for writing.

    Veröffentlicht Aktualisiert
  3. CVE-2025-39955

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

    tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect().

    In the Linux kernel, the following vulnerability has been resolved: tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). syzbot reported the splat below where a socket had tcp_sk(sk)->fastopen_rsk in the TCP_ESTABLISHED state. [0] syzbot reused the server-side TCP Fast Open socket as a new client before the TFO socket completes 3WHS: 1. accept() 2. connect(AF_UNSPEC) 3. connect() to another destination As of accept(), sk->sk_state is TCP_SYN_RECV, and tcp_disconnect() changes it to TCP_CLOSE and makes connect() possible, which restarts timers. Since tcp_disconnect() forgot to clear tcp_sk(sk)->fastopen_rsk, the retransmit time

    Veröffentlicht Aktualisiert
  4. CVE-2023-53687

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

    tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() when iterating clk

    In the Linux kernel, the following vulnerability has been resolved: tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() when iterating clk When the best clk is searched, we iterate over all possible clk. If we find a better match, the previous one, if any, needs to be freed. If a better match has already been found, we still need to free the new one, otherwise it leaks.

    Veröffentlicht Aktualisiert
  5. CVE-2023-53685

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

    tun: Fix memory leak for detached NAPI queue.

    In the Linux kernel, the following vulnerability has been resolved: tun: Fix memory leak for detached NAPI queue. syzkaller reported [0] memory leaks of sk and skb related to the TUN device with no repro, but we can reproduce it easily with: struct ifreq ifr = {} int fd_tun, fd_tmp; char buf[4] = {}; fd_tun = openat(AT_FDCWD, "/dev/net/tun", O_WRONLY, 0); ifr.ifr_flags = IFF_TUN | IFF_NAPI | IFF_MULTI_QUEUE; ioctl(fd_tun, TUNSETIFF, &ifr); ifr.ifr_flags = IFF_DETACH_QUEUE; ioctl(fd_tun, TUNSETQUEUE, &ifr); fd_tmp = socket(AF_PACKET, SOCK_PACKET, 0); ifr.ifr_flags = IFF_UP; ioctl(fd_tmp, SIOCSIFFLAGS, &ifr); writ

    Veröffentlicht Aktualisiert
  6. CVE-2023-53681

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

    bcache: Fix __bch_btree_node_alloc to make the failure behavior consistent

    In the Linux kernel, the following vulnerability has been resolved: bcache: Fix __bch_btree_node_alloc to make the failure behavior consistent In some specific situations, the return value of __bch_btree_node_alloc may be NULL. This may lead to a potential NULL pointer dereference in caller function like a calling chain : btree_split->bch_btree_node_alloc->__bch_btree_node_alloc. Fix it by initializing the return value in __bch_btree_node_alloc.

    Veröffentlicht Aktualisiert
  7. CVE-2023-53676

    Hoch · CVSS 8.8EPSS 0,32%Keine Korrektur veröffentlicht

    scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show()

    In the Linux kernel, the following vulnerability has been resolved: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() The function lio_target_nacl_info_show() uses sprintf() in a loop to print details for every iSCSI connection in a session without checking for the buffer length. With enough iSCSI connections it's possible to overflow the buffer provided by configfs and corrupt the memory. This patch replaces sprintf() with sysfs_emit_at() that checks for buffer boundries.

    Veröffentlicht Aktualisiert
  8. CVE-2023-53672

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

    btrfs: output extra debug info if we failed to find an inline backref

    In the Linux kernel, the following vulnerability has been resolved: btrfs: output extra debug info if we failed to find an inline backref [BUG] Syzbot reported several warning triggered inside lookup_inline_extent_backref(). [CAUSE] As usual, the reproducer doesn't reliably trigger locally here, but at least we know the WARN_ON() is triggered when an inline backref can not be found, and it can only be triggered when @insert is true. (I.e. inserting a new inline backref, which means the backref should already exist) [ENHANCEMENT] After the WARN_ON(), dump all the parameters and the extent tree leaf to help debug.

    Veröffentlicht Aktualisiert
  9. CVE-2023-53668

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

    ring-buffer: Fix deadloop issue on reading trace_pipe

    In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix deadloop issue on reading trace_pipe Soft lockup occurs when reading file 'trace_pipe': watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [cat:4488] [...] RIP: 0010:ring_buffer_empty_cpu+0xed/0x170 RSP: 0018:ffff88810dd6fc48 EFLAGS: 00000246 RAX: 0000000000000000 RBX: 0000000000000246 RCX: ffffffff93d1aaeb RDX: ffff88810a280040 RSI: 0000000000000008 RDI: ffff88811164b218 RBP: ffff88811164b218 R08: 0000000000000000 R09: ffff88815156600f R10: ffffed102a2acc01 R11: 0000000000000001 R12: 0000000051651901 R13: 0000000000000000 R14: ffff888115e

    Veröffentlicht Aktualisiert
  10. CVE-2023-53667

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

    net: cdc_ncm: Deal with too low values of dwNtbOutMaxSize

    In the Linux kernel, the following vulnerability has been resolved: net: cdc_ncm: Deal with too low values of dwNtbOutMaxSize Currently in cdc_ncm_check_tx_max(), if dwNtbOutMaxSize is lower than the calculated "min" value, but greater than zero, the logic sets tx_max to dwNtbOutMaxSize. This is then used to allocate a new SKB in cdc_ncm_fill_tx_frame() where all the data is handled. For small values of dwNtbOutMaxSize the memory allocated during alloc_skb(dwNtbOutMaxSize, GFP_ATOMIC) will have the same size, due to how size is aligned at alloc time: size = SKB_DATA_ALIGN(size); size += SKB_DATA_ALIGN(sizeof(struct skb_shared_info

    Veröffentlicht Aktualisiert
  11. CVE-2022-50551

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

    wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request()

    In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() This patch fixes a shift-out-of-bounds in brcmfmac that occurs in BIT(chiprev) when a 'chiprev' provided by the device is too large. It should also not be equal to or greater than BITS_PER_TYPE(u32) as we do bitwise AND with a u32 variable and BIT(chiprev). The patch adds a check that makes the function return NULL if that is the case. Note that the NULL case is later handled by the bus-specific caller, brcmf_usb_probe_cb() or brcmf_usb_reset_resume(), for example. Found by a modified version of

    Veröffentlicht Aktualisiert
  12. CVE-2022-50549

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

    dm thin: Fix ABBA deadlock between shrink_slab and dm_pool_abort_metadata

    In the Linux kernel, the following vulnerability has been resolved: dm thin: Fix ABBA deadlock between shrink_slab and dm_pool_abort_metadata Following concurrent processes: P1(drop cache) P2(kworker) drop_caches_sysctl_handler drop_slab shrink_slab down_read(&shrinker_rwsem) - LOCK A do_shrink_slab super_cache_scan prune_icache_sb dispose_list evict ext4_evict_inode ext4_clear_inode ext4_discard_preallocations ext4_mb_load_buddy_gfp ext4_mb_init_cache ext4_read_block_bitmap_nowait ext4_read_bh_nowait submit_bh dm_submit_bio

    Veröffentlicht Aktualisiert
  13. CVE-2022-50547

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

    media: solo6x10: fix possible memory leak in solo_sysfs_init()

    In the Linux kernel, the following vulnerability has been resolved: media: solo6x10: fix possible memory leak in solo_sysfs_init() If device_register() returns error in solo_sysfs_init(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup().

    Veröffentlicht Aktualisiert
  14. CVE-2022-50545

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

    r6040: Fix kmemleak in probe and remove

    In the Linux kernel, the following vulnerability has been resolved: r6040: Fix kmemleak in probe and remove There is a memory leaks reported by kmemleak: unreferenced object 0xffff888116111000 (size 2048): comm "modprobe", pid 817, jiffies 4294759745 (age 76.502s) hex dump (first 32 bytes): 00 c4 0a 04 81 88 ff ff 08 10 11 16 81 88 ff ff ................ 08 10 11 16 81 88 ff ff 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffff815bcd82>] kmalloc_trace+0x22/0x60 [<ffffffff827e20ee>] phy_device_create+0x4e/0x90 [<ffffffff827e6072>] get_phy_device+0xd2/0x220 [<ffffffff827e7844>]

    Veröffentlicht Aktualisiert
  15. CVE-2022-50544

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

    usb: host: xhci: Fix potential memory leak in xhci_alloc_stream_info()

    In the Linux kernel, the following vulnerability has been resolved: usb: host: xhci: Fix potential memory leak in xhci_alloc_stream_info() xhci_alloc_stream_info() allocates stream context array for stream_info ->stream_ctx_array with xhci_alloc_stream_ctx(). When some error occurs, stream_info->stream_ctx_array is not released, which will lead to a memory leak. We can fix it by releasing the stream_info->stream_ctx_array with xhci_free_stream_ctx() on the error path to avoid the potential memory leak.

    Veröffentlicht Aktualisiert
  16. CVE-2022-50542

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

    media: si470x: Fix use-after-free in si470x_int_in_callback()

    In the Linux kernel, the following vulnerability has been resolved: media: si470x: Fix use-after-free in si470x_int_in_callback() syzbot reported use-after-free in si470x_int_in_callback() [1]. This indicates that urb->context, which contains struct si470x_device object, is freed when si470x_int_in_callback() is called. The cause of this issue is that si470x_int_in_callback() is called for freed urb. si470x_usb_driver_probe() calls si470x_start_usb(), which then calls usb_submit_urb() and si470x_start(). If si470x_start_usb() fails, si470x_usb_driver_probe() doesn't kill urb, but it just frees struct si470x_device object, as depicted be

    Veröffentlicht Aktualisiert
  17. CVE-2023-53650

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

    fbdev: omapfb: lcd_mipid: Fix an error handling path in mipid_spi_probe()

    In the Linux kernel, the following vulnerability has been resolved: fbdev: omapfb: lcd_mipid: Fix an error handling path in mipid_spi_probe() If 'mipid_detect()' fails, we must free 'md' to avoid a memory leak.

    Veröffentlicht Aktualisiert
  18. CVE-2023-53648

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

    ALSA: ac97: Fix possible NULL dereference in snd_ac97_mixer

    In the Linux kernel, the following vulnerability has been resolved: ALSA: ac97: Fix possible NULL dereference in snd_ac97_mixer smatch error: sound/pci/ac97/ac97_codec.c:2354 snd_ac97_mixer() error: we previously assumed 'rac97' could be null (see line 2072) remove redundant assignment, return error if rac97 is NULL.

    Veröffentlicht Aktualisiert
  19. CVE-2023-53644

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

    media: radio-shark: Add endpoint checks

    In the Linux kernel, the following vulnerability has been resolved: media: radio-shark: Add endpoint checks The syzbot fuzzer was able to provoke a WARNING from the radio-shark2 driver: ------------[ cut here ]------------ usb 1-1: BOGUS urb xfer, pipe 1 != type 3 WARNING: CPU: 0 PID: 3271 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed2/0x1880 drivers/usb/core/urb.c:504 Modules linked in: CPU: 0 PID: 3271 Comm: kworker/0:3 Not tainted 6.1.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Workqueue: usb_hub_wq hub_event RIP: 0010:usb_submit_urb+0xed2/0x1880 drivers/usb/core/urb.c

    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 →