p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-gcp-5.4 · Seite 29

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

RSS ↗ JSON ↗
Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 1756

  1. CVE-2022-49592

    Hoch · CVSS 7.8EPSS 0,28%Korrektur verfügbar

    net: stmmac: fix dma queue left shift overflow issue

    In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix dma queue left shift overflow issue When queue number is > 4, left shift overflows due to 32 bits integer variable. Mask calculation is wrong for MTL_RXQ_DMA_MAP1. If CONFIG_UBSAN is enabled, kernel dumps below warning: [ 10.363842] ================================================================== [ 10.363882] UBSAN: shift-out-of-bounds in /build/linux-intel-iotg-5.15-8e6Tf4/ linux-intel-iotg-5.15-5.15.0/drivers/net/ethernet/stmicro/stmmac/dwmac4_core.c:224:12 [ 10.363929] shift exponent 40 is too large for 32-bit type 'unsigned int' [ 10.363953]

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  2. CVE-2022-49590

    Mittel · CVSS 4.7EPSS 0,19%Korrektur verfügbar

    igmp: Fix data-races around sysctl_igmp_llm_reports.

    In the Linux kernel, the following vulnerability has been resolved: igmp: Fix data-races around sysctl_igmp_llm_reports. While reading sysctl_igmp_llm_reports, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers. This test can be packed into a helper, so such changes will be in the follow-up series after net is merged into net-next. if (ipv4_is_local_multicast(pmc->multiaddr) && !READ_ONCE(net->ipv4.sysctl_igmp_llm_reports))

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  3. CVE-2022-49589

    Mittel · CVSS 4.7EPSS 0,19%Korrektur verfügbar

    igmp: Fix data-races around sysctl_igmp_qrv.

    In the Linux kernel, the following vulnerability has been resolved: igmp: Fix data-races around sysctl_igmp_qrv. While reading sysctl_igmp_qrv, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers. This test can be packed into a helper, so such changes will be in the follow-up series after net is merged into net-next. qrv ?: READ_ONCE(net->ipv4.sysctl_igmp_qrv);

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  4. CVE-2022-49587

    Mittel · CVSS 4.7EPSS 0,19%Korrektur verfügbar

    tcp: Fix a data-race around sysctl_tcp_notsent_lowat.

    In the Linux kernel, the following vulnerability has been resolved: tcp: Fix a data-race around sysctl_tcp_notsent_lowat. While reading sysctl_tcp_notsent_lowat, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader.

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  5. CVE-2022-49586

    Mittel · CVSS 4.7EPSS 0,19%Korrektur verfügbar

    tcp: Fix data-races around sysctl_tcp_fastopen.

    In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctl_tcp_fastopen. While reading sysctl_tcp_fastopen, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers.

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  6. CVE-2022-49584

    Mittel · CVSS 5.5EPSS 0,2%Korrektur verfügbar

    ixgbe: Add locking to prevent panic when setting sriov_numvfs to zero

    In the Linux kernel, the following vulnerability has been resolved: ixgbe: Add locking to prevent panic when setting sriov_numvfs to zero It is possible to disable VFs while the PF driver is processing requests from the VF driver. This can result in a panic. BUG: unable to handle kernel paging request at 000000000000106c PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI CPU: 8 PID: 0 Comm: swapper/8 Kdump: loaded Tainted: G I --------- - Hardware name: Dell Inc. PowerEdge R740/06WXJT, BIOS 2.8.2 08/27/2020 RIP: 0010:ixgbe_msg_task+0x4c8/0x1690 [ixgbe] Code: 00 00 48 8d 04 40 48 c1 e0 05 89 7c 24 24 89 fd 48 89 44 24 10 83 ff 01 0f 84 b8 04 00 00

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  7. CVE-2022-49583

    Mittel · CVSS 5.5EPSS 0,27%Korrektur verfügbar

    iavf: Fix handling of dummy receive descriptors

    In the Linux kernel, the following vulnerability has been resolved: iavf: Fix handling of dummy receive descriptors Fix memory leak caused by not handling dummy receive descriptor properly. iavf_get_rx_buffer now sets the rx_buffer return value for dummy receive descriptors. Without this patch, when the hardware writes a dummy descriptor, iavf would not free the page allocated for the previous receive buffer. This is an unlikely event but can still happen. [Jesse: massaged commit message]

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  8. CVE-2022-49581

    Hoch · CVSS 7.8EPSS 0,31%Korrektur verfügbar

    be2net: Fix buffer overflow in be_get_module_eeprom

    In the Linux kernel, the following vulnerability has been resolved: be2net: Fix buffer overflow in be_get_module_eeprom be_cmd_read_port_transceiver_data assumes that it is given a buffer that is at least PAGE_DATA_LEN long, or twice that if the module supports SFF 8472. However, this is not always the case. Fix this by passing the desired offset and length to be_cmd_read_port_transceiver_data so that we only copy the bytes once.

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  9. CVE-2022-49580

    Mittel · CVSS 4.7EPSS 0,18%Korrektur verfügbar

    ipv4: Fix a data-race around sysctl_fib_multipath_use_neigh.

    In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix a data-race around sysctl_fib_multipath_use_neigh. While reading sysctl_fib_multipath_use_neigh, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader.

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  10. CVE-2022-49577

    Mittel · CVSS 4.7EPSS 0,18%Korrektur verfügbar

    udp: Fix a data-race around sysctl_udp_l3mdev_accept.

    In the Linux kernel, the following vulnerability has been resolved: udp: Fix a data-race around sysctl_udp_l3mdev_accept. While reading sysctl_udp_l3mdev_accept, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader.

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  11. CVE-2022-49575

    Mittel · CVSS 4.7EPSS 0,19%Korrektur verfügbar

    tcp: Fix a data-race around sysctl_tcp_thin_linear_timeouts.

    In the Linux kernel, the following vulnerability has been resolved: tcp: Fix a data-race around sysctl_tcp_thin_linear_timeouts. While reading sysctl_tcp_thin_linear_timeouts, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader.

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  12. CVE-2022-49574

    Mittel · CVSS 4.7EPSS 0,19%Korrektur verfügbar

    tcp: Fix data-races around sysctl_tcp_recovery.

    In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctl_tcp_recovery. While reading sysctl_tcp_recovery, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers.

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  13. CVE-2022-49573

    Mittel · CVSS 4.7EPSS 0,19%Korrektur verfügbar

    tcp: Fix a data-race around sysctl_tcp_early_retrans.

    In the Linux kernel, the following vulnerability has been resolved: tcp: Fix a data-race around sysctl_tcp_early_retrans. While reading sysctl_tcp_early_retrans, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader.

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  14. CVE-2022-49572

    Mittel · CVSS 4.7EPSS 0,19%Korrektur verfügbar

    tcp: Fix data-races around sysctl_tcp_slow_start_after_idle.

    In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctl_tcp_slow_start_after_idle. While reading sysctl_tcp_slow_start_after_idle, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers.

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  15. CVE-2022-49571

    Mittel · CVSS 4.7EPSS 0,19%Korrektur verfügbar

    tcp: Fix data-races around sysctl_tcp_max_reordering.

    In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctl_tcp_max_reordering. While reading sysctl_tcp_max_reordering, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers.

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  16. CVE-2022-49569

    Mittel · CVSS 5.5EPSS 0,26%Korrektur verfügbar

    spi: bcm2835: bcm2835_spi_handle_err(): fix NULL pointer deref for non DMA transfers

    In the Linux kernel, the following vulnerability has been resolved: spi: bcm2835: bcm2835_spi_handle_err(): fix NULL pointer deref for non DMA transfers In case a IRQ based transfer times out the bcm2835_spi_handle_err() function is called. Since commit 1513ceee70f2 ("spi: bcm2835: Drop dma_pending flag") the TX and RX DMA transfers are unconditionally canceled, leading to NULL pointer derefs if ctlr->dma_tx or ctlr->dma_rx are not set. Fix the NULL pointer deref by checking that ctlr->dma_tx and ctlr->dma_rx are valid pointers before accessing them.

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  17. CVE-2022-49568

    Mittel · CVSS 5.5EPSS 0,3%Korrektur verfügbar

    KVM: Don't null dereference ops->destroy

    In the Linux kernel, the following vulnerability has been resolved: KVM: Don't null dereference ops->destroy A KVM device cleanup happens in either of two callbacks: 1) destroy() which is called when the VM is being destroyed; 2) release() which is called when a device fd is closed. Most KVM devices use 1) but Book3s's interrupt controller KVM devices (XICS, XIVE, XIVE-native) use 2) as they need to close and reopen during the machine execution. The error handling in kvm_ioctl_create_device() assumes destroy() is always defined which leads to NULL dereference as discovered by Syzkaller. This adds a checks for destroy!=NULL and adds a miss

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1092.101~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  18. CVE-2022-49561

    Kritisch · CVSS 9.8EPSS 0,82%Korrektur verfügbar

    netfilter: conntrack: re-fetch conntrack after insertion

    In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: re-fetch conntrack after insertion In case the conntrack is clashing, insertion can free skb->_nfct and set skb->_nfct to the already-confirmed entry. This wasn't found before because the conntrack entry and the extension space used to free'd after an rcu grace period, plus the race needs events enabled to trigger.

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1089.97~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  19. CVE-2022-49554

    Hoch · CVSS 7.8EPSS 0,22%Korrektur verfügbar

    zsmalloc: fix races between asynchronous zspage free and page migration

    In the Linux kernel, the following vulnerability has been resolved: zsmalloc: fix races between asynchronous zspage free and page migration The asynchronous zspage free worker tries to lock a zspage's entire page list without defending against page migration. Since pages which haven't yet been locked can concurrently migrate off the zspage page list while lock_zspage() churns away, lock_zspage() can suffer from a few different lethal races. It can lock a page which no longer belongs to the zspage and unsafely dereference page_private(), it can unsafely dereference a torn pointer to the next page (since there's a data race), and it can obs

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1089.97~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  20. CVE-2022-49544

    Mittel · CVSS 5.5EPSS 0,26%Korrektur verfügbar

    ipw2x00: Fix potential NULL dereference in libipw_xmit()

    In the Linux kernel, the following vulnerability has been resolved: ipw2x00: Fix potential NULL dereference in libipw_xmit() crypt and crypt->ops could be null, so we need to checking null before dereference

    linux-gcp-5.4Betriebssysteme
    • Auf 5.4.0-1089.97~18.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

Prüfen Sie Ihren Server

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

Prüfen Sie Ihren Server →