p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-aws-5.15 · Seite 159

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 4238

  1. CVE-2024-36016

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

    tty: n_gsm: fix possible out-of-bounds in gsm0_receive()

    In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() Assuming the following: - side A configures the n_gsm in basic option mode - side B sends the header of a basic option mode frame with data length 1 - side A switches to advanced option mode - side B sends 2 data bytes which exceeds gsm->len Reason: gsm->len is not used in advanced option mode. - side A switches to basic option mode - side B keeps sending until gsm0_receive() writes past gsm->buf Reason: Neither gsm->state nor gsm->len have been reset after reconfiguration. Fix this by changing gsm->count to gs

    • Auf 5.15.0-1066.72~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2023-52881

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

    tcp: do not accept ACK of bytes we never sent

    In the Linux kernel, the following vulnerability has been resolved: tcp: do not accept ACK of bytes we never sent This patch is based on a detailed report and ideas from Yepeng Pan and Christian Rossow. ACK seq validation is currently following RFC 5961 5.2 guidelines: The ACK value is considered acceptable only if it is in the range of ((SND.UNA - MAX.SND.WND) <= SEG.ACK <= SND.NXT). All incoming segments whose ACK value doesn't satisfy the above condition MUST be discarded and an ACK sent back. It needs to be noted that RFC 793 on page 72 (fifth check) says: "If the ACK is a duplicate (SEG.ACK < SND.UNA), it can be i

    • Auf 5.15.0-1056.61~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2024-36015

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

    ppdev: Add an error check in register_device

    In the Linux kernel, the following vulnerability has been resolved: ppdev: Add an error check in register_device In register_device, the return value of ida_simple_get is unchecked, in witch ida_simple_get will use an invalid index value. To address this issue, index should be checked after ida_simple_get. When the index value is abnormal, a warning message should be printed, the port should be dropped, and the value should be recorded.

    • Auf 5.15.0-1069.75~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2024-36014

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

    drm/arm/malidp: fix a possible null pointer dereference

    In the Linux kernel, the following vulnerability has been resolved: drm/arm/malidp: fix a possible null pointer dereference In malidp_mw_connector_reset, new memory is allocated with kzalloc, but no check is performed. In order to prevent null pointer dereferencing, ensure that mw_state is checked before calling __drm_atomic_helper_connector_reset.

    • Auf 5.15.0-1069.75~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2023-52880

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

    tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc

    In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc Any unprivileged user can attach N_GSM0710 ldisc, but it requires CAP_NET_ADMIN to create a GSM network anyway. Require initial namespace CAP_NET_ADMIN to do that.

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2023-52878

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

    can: dev: can_put_echo_skb(): don't crash kernel if can_priv::echo_skb is accessed out of bounds

    In the Linux kernel, the following vulnerability has been resolved: can: dev: can_put_echo_skb(): don't crash kernel if can_priv::echo_skb is accessed out of bounds If the "struct can_priv::echoo_skb" is accessed out of bounds, this would cause a kernel crash. Instead, issue a meaningful warning message and return with an error.

    • Auf 5.15.0-1056.61~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2023-52877

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

    usb: typec: tcpm: Fix NULL pointer dereference in tcpm_pd_svdm()

    In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: Fix NULL pointer dereference in tcpm_pd_svdm() It is possible that typec_register_partner() returns ERR_PTR on failure. When port->partner is an error, a NULL pointer dereference may occur as shown below. [91222.095236][ T319] typec port0: failed to register partner (-17) ... [91225.061491][ T319] Unable to handle kernel NULL pointer dereference at virtual address 000000000000039f [91225.274642][ T319] pc : tcpm_pd_data_request+0x310/0x13fc [91225.274646][ T319] lr : tcpm_pd_data_request+0x298/0x13fc [91225.308067][ T319] Call trace: [91225.308070][

    • Auf 5.15.0-1056.61~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2023-52876

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

    clk: mediatek: clk-mt7629-eth: Add check for mtk_alloc_clk_data

    In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: clk-mt7629-eth: Add check for mtk_alloc_clk_data Add the check for the return value of mtk_alloc_clk_data() in order to avoid NULL pointer dereference.

    • Auf 5.15.0-1056.61~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2023-52875

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

    clk: mediatek: clk-mt2701: Add check for mtk_alloc_clk_data

    In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: clk-mt2701: Add check for mtk_alloc_clk_data Add the check for the return value of mtk_alloc_clk_data() in order to avoid NULL pointer dereference.

    • Auf 5.15.0-1056.61~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2023-52873

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

    clk: mediatek: clk-mt6779: Add check for mtk_alloc_clk_data

    In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: clk-mt6779: Add check for mtk_alloc_clk_data Add the check for the return value of mtk_alloc_clk_data() in order to avoid NULL pointer dereference.

    • Auf 5.15.0-1056.61~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2023-52872

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

    tty: n_gsm: fix race condition in status line change on dead connections

    In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: fix race condition in status line change on dead connections gsm_cleanup_mux() cleans up the gsm by closing all DLCIs, stopping all timers, removing the virtual tty devices and clearing the data queues. This procedure, however, may cause subsequent changes of the virtual modem status lines of a DLCI. More data is being added the outgoing data queue and the deleted kick timer is restarted to handle this. At this point many resources have already been removed by the cleanup procedure. Thus, a kernel panic occurs. Fix this by proving in gsm_modem_update() that the

    • Auf 5.15.0-1056.61~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2023-52871

    Hoch · CVSS 7.1EPSS 0,23%Korrektur verfügbar

    soc: qcom: llcc: Handle a second device without data corruption

    In the Linux kernel, the following vulnerability has been resolved: soc: qcom: llcc: Handle a second device without data corruption Usually there is only one llcc device. But if there were a second, even a failed probe call would modify the global drv_data pointer. So check if drv_data is valid before overwriting it.

    • Auf 5.15.0-1056.61~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2023-52870

    Mittel · CVSS 4.1EPSS 0,22%Korrektur verfügbar

    clk: mediatek: clk-mt6765: Add check for mtk_alloc_clk_data

    In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: clk-mt6765: Add check for mtk_alloc_clk_data Add the check for the return value of mtk_alloc_clk_data() in order to avoid NULL pointer dereference.

    • Auf 5.15.0-1056.61~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2023-52869

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

    pstore/platform: Add check for kstrdup

    In the Linux kernel, the following vulnerability has been resolved: pstore/platform: Add check for kstrdup Add check for the return value of kstrdup() and return the error if it fails in order to avoid NULL pointer dereference.

    • Auf 5.15.0-1056.61~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2023-52868

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

    thermal: core: prevent potential string overflow

    In the Linux kernel, the following vulnerability has been resolved: thermal: core: prevent potential string overflow The dev->id value comes from ida_alloc() so it's a number between zero and INT_MAX. If it's too high then these sprintf()s will overflow.

    • Auf 5.15.0-1056.61~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2023-52865

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

    clk: mediatek: clk-mt6797: Add check for mtk_alloc_clk_data

    In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: clk-mt6797: Add check for mtk_alloc_clk_data Add the check for the return value of mtk_alloc_clk_data() in order to avoid NULL pointer dereference.

    • Auf 5.15.0-1056.61~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2023-52864

    Hoch · CVSS 7EPSS 0,27%Korrektur verfügbar

    platform/x86: wmi: Fix opening of char device

    In the Linux kernel, the following vulnerability has been resolved: platform/x86: wmi: Fix opening of char device Since commit fa1f68db6ca7 ("drivers: misc: pass miscdevice pointer via file private data"), the miscdevice stores a pointer to itself inside filp->private_data, which means that private_data will not be NULL when wmi_char_open() is called. This might cause memory corruption should wmi_char_open() be unable to find its driver, something which can happen when the associated WMI device is deleted in wmi_free_devices(). Fix the problem by using the miscdevice pointer to retrieve the WMI device data associated with a char device usi

    • Auf 5.15.0-1056.61~20.04.1 aktualisieren
    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 →