p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-oracle · Seite 12

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 3435

  1. CVE-2022-50659

    Nicht bewertetEPSS 0,28%Korrektur verfügbar

    hwrng: geode - Fix PCI device refcount leak

    In the Linux kernel, the following vulnerability has been resolved: hwrng: geode - Fix PCI device refcount leak for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL. If we break for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count. We add a new struct 'amd_geode_priv' to record pointer of the pci_dev and membase, and then add missing pci_dev_put() for the normal and error path.

    • Auf 5.4.0-1094.103 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2023-53820

    Mittel · CVSS 6.7EPSS 0,28%Korrektur verfügbar

    loop: loop_set_status_from_info() check before assignment

    In the Linux kernel, the following vulnerability has been resolved: loop: loop_set_status_from_info() check before assignment In loop_set_status_from_info(), lo->lo_offset and lo->lo_sizelimit should be checked before reassignment, because if an overflow error occurs, the original correct value will be changed to the wrong value, and it will not be changed back. More, the original patch did not solve the problem, the value was set and ioctl returned an error, but the subsequent io used the value in the loop driver, which still caused an alarm: loop_handle_cmd do_req_filebacked loff_t pos = ((loff_t) blk_rq_pos(rq) << 9) + lo->lo_offset

    • Auf 5.4.0-1127.136 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2023-53818

    Nicht bewertetEPSS 0,19%Korrektur verfügbar

    ARM: zynq: Fix refcount leak in zynq_early_slcr_init

    In the Linux kernel, the following vulnerability has been resolved: ARM: zynq: Fix refcount leak in zynq_early_slcr_init of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on error path. Add missing of_node_put() to avoid refcount leak.

    • Auf 5.4.0-1103.112 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2023-53817

    Hoch · CVSS 7.5EPSS 0,51%Korrektur verfügbar

    crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui()

    In the Linux kernel, the following vulnerability has been resolved: crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui() During NVMeTCP Authentication a controller can trigger a kernel oops by specifying the 8192 bit Diffie Hellman group and passing a correctly sized, but zeroed Diffie Hellamn value. mpi_cmp_ui() was detecting this if the second parameter was 0, but 1 is passed from dh_is_pubkey_valid(). This causes the null pointer u->d to be dereferenced towards the end of mpi_cmp_ui()

    • Auf 5.4.0-1115.124 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2023-53804

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

    nilfs2: fix use-after-free bug of nilfs_root in nilfs_evict_inode()

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix use-after-free bug of nilfs_root in nilfs_evict_inode() During unmount process of nilfs2, nothing holds nilfs_root structure after nilfs2 detaches its writer in nilfs_detach_log_writer(). However, since nilfs_evict_inode() uses nilfs_root for some cleanup operations, it may cause use-after-free read if inodes are left in "garbage_list" and released by nilfs_dispose_list() at the end of nilfs_detach_log_writer(). Fix this issue by modifying nilfs_evict_inode() to only clear inode without additional metadata changes that use nilfs_root if the file system is degr

    • Auf 5.4.0-1108.117 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2023-53803

    Hoch · CVSS 8.1EPSS 0,29%Korrektur verfügbar

    scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process()

    In the Linux kernel, the following vulnerability has been resolved: scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process() A fix for: BUG: KASAN: slab-out-of-bounds in ses_enclosure_data_process+0x949/0xe30 [ses] Read of size 1 at addr ffff88a1b043a451 by task systemd-udevd/3271 Checking after (and before in next loop) addl_desc_ptr[1] is sufficient, we expect the size to be sanitized before first access to addl_desc_ptr[1]. Make sure we don't walk beyond end of page.

    • Auf 5.4.0-1103.112 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2023-53802

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

    wifi: ath9k: htc_hst: free skb in ath9k_htc_rx_msg() if there is no callback function

    In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: htc_hst: free skb in ath9k_htc_rx_msg() if there is no callback function It is stated that ath9k_htc_rx_msg() either frees the provided skb or passes its management to another callback function. However, the skb is not freed in case there is no another callback function, and Syzkaller was able to cause a memory leak. Also minor comment fix. Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

    • Auf 5.4.0-1103.112 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2023-53800

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

    ubi: Fix use-after-free when volume resizing failed

    In the Linux kernel, the following vulnerability has been resolved: ubi: Fix use-after-free when volume resizing failed There is an use-after-free problem reported by KASAN: ================================================================== BUG: KASAN: use-after-free in ubi_eba_copy_table+0x11f/0x1c0 [ubi] Read of size 8 at addr ffff888101eec008 by task ubirsvol/4735 CPU: 2 PID: 4735 Comm: ubirsvol Not tainted 6.1.0-rc1-00003-g84fa3304a7fc-dirty #14 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44 print_report+0x171/0x472 kasan_repor

    • Auf 5.4.0-1103.112 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2023-53797

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

    HID: wacom: Use ktime_t rather than int when dealing with timestamps

    In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Use ktime_t rather than int when dealing with timestamps Code which interacts with timestamps needs to use the ktime_t type returned by functions like ktime_get. The int type does not offer enough space to store these values, and attempting to use it is a recipe for problems. In this particular case, overflows would occur when calculating/storing timestamps leading to incorrect values being reported to userspace. In some cases these bad timestamps cause input handling in userspace to appear hung.

    • Auf 5.4.0-1112.121 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2023-53796

    Niedrig · CVSS 0EPSS 0,21%Korrektur verfügbar

    f2fs: fix information leak in f2fs_move_inline_dirents()

    In the Linux kernel, the following vulnerability has been resolved: f2fs: fix information leak in f2fs_move_inline_dirents() When converting an inline directory to a regular one, f2fs is leaking uninitialized memory to disk because it doesn't initialize the entire directory block. Fix this by zero-initializing the block. This bug was introduced by commit 4ec17d688d74 ("f2fs: avoid unneeded initializing when converting inline dentry"), which didn't consider the security implications of leaking uninitialized memory to disk. This was found by running xfstest generic/435 on a KMSAN-enabled kernel.

    • Auf 5.4.0-1103.112 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2023-53788

    Nicht bewertetEPSS 0,21%Korrektur verfügbar

    ALSA: hda/ca0132: fixup buffer overrun at tuning_ctl_set()

    In the Linux kernel, the following vulnerability has been resolved: ALSA: hda/ca0132: fixup buffer overrun at tuning_ctl_set() tuning_ctl_set() might have buffer overrun at (X) if it didn't break from loop by matching (A). static int tuning_ctl_set(...) { for (i = 0; i < TUNING_CTLS_COUNT; i++) (A) if (nid == ca0132_tuning_ctls[i].nid) break; snd_hda_power_up(...); (X) dspio_set_param(..., ca0132_tuning_ctls[i].mid, ...); snd_hda_power_down(...); ^ return 1; } We will get below error by cppcheck sound/pci/hda/patch_ca0132.c:4229:2: note: After for loop, i has value 12 for (i = 0; i < TUNING_CTLS_COUN

    • Auf 5.4.0-1106.115 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2023-53786

    Nicht bewertetEPSS 0,23%Korrektur verfügbar

    dm flakey: fix a crash with invalid table line

    In the Linux kernel, the following vulnerability has been resolved: dm flakey: fix a crash with invalid table line This command will crash with NULL pointer dereference: dmsetup create flakey --table \ "0 `blockdev --getsize /dev/ram0` flakey /dev/ram0 0 0 1 2 corrupt_bio_byte 512" Fix the crash by checking if arg_name is non-NULL before comparing it.

    • Auf 5.4.0-1108.117 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2023-53783

    Nicht bewertetEPSS 0,21%Korrektur verfügbar

    blk-iocost: fix divide by 0 error in calc_lcoefs()

    In the Linux kernel, the following vulnerability has been resolved: blk-iocost: fix divide by 0 error in calc_lcoefs() echo max of u64 to cost.model can cause divide by 0 error. # echo 8:0 rbps=18446744073709551615 > /sys/fs/cgroup/io.cost.model divide error: 0000 [#1] PREEMPT SMP RIP: 0010:calc_lcoefs+0x4c/0xc0 Call Trace: <TASK> ioc_refresh_params+0x2b3/0x4f0 ioc_cost_model_write+0x3cb/0x4c0 ? _copy_from_iter+0x6d/0x6c0 ? kernfs_fop_write_iter+0xfc/0x270 cgroup_file_write+0xa0/0x200 kernfs_fop_write_iter+0x17d/0x270 vfs_write+0x414/0x620 ksys_write+0x73/0x160 __x64_sys_write+0x1e/0x30 do_syscall_

    • Auf 5.4.0-1103.112 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2023-53782

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

    dccp: Fix out of bounds access in DCCP error handler

    In the Linux kernel, the following vulnerability has been resolved: dccp: Fix out of bounds access in DCCP error handler There was a previous attempt to fix an out-of-bounds access in the DCCP error handlers, but that fix assumed that the error handlers only want to access the first 8 bytes of the DCCP header. Actually, they also look at the DCCP sequence number, which is stored beyond 8 bytes, so an explicit pskb_may_pull() is required.

    • Auf 5.4.0-1115.124 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2022-50656

    Hoch · CVSS 8.1EPSS 0,34%Korrektur verfügbar

    nfc: pn533: Clear nfc_target before being used

    In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: Clear nfc_target before being used Fix a slab-out-of-bounds read that occurs in nla_put() called from nfc_genl_send_target() when target->sensb_res_len, which is duplicated from an nfc_target in pn533, is too large as the nfc_target is not properly initialized and retains garbage values. Clear nfc_targets with memset() before they are used. Found by a modified version of syzkaller. BUG: KASAN: slab-out-of-bounds in nla_put Call Trace: memcpy nla_put nfc_genl_dump_targets genl_lock_dumpit netlink_dump __netlink_dump_start genl_family_rcv_msg_dumpit genl

    • Auf 5.4.0-1094.103 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2022-50655

    Mittel · CVSS 4.8EPSS 0,21%Korrektur verfügbar

    ppp: associate skb with a device at tx

    In the Linux kernel, the following vulnerability has been resolved: ppp: associate skb with a device at tx Syzkaller triggered flow dissector warning with the following: r0 = openat$ppp(0xffffffffffffff9c, &(0x7f0000000000), 0xc0802, 0x0) ioctl$PPPIOCNEWUNIT(r0, 0xc004743e, &(0x7f00000000c0)) ioctl$PPPIOCSACTIVE(r0, 0x40107446, &(0x7f0000000240)={0x2, &(0x7f0000000180)=[{0x20, 0x0, 0x0, 0xfffff034}, {0x6}]}) pwritev(r0, &(0x7f0000000040)=[{&(0x7f0000000140)='\x00!', 0x2}], 0x1, 0x0, 0x0) [ 9.485814] WARNING: CPU: 3 PID: 329 at net/core/flow_dissector.c:1016 __skb_flow_dissect+0x1ee0/0x1fa0 [ 9.485929] skb_get_poff+0x53/0xa0 [ 9.

    • Auf 5.4.0-1094.103 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2022-50653

    Nicht bewertetEPSS 0,21%Korrektur verfügbar

    mmc: atmel-mci: fix return value check of mmc_add_host()

    In the Linux kernel, the following vulnerability has been resolved: mmc: atmel-mci: fix return value check of mmc_add_host() mmc_add_host() may return error, if we ignore its return value, it will lead two issues: 1. The memory that allocated in mmc_alloc_host() is leaked. 2. In the remove() path, mmc_remove_host() will be called to delete device, but it's not added yet, it will lead a kernel crash because of null-ptr-deref in device_del(). So fix this by checking the return value and calling mmc_free_host() in the error path.

    • Auf 5.4.0-1094.103 aktualisieren
    Veröffentlicht Aktualisiert
  18. CVE-2022-50652

    Nicht bewertetEPSS 0,23%Korrektur verfügbar

    uio: uio_dmem_genirq: Fix missing unlock in irq configuration

    In the Linux kernel, the following vulnerability has been resolved: uio: uio_dmem_genirq: Fix missing unlock in irq configuration Commit b74351287d4b ("uio: fix a sleep-in-atomic-context bug in uio_dmem_genirq_irqcontrol()") started calling disable_irq() without holding the spinlock because it can sleep. However, that fix introduced another bug: if interrupt is already disabled and a new disable request comes in, then the spinlock is not unlocked: root@localhost:~# printf '\x00\x00\x00\x00' > /dev/uio0 root@localhost:~# printf '\x00\x00\x00\x00' > /dev/uio0 root@localhost:~# [ 14.851538] BUG: scheduling while atomic: bash/223/0x00000002

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