p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-aws-fips · Seite 152

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 6849

  1. CVE-2022-50670

    Nicht bewertetEPSS 0,24%Keine Korrektur veröffentlicht

    mmc: omap_hsmmc: fix return value check of mmc_add_host()

    In the Linux kernel, the following vulnerability has been resolved: mmc: omap_hsmmc: 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(). Fix this by checking the return value and goto error path wihch will call mmc_free_host().

    Veröffentlicht Aktualisiert
  2. CVE-2022-50668

    Hoch · CVSS 7.5EPSS 0,81%Keine Korrektur veröffentlicht

    ext4: fix deadlock due to mbcache entry corruption

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix deadlock due to mbcache entry corruption When manipulating xattr blocks, we can deadlock infinitely looping inside ext4_xattr_block_set() where we constantly keep finding xattr block for reuse in mbcache but we are unable to reuse it because its reference count is too big. This happens because cache entry for the xattr block is marked as reusable (e_reusable set) although its reference count is too big. When this inconsistency happens, this inconsistent state is kept indefinitely and so ext4_xattr_block_set() keeps retrying indefinitely. The inconsistent state is

    Veröffentlicht Aktualisiert
  3. CVE-2022-50660

    Nicht bewertetEPSS 0,25%Keine Korrektur veröffentlicht

    wifi: ipw2200: fix memory leak in ipw_wdev_init()

    In the Linux kernel, the following vulnerability has been resolved: wifi: ipw2200: fix memory leak in ipw_wdev_init() In the error path of ipw_wdev_init(), exception value is returned, and the memory applied for in the function is not released. Also the memory is not released in ipw_pci_probe(). As a result, memory leakage occurs. So memory release needs to be added to the error path of ipw_wdev_init().

    Veröffentlicht Aktualisiert
  4. CVE-2022-50659

    Nicht bewertetEPSS 0,28%Keine Korrektur veröffentlicht

    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.

    Veröffentlicht Aktualisiert
  5. CVE-2023-53819

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

    amdgpu: validate offset_in_bo of drm_amdgpu_gem_va

    In the Linux kernel, the following vulnerability has been resolved: amdgpu: validate offset_in_bo of drm_amdgpu_gem_va This is motivated by OOB access in amdgpu_vm_update_range when offset_in_bo+map_size overflows. v2: keep the validations in amdgpu_vm_bo_map v3: add the validations to amdgpu_vm_bo_map/amdgpu_vm_bo_replace_map rather than to amdgpu_gem_va_ioctl

    Veröffentlicht Aktualisiert
  6. CVE-2023-53818

    Nicht bewertetEPSS 0,19%Keine Korrektur veröffentlicht

    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.

    Veröffentlicht Aktualisiert
  7. CVE-2023-53817

    Hoch · CVSS 7.5EPSS 0,51%Keine Korrektur veröffentlicht

    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()

    Veröffentlicht Aktualisiert
  8. CVE-2023-53816

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

    drm/amdkfd: fix potential kgd_mem UAFs

    In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: fix potential kgd_mem UAFs kgd_mem pointers returned by kfd_process_device_translate_handle are only guaranteed to be valid while p->mutex is held. As soon as the mutex is unlocked, another thread can free the BO.

    Veröffentlicht Aktualisiert
  9. CVE-2023-53806

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

    drm/amd/display: populate subvp cmd info only for the top pipe

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: populate subvp cmd info only for the top pipe [Why] System restart observed while changing the display resolution to 8k with extended mode. Sytem restart was caused by a page fault. [How] When the driver populates subvp info it did it for both the pipes using vblank which caused an outof bounds array access causing the page fault. added checks to allow the top pipe only to fix this issue.

    Veröffentlicht Aktualisiert
  10. CVE-2023-53804

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

    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

    Veröffentlicht Aktualisiert
  11. CVE-2023-53803

    Hoch · CVSS 8.1EPSS 0,29%Keine Korrektur veröffentlicht

    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.

    Veröffentlicht Aktualisiert
  12. CVE-2023-53802

    Mittel · CVSS 5.1EPSS 0,19%Keine Korrektur veröffentlicht

    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.

    Veröffentlicht Aktualisiert
  13. CVE-2023-53800

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

    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

    Veröffentlicht Aktualisiert
  14. CVE-2023-53799

    Nicht bewertetEPSS 0,21%Keine Korrektur veröffentlicht

    crypto: api - Use work queue in crypto_destroy_instance

    In the Linux kernel, the following vulnerability has been resolved: crypto: api - Use work queue in crypto_destroy_instance The function crypto_drop_spawn expects to be called in process context. However, when an instance is unregistered while it still has active users, the last user may cause the instance to be freed in atomic context. Fix this by delaying the freeing to a work queue.

    Veröffentlicht Aktualisiert
  15. CVE-2023-53796

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

    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.

    Veröffentlicht Aktualisiert
  16. CVE-2023-53794

    Kritisch · CVSS 9.8EPSS 0,51%Keine Korrektur veröffentlicht

    cifs: fix session state check in reconnect to avoid use-after-free issue

    In the Linux kernel, the following vulnerability has been resolved: cifs: fix session state check in reconnect to avoid use-after-free issue Don't collect exiting session in smb2_reconnect_server(), because it will be released soon. Note that the exiting session will stay in server->smb_ses_list until it complete the cifs_free_ipc() and logoff() and then delete itself from the list.

    Veröffentlicht Aktualisiert
  17. CVE-2023-53788

    Nicht bewertetEPSS 0,21%Keine Korrektur veröffentlicht

    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

    Veröffentlicht Aktualisiert
  18. CVE-2023-53786

    Nicht bewertetEPSS 0,23%Keine Korrektur veröffentlicht

    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.

    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 →