p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-ibm · Seite 109

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 3088

  1. CVE-2023-52730

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

    mmc: sdio: fix possible resource leaks in some error paths

    In the Linux kernel, the following vulnerability has been resolved: mmc: sdio: fix possible resource leaks in some error paths If sdio_add_func() or sdio_init_func() fails, sdio_remove_func() can not release the resources, because the sdio function is not presented in these two cases, it won't call of_node_put() or put_device(). To fix these leaks, make sdio_func_present() only control whether device_del() needs to be called or not, then always call of_node_put() and put_device(). In error case in sdio_init_func(), the reference of 'card->dev' is not get, to avoid redundant put in sdio_free_func_cis(), move the get_device() to sdio_alloc_

    • Auf 5.4.0-1049.54 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2023-52708

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

    mmc: mmc_spi: fix error handling in mmc_spi_probe()

    In the Linux kernel, the following vulnerability has been resolved: mmc: mmc_spi: fix error handling in mmc_spi_probe() If mmc_add_host() fails, it doesn't need to call mmc_remove_host(), or it will cause null-ptr-deref, because of deleting a not added device in mmc_remove_host(). To fix this, goto label 'fail_glue_init', if mmc_add_host() fails, and change the label 'fail_add_host' to 'fail_gpiod_request'.

    • Auf 5.4.0-1049.54 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2023-52707

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

    sched/psi: Fix use-after-free in ep_remove_wait_queue()

    In the Linux kernel, the following vulnerability has been resolved: sched/psi: Fix use-after-free in ep_remove_wait_queue() If a non-root cgroup gets removed when there is a thread that registered trigger and is polling on a pressure file within the cgroup, the polling waitqueue gets freed in the following path: do_rmdir cgroup_rmdir kernfs_drain_open_files cgroup_file_release cgroup_pressure_release psi_trigger_destroy However, the polling thread still has a reference to the pressure file and will access the freed waitqueue when the file is closed or upon exit: fput ep_eventpoll_release ep_fr

    • Auf 5.4.0-1049.54 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2023-52705

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

    nilfs2: fix underflow in second superblock position calculations

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix underflow in second superblock position calculations Macro NILFS_SB2_OFFSET_BYTES, which computes the position of the second superblock, underflows when the argument device size is less than 4096 bytes. Therefore, when using this macro, it is necessary to check in advance that the device size is not less than a lower limit, or at least that underflow does not occur. The current nilfs2 implementation lacks this check, causing out-of-bound block access when mounting devices smaller than 4096 bytes: I/O error, dev loop0, sector 36028797018963960 op 0x0:(READ) f

    • Auf 5.4.0-1049.54 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2023-52703

    Niedrig · CVSS 3.3EPSS 0,25%Korrektur verfügbar

    net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path

    In the Linux kernel, the following vulnerability has been resolved: net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path syzbot reported that act_len in kalmia_send_init_packet() is uninitialized when passing it to the first usb_bulk_msg error path. Jiri Pirko noted that it's pointless to pass it in the error path, and that the value that would be printed in the second error path would be the value of act_len from the first call to usb_bulk_msg.[1] With this in mind, let's just not pass act_len to the usb_bulk_msg error paths. 1: https://lore.kernel.org/lkml/Y9pY61y1nwTuzMOa@nanopsycho/

    • Auf 5.4.0-1049.54 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2022-48708

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

    pinctrl: single: fix potential NULL dereference

    In the Linux kernel, the following vulnerability has been resolved: pinctrl: single: fix potential NULL dereference Added checking of pointer "function" in pcs_set_mux(). pinmux_generic_get_function() can return NULL and the pointer "function" was dereferenced without checking against NULL. Found by Linux Verification Center (linuxtesting.org) with SVACE.

    • Auf 5.4.0-1049.54 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2021-47431

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

    drm/amdgpu: fix gart.bo pin_count leak

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix gart.bo pin_count leak gmc_v{9,10}_0_gart_disable() isn't called matched with correspoding gart_enbale function in SRIOV case. This will lead to gart.bo pin_count leak on driver unload.

    • Auf 5.4.0-1010.11 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2021-47425

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

    i2c: acpi: fix resource leak in reconfiguration device addition

    In the Linux kernel, the following vulnerability has been resolved: i2c: acpi: fix resource leak in reconfiguration device addition acpi_i2c_find_adapter_by_handle() calls bus_find_device() which takes a reference on the adapter which is never released which will result in a reference count leak and render the adapter unremovable. Make sure to put the adapter after creating the client in the same manner that we do for OF. [wsa: fixed title]

    • Auf 5.4.0-1010.11 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2021-47424

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

    i40e: Fix freeing of uninitialized misc IRQ vector

    In the Linux kernel, the following vulnerability has been resolved: i40e: Fix freeing of uninitialized misc IRQ vector When VSI set up failed in i40e_probe() as part of PF switch set up driver was trying to free misc IRQ vectors in i40e_clear_interrupt_scheme and produced a kernel Oops: Trying to free already-free IRQ 266 WARNING: CPU: 0 PID: 5 at kernel/irq/manage.c:1731 __free_irq+0x9a/0x300 Workqueue: events work_for_cpu_fn RIP: 0010:__free_irq+0x9a/0x300 Call Trace: ? synchronize_irq+0x3a/0xa0 free_irq+0x2e/0x60 i40e_clear_interrupt_scheme+0x53/0x190 [i40e] i40e_probe.part.108+0x134b/0x1a40 [i40e] ? kmem_c

    • Auf 5.4.0-1010.11 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2021-47423

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

    drm/nouveau/debugfs: fix file release memory leak

    In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/debugfs: fix file release memory leak When using single_open() for opening, single_release() should be called, otherwise the 'op' allocated in single_open() will be leaked.

    • Auf 5.4.0-1010.11 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2021-47419

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

    net/sched: sch_taprio: properly cancel timer from taprio_destroy()

    In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_taprio: properly cancel timer from taprio_destroy() There is a comment in qdisc_create() about us not calling ops->reset() in some cases. err_out4: /* * Any broken qdiscs that would require a ops->reset() here? * The qdisc was never in action so it shouldn't be necessary. */ As taprio sets a timer before actually receiving a packet, we need to cancel it from ops->destroy, just in case ops->reset has not been called. syzbot reported: ODEBUG: free active (active state 0) object type: hrtimer hint: advance_sched+0x0/0x9a0 arch/x86/include/asm/atomic64

    • Auf 5.4.0-1010.11 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2021-47418

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

    net_sched: fix NULL deref in fifo_set_limit()

    In the Linux kernel, the following vulnerability has been resolved: net_sched: fix NULL deref in fifo_set_limit() syzbot reported another NULL deref in fifo_set_limit() [1] I could repro the issue with : unshare -n tc qd add dev lo root handle 1:0 tbf limit 200000 burst 70000 rate 100Mbit tc qd replace dev lo parent 1:0 pfifo_fast tc qd change dev lo root handle 1:0 tbf limit 300000 burst 70000 rate 100Mbit pfifo_fast does not have a change() operation. Make fifo_set_limit() more robust about this. [1] BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 1cf99067 P4D 1cf99067 PUD 7ca49067 PMD 0 Oops: 0010 [#1] PREEMPT SMP

    • Auf 5.4.0-1010.11 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2021-47416

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

    phy: mdio: fix memory leak

    In the Linux kernel, the following vulnerability has been resolved: phy: mdio: fix memory leak Syzbot reported memory leak in MDIO bus interface, the problem was in wrong state logic. MDIOBUS_ALLOCATED indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiobus_register() fails, but device_register() was called In case of device_register() has been called we should call put_device() to correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of MDIOBUS_ALLOCATED state To avoid this behaviour we need to set bus->state to MDIOBUS_UNREGISTERED _before_ calling device_registe

    • Auf 5.4.0-1010.11 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2021-47409

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

    usb: dwc2: check return value after calling platform_get_resource()

    In the Linux kernel, the following vulnerability has been resolved: usb: dwc2: check return value after calling platform_get_resource() It will cause null-ptr-deref if platform_get_resource() returns NULL, we need check the return value.

    • Auf 5.4.0-1010.11 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2021-47405

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

    HID: usbhid: free raw_report buffers in usbhid_stop

    In the Linux kernel, the following vulnerability has been resolved: HID: usbhid: free raw_report buffers in usbhid_stop Free the unsent raw_report buffers when the device is removed. Fixes a memory leak reported by syzbot at: https://syzkaller.appspot.com/bug?id=7b4fa7cb1a7c2d3342a2a8a6c53371c8c418ab47

    • Auf 5.4.0-1008.9 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2021-47404

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

    HID: betop: fix slab-out-of-bounds Write in betop_probe

    In the Linux kernel, the following vulnerability has been resolved: HID: betop: fix slab-out-of-bounds Write in betop_probe Syzbot reported slab-out-of-bounds Write bug in hid-betopff driver. The problem is the driver assumes the device must have an input report but some malicious devices violate this assumption. So this patch checks hid_device's input is non empty before it's been used.

    • Auf 5.4.0-1008.9 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2021-47403

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

    ipack: ipoctal: fix module reference leak

    In the Linux kernel, the following vulnerability has been resolved: ipack: ipoctal: fix module reference leak A reference to the carrier module was taken on every open but was only released once when the final reference to the tty struct was dropped. Fix this by taking the module reference and initialising the tty driver data when installing the tty.

    • Auf 5.4.0-1008.9 aktualisieren
    Veröffentlicht Aktualisiert
  18. CVE-2021-47402

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

    net: sched: flower: protect fl_walk() with rcu

    In the Linux kernel, the following vulnerability has been resolved: net: sched: flower: protect fl_walk() with rcu Patch that refactored fl_walk() to use idr_for_each_entry_continue_ul() also removed rcu protection of individual filters which causes following use-after-free when filter is deleted concurrently. Fix fl_walk() to obtain rcu read lock while iterating and taking the filter reference and temporary release the lock while calling arg->fn() callback that can sleep. KASAN trace: [ 352.773640] ================================================================== [ 352.775041] BUG: KASAN: use-after-free in fl_walk+0x159/0x240 [cls_flo

    • Auf 5.4.0-1008.9 aktualisieren
    Veröffentlicht Aktualisiert
  19. CVE-2021-47401

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

    ipack: ipoctal: fix stack information leak

    In the Linux kernel, the following vulnerability has been resolved: ipack: ipoctal: fix stack information leak The tty driver name is used also after registering the driver and must specifically not be allocated on the stack to avoid leaking information to user space (or triggering an oops). Drivers should not try to encode topology information in the tty device name but this one snuck in through staging without anyone noticing and another driver has since copied this malpractice. Fixing the ABI is a separate issue, but this at least plugs the security hole.

    • Auf 5.4.0-1008.9 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 →