p PatchFirst

PatchFirst · Свежие уязвимости

Уязвимости linux-fips · Страница 131

За последние 30 дней в linux-fips опубликовано уязвимостей: 266; в каталоге KEV: 0.

Фильтры уязвимостей
Сбросить фильтры

Уязвимостей: 5095

  1. CVE-2023-53337

    Средний · CVSS 5.5EPSS 0,21%Нет опубликованного исправления

    nilfs2: do not write dirty data after degenerating to read-only

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not write dirty data after degenerating to read-only According to syzbot's report, mark_buffer_dirty() called from nilfs_segctor_do_construct() outputs a warning with some patterns after nilfs2 detects metadata corruption and degrades to read-only mode. After such read-only degeneration, page cache data may be cleared through nilfs_clear_dirty_page() which may also clear the uptodate flag for their buffer heads. However, even after the degeneration, log writes are still performed by unmount processing etc., which causes mark_buffer_dirty() to be called for buff

    Опубликовано Обновлено
  2. CVE-2022-50368

    Высокий · CVSS 7.8EPSS 0,22%Нет опубликованного исправления

    drm/msm/dsi: fix memory corruption with too many bridges

    In the Linux kernel, the following vulnerability has been resolved: drm/msm/dsi: fix memory corruption with too many bridges Add the missing sanity check on the bridge counter to avoid corrupting data beyond the fixed-sized bridge array in case there are ever more than eight bridges. Patchwork: https://patchwork.freedesktop.org/patch/502668/

    Опубликовано Обновлено
  3. CVE-2022-50367

    Высокий · CVSS 7.8EPSS 0,22%Нет опубликованного исправления

    fs: fix UAF/GPF bug in nilfs_mdt_destroy

    In the Linux kernel, the following vulnerability has been resolved: fs: fix UAF/GPF bug in nilfs_mdt_destroy In alloc_inode, inode_init_always() could return -ENOMEM if security_inode_alloc() fails, which causes inode->i_private uninitialized. Then nilfs_is_metadata_file_inode() returns true and nilfs_free_inode() wrongly calls nilfs_mdt_destroy(), which frees the uninitialized inode->i_private and leads to crashes(e.g., UAF/GPF). Fix this by moving security_inode_alloc just prior to this_cpu_inc(nr_inodes)

    Опубликовано Обновлено
  4. CVE-2022-50366

    Высокий · CVSS 7.1EPSS 0,22%Нет опубликованного исправления

    powercap: intel_rapl: fix UBSAN shift-out-of-bounds issue

    In the Linux kernel, the following vulnerability has been resolved: powercap: intel_rapl: fix UBSAN shift-out-of-bounds issue When value < time_unit, the parameter of ilog2() will be zero and the return value is -1. u64(-1) is too large for shift exponent and then will trigger shift-out-of-bounds: shift exponent 18446744073709551615 is too large for 32-bit type 'int' Call Trace: rapl_compute_time_window_core rapl_write_data_raw set_time_window store_constraint_time_window_us

    Опубликовано Обновлено
  5. CVE-2022-50364

    Средний · CVSS 5.5EPSS 0,21%Нет опубликованного исправления

    i2c: mux: reg: check return value after calling platform_get_resource()

    In the Linux kernel, the following vulnerability has been resolved: i2c: mux: reg: check return value after calling platform_get_resource() It will cause null-ptr-deref in resource_size(), if platform_get_resource() returns NULL, move calling resource_size() after devm_ioremap_resource() that will check 'res' to avoid null-ptr-deref. And use devm_platform_get_and_ioremap_resource() to simplify code.

    Опубликовано Обновлено
  6. CVE-2022-50359

    Средний · CVSS 5.5EPSS 0,21%Нет опубликованного исправления

    media: cx88: Fix a null-ptr-deref bug in buffer_prepare()

    In the Linux kernel, the following vulnerability has been resolved: media: cx88: Fix a null-ptr-deref bug in buffer_prepare() When the driver calls cx88_risc_buffer() to prepare the buffer, the function call may fail, resulting in a empty buffer and null-ptr-deref later in buffer_queue(). The following log can reveal it: [ 41.822762] general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI [ 41.824488] KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] [ 41.828027] RIP: 0010:buffer_queue+0xc2/0x500 [ 41.836311] Call Trace: [ 41.836945] __enqueue_in_driv

    Опубликовано Обновлено
  7. CVE-2022-50358

    Средний · CVSS 4.2EPSS 0,29%Нет опубликованного исправления

    brcmfmac: return error when getting invalid max_flowrings from dongle

    In the Linux kernel, the following vulnerability has been resolved: brcmfmac: return error when getting invalid max_flowrings from dongle When firmware hit trap at initialization, host will read abnormal max_flowrings number from dongle, and it will cause kernel panic when doing iowrite to initialize dongle ring. To detect this error at early stage, we directly return error when getting invalid max_flowrings(>256).

    Опубликовано Обновлено
  8. CVE-2022-50356

    Средний · CVSS 5.5EPSS 0,21%Нет опубликованного исправления

    net: sched: sfb: fix null pointer access issue when sfb_init() fails

    In the Linux kernel, the following vulnerability has been resolved: net: sched: sfb: fix null pointer access issue when sfb_init() fails When the default qdisc is sfb, if the qdisc of dev_queue fails to be inited during mqprio_init(), sfb_reset() is invoked to clear resources. In this case, the q->qdisc is NULL, and it will cause gpf issue. The process is as follows: qdisc_create_dflt() sfb_init() tcf_block_get() --->failed, q->qdisc is NULL ... qdisc_put() ... sfb_reset() qdisc_reset(q->qdisc) --->q->qdisc is NULL ops = qdisc->ops The following is the Call Trace information: general protection fault, probably

    Опубликовано Обновлено
  9. CVE-2022-50353

    Средний · CVSS 5.5EPSS 0,2%Нет опубликованного исправления

    mmc: wmt-sdmmc: fix return value check of mmc_add_host()

    In the Linux kernel, the following vulnerability has been resolved: mmc: wmt-sdmmc: fix return value check of mmc_add_host() mmc_add_host() may return error, if we ignore its return value, the memory that allocated in mmc_alloc_host() will be leaked and it will lead a kernel crash because of deleting not added device in the remove path. So fix this by checking the return value and goto error path which will call mmc_free_host(), besides, clk_disable_unprepare() also needs be called.

    Опубликовано Обновлено
  10. CVE-2023-53333

    Высокий · CVSS 8.2EPSS 0,28%Нет опубликованного исправления

    netfilter: conntrack: dccp: copy entire header to stack buffer, not just basic one

    In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: dccp: copy entire header to stack buffer, not just basic one Eric Dumazet says: nf_conntrack_dccp_packet() has an unique: dh = skb_header_pointer(skb, dataoff, sizeof(_dh), &_dh); And nothing more is 'pulled' from the packet, depending on the content. dh->dccph_doff, and/or dh->dccph_x ...) So dccp_ack_seq() is happily reading stuff past the _dh buffer. BUG: KASAN: stack-out-of-bounds in nf_conntrack_dccp_packet+0x1134/0x11c0 Read of size 4 at addr ffff000128f66e0c by task syz-executor.2/29371 [..] Fix this by increasing the stack buffer

    Опубликовано Обновлено
  11. CVE-2023-53331

    Высокий · CVSS 7.8EPSS 0,16%Нет опубликованного исправления

    pstore/ram: Check start of empty przs during init

    In the Linux kernel, the following vulnerability has been resolved: pstore/ram: Check start of empty przs during init After commit 30696378f68a ("pstore/ram: Do not treat empty buffers as valid"), initialization would assume a prz was valid after seeing that the buffer_size is zero (regardless of the buffer start position). This unchecked start value means it could be outside the bounds of the buffer, leading to future access panics when written to: sysdump_panic_event+0x3b4/0x5b8 atomic_notifier_call_chain+0x54/0x90 panic+0x1c8/0x42c die+0x29c/0x2a8 die_kernel_fault+0x68/0x78 __do_kernel_fault+0x1c4/0x1e0 do_bad_area+0x40/0x100 do

    Опубликовано Обновлено
  12. CVE-2023-53330

    Средний · CVSS 5.5EPSS 0,15%Нет опубликованного исправления

    caif: fix memory leak in cfctrl_linkup_request()

    In the Linux kernel, the following vulnerability has been resolved: caif: fix memory leak in cfctrl_linkup_request() When linktype is unknown or kzalloc failed in cfctrl_linkup_request(), pkt is not released. Add release process to error path.

    Опубликовано Обновлено
  13. CVE-2023-53322

    Высокий · CVSS 8.8EPSS 0,21%Нет опубликованного исправления

    scsi: qla2xxx: Wait for io return on terminate rport

    In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Wait for io return on terminate rport System crash due to use after free. Current code allows terminate_rport_io to exit before making sure all IOs has returned. For FCP-2 device, IO's can hang on in HW because driver has not tear down the session in FW at first sign of cable pull. When dev_loss_tmo timer pops, terminate_rport_io is called and upper layer is about to free various resources. Terminate_rport_io trigger qla to do the final cleanup, but the cleanup might not be fast enough where it leave qla still holding on to the same resource. Wait for IO's t

    Опубликовано Обновлено
  14. CVE-2023-53318

    Средний · CVSS 5.5EPSS 0,16%Нет опубликованного исправления

    recordmcount: Fix memory leaks in the uwrite function

    In the Linux kernel, the following vulnerability has been resolved: recordmcount: Fix memory leaks in the uwrite function Common realloc mistake: 'file_append' nulled but not freed upon failure

    Опубликовано Обновлено
  15. CVE-2023-53317

    Средний · CVSS 5.5EPSS 0,16%Нет опубликованного исправления

    ext4: fix WARNING in mb_find_extent

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix WARNING in mb_find_extent Syzbot found the following issue: EXT4-fs: Warning: mounting with data=journal disables delayed allocation, dioread_nolock, O_DIRECT and fast_commit support! EXT4-fs (loop0): orphan cleanup on readonly fs ------------[ cut here ]------------ WARNING: CPU: 1 PID: 5067 at fs/ext4/mballoc.c:1869 mb_find_extent+0x8a1/0xe30 Modules linked in: CPU: 1 PID: 5067 Comm: syz-executor307 Not tainted 6.2.0-rc1-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 RIP: 0010:mb_find_extent+0x8a1/0xe30 fs

    Опубликовано Обновлено
  16. CVE-2023-53314

    Высокий · CVSS 7.8EPSS 0,17%Нет опубликованного исправления

    fbdev/ep93xx-fb: Do not assign to struct fb_info.dev

    In the Linux kernel, the following vulnerability has been resolved: fbdev/ep93xx-fb: Do not assign to struct fb_info.dev Do not assing the Linux device to struct fb_info.dev. The call to register_framebuffer() initializes the field to the fbdev device. Drivers should not override its value. Fixes a bug where the driver incorrectly decreases the hardware device's reference counter and leaks the fbdev device. v2: * add Fixes tag (Dan)

    Опубликовано Обновлено
  17. CVE-2023-53313

    Средний · CVSS 5.5EPSS 0,16%Нет опубликованного исправления

    md/raid10: fix wrong setting of max_corr_read_errors

    In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix wrong setting of max_corr_read_errors There is no input check when echo md/max_read_errors and overflow might occur. Add check of input number.

    Опубликовано Обновлено
  18. CVE-2023-53311

    Высокий · CVSS 7.8EPSS 0,16%Нет опубликованного исправления

    nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput During unmount process of nilfs2, nothing holds nilfs_root structure after nilfs2 detaches its writer in nilfs_detach_log_writer(). Previously, nilfs_evict_inode() could cause use-after-free read for nilfs_root if inodes are left in "garbage_list" and released by nilfs_dispose_list at the end of nilfs_detach_log_writer(), and this bug was fixed by commit 9b5a04ac3ad9 ("nilfs2: fix use-after-free bug of nilfs_root in nilfs_evict_inode()"). However, it turned out that there is another possibility of UAF in

    Опубликовано Обновлено
  19. CVE-2023-53309

    Средний · CVSS 5.5EPSS 0,16%Нет опубликованного исправления

    drm/radeon: Fix integer overflow in radeon_cs_parser_init

    In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Fix integer overflow in radeon_cs_parser_init The type of size is unsigned, if size is 0x40000000, there will be an integer overflow, size will be zero after size *= sizeof(uint32_t), will cause uninitialized memory to be referenced later

    Опубликовано Обновлено
  20. CVE-2023-53305

    Высокий · CVSS 8.8EPSS 0,23%Нет опубликованного исправления

    Bluetooth: L2CAP: Fix use-after-free

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free Fix potential use-after-free in l2cap_le_command_rej.

    Опубликовано Обновлено

Проверьте свой сервер

Сопоставьте установленный стек и версии со свежими базами уязвимостей.

Проверьте свой сервер →