p PatchFirst

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

Уязвимости linux-azure-4.15 · Страница 25

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

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

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

  1. CVE-2026-97531

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

    scsi: qla2xxx: Skip vport under deletion in report ID acquisition

    In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Skip vport under deletion in report ID acquisition qla24xx_report_id_acquisition() format-1 handling walks ha->vp_list under vport_slock, takes a vref_count on the matching vport and calls qla_update_host_map() to register its port id. A vport teardown via qla24xx_vport_delete() sets VPORT_DELETE, then qla24xx_disable_vp() removes the vport from the host_map btree and zeroes vha->d_id (RESET_AL_PA). The vport is only unlinked from vp_list later, in qla24xx_deallocate_vp_id(), which clears vp_map[idx] (RESET_VP_IDX) but does not touch host_map. In the window

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

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

    scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[]

    In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[] The FC BSG transport allocates job->request via memdup_user() using the exact user-supplied request_len. For FC_BSG_HST_VENDOR, fc_bsg_host_dispatch() only guarantees request_len covers msgcode and vendor_id; it does not account for the vendor_cmd[] flexible array. qla2xxx then reads the command selector vendor_cmd[0] and, in several sub-handlers, vendor_cmd[1]/[2] or structures overlaid on the vendor command area without verifying request_len. A caller holding CAP_SYS_RAWIO can submit a short request whos

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

    Без оценкиEPSS 0,15%Нет опубликованного исправления

    gfs2: fix quota init duplicate scan

    In the Linux kernel, the following vulnerability has been resolved: gfs2: fix quota init duplicate scan gfs2_quota_init() checks for duplicate quota_change IDs while holding qd_lock and the quota hash bucket bitlock. That path used gfs2_qd_search_bucket(), which takes a lockref reference via lockref_get_not_dead(). On PREEMPT_RT this may sleep, which is not allowed under the bucket bitlock, triggering "sleeping function called from invalid context". Use a no-ref bucket lookup in this path, then continue duplicate handling without taking a lockref there. Refactor gfs2_qd_search_bucket() to build on top of the no-ref helper so lookup trave

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

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

    gfs2: move quota_init qc iterator increment

    In the Linux kernel, the following vulnerability has been resolved: gfs2: move quota_init qc iterator increment Move qc++ from the loop body into the for-loop increment expression in gfs2_quota_init(). This keeps iterator progression explicit and avoids mixing pointer advance with duplicate-slot handling in the loop body.

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

    Без оценкиEPSS 0,14%Нет опубликованного исправления

    drm/xe: Fix null pointer dereference in devcoredump cleanup

    In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix null pointer dereference in devcoredump cleanup In xe_devcoredump_snapshot_free(), ss->gt may be NULL when the snapshot was never fully populated (e.g., when cleanup is triggered without a prior capture). Guard the xe_guc_capture_put_matched_nodes() call with IS_ERR_OR_NULL() to prevent a null dereference. In xe_devcoredump_free(), the deferred work is only queued when a coredump is captured, so guard cancel_work_sync() with a check on coredump->captured.

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

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

    wifi: cfg80211: reject duplicate wiphy cipher suite entries

    In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: reject duplicate wiphy cipher suite entries Duplicate entries in wiphy->cipher_suites do not describe any additional capability, but cfg80211 currently accepts them and leaves individual consumers to deal with them. One such consumer is the WEXT compatibility code, which appends a WEP key length for each WEP cipher entry it sees. Repeated WEP entries can therefore overflow the fixed iw_range::encoding_size array returned by SIOCGIWRANGE. Reject duplicate cipher suite entries in wiphy_register() instead. This keeps the cipher suite invariant in one place an

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

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

    wifi: nl80211: reject beacons with bad HE operation

    In the Linux kernel, the following vulnerability has been resolved: wifi: nl80211: reject beacons with bad HE operation The HE operation element not only needs to be longer than the fixed part, but also have an appropriate size for the variable part inside of it. Check this.

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

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

    wifi: rtw88: Add NULL check for chip->edcca_th in rtw_fw_adaptivity_result()

    In the Linux kernel, the following vulnerability has been resolved: wifi: rtw88: Add NULL check for chip->edcca_th in rtw_fw_adaptivity_result() It was recently reported that rtw_fw_adaptivity_result() in fw.c dereferences rtwdev->chip->edcca_th without a NULL check. The issue is that devices with the 8821CE chip don't define edcca_th in their chip info. As a result, when rtw_fw_adaptivity_result() tries to dereference it, the kernel triggers an oops. Add a NULL check for edcca_th before dereferencing it in rtw_fw_adaptivity_result() in fw.c. Placing the check at the function entry avoids logging any garbage values. This change does not a

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

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

    i3c: master: svc: Prevent IRQ storm from false SLVSTART on NPCM845

    In the Linux kernel, the following vulnerability has been resolved: i3c: master: svc: Prevent IRQ storm from false SLVSTART on NPCM845 On NPCM845, when a target on the I3C bus gets stuck holding SDA low, the controller reports a false Master Request (MR) in-band interrupt event. The driver handles this by emitting a STOP condition to restore the bus. However, the hardware quirk SVC_I3C_QUIRK_FALSE_SLVSTART indicates that emitting a STOP condition may spuriously set the SLVSTART interrupt status bit. In the Master Request case, this creates a feedback loop: the STOP triggers a new SLVSTART event, the IRQ handler fires again, the controller

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

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

    media: chips-media: wave5: Fix Reports from Kernel Lock Validator

    In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Fix Reports from Kernel Lock Validator handle_dynamic_resolution change requires that the state_lock be acquired based on the lockdep_assert_held. However, the handle_dynamic_resolution_change call in initialize_sequence does not properly obtain the lock before calling. Since the v4l2_ctrl_find and s_ctrl can sleep, they should not be called while a lock is already held. Store off the fbc_buf_count then properly update control once lock has been freed.

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

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

    media: chips-media: wave5: Release m2m_ctx after Instance Removed from List

    In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Release m2m_ctx after Instance Removed from List Possible use after free if IRQ thread manages to obtain spinlock between m2m_ctx release and wave5_release function removing stream instance from list of active instances. The IRQ thread looks for the m2m_ctx which is freed so null pointer dereference occurs.

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

    Без оценкиEPSS 0,16%Нет опубликованного исправления

    spi: spi-qcom-qspi: Fix incomplete error handling in runtime PM

    In the Linux kernel, the following vulnerability has been resolved: spi: spi-qcom-qspi: Fix incomplete error handling in runtime PM The runtime PM functions had incomplete error handling that could leave the system in an inconsistent state. If any operation failed midway through suspend or resume, some resources would be left in the wrong state while others were already changed, leading to potential clock/power imbalances. Reorder the suspend/resume sequences to avoid brownout risk by ensuring the performance state is set appropriately before clocks are enabled and clocks are disabled before dropping the performance state. Fix by adding p

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

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

    wifi: mac80211: avoid out-of-bounds access in monitor

    In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: avoid out-of-bounds access in monitor In NAN, we don't know on what band the frame will be sent. Therefore we set info->band to NUM_NL80211_BANDS. However, this leads to out-of-bound access in ieee80211_add_tx_radiotap_header when we try to access the sbands array. Fix it by not accessing the array if the band is NUM_NL80211_BANDS. This means that we will not report rate info for legacy rate in NAN. But nobody really cares about it.

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

    Без оценкиEPSS 0,16%Нет опубликованного исправления

    thunderbolt: Release request if tb_cfg_request() fails in __tb_xdomain_response()

    In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Release request if tb_cfg_request() fails in __tb_xdomain_response() If tb_cfg_request() fails setting up the request (for example the control channel is shut down already) it returns an error without calling the callback. To avoid leaking that memory, call tb_cfg_request_put() if tb_cfg_request() fails.

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

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

    thunderbolt: Keep XDomain reference during the lifetime of a service

    In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Keep XDomain reference during the lifetime of a service This is needed because we release the service ID in tb_service_release() and the ID array is owned by the parent XDomain.

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

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

    thunderbolt: Set tb->root_switch to NULL when domain is stopped

    In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Set tb->root_switch to NULL when domain is stopped Similarly what we do with the firmware connection manager. This makes tb_xdp_handle_request() return error to the remote host. However, we need to make sure we keep the uuid alive so that we can reply until the whole domain is released.

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

    Без оценкиEPSS 0,16%Нет опубликованного исправления

    media: dm1105: fix missing error check for dma_alloc_coherent

    In the Linux kernel, the following vulnerability has been resolved: media: dm1105: fix missing error check for dma_alloc_coherent The return value of dm1105_dma_map(), which handles DMA memory allocation, is ignored in dm1105_hw_init(). If dma_alloc_coherent() fails, the driver will proceed using a NULL pointer for DMA transfers, leading to a kernel oops or invalid hardware access. Fix this by checking the return value and propagating -ENOMEM on failure.

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

    Без оценкиEPSS 0,16%Нет опубликованного исправления

    crypto: ixp4xx - fix buffer chain unwind on allocation failure

    In the Linux kernel, the following vulnerability has been resolved: crypto: ixp4xx - fix buffer chain unwind on allocation failure chainup_buffers() builds a linked list of buffer descriptors for a scatterlist. If dma_pool_alloc() fails while constructing the list, the current code sets buf to NULL and later dereferences it unconditionally at the end of the function: buf->next = NULL; buf->phys_next = 0; This can lead to a null-pointer dereference on allocation failure. If the failure happens after part of the descriptor chain has already been allocated and DMA-mapped, the partially constructed chain also needs to be released. Fix t

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

    Без оценкиEPSS 0,16%Нет опубликованного исправления

    PCI/sysfs: Add CAP_SYS_ADMIN check to __resource_resize_store()

    In the Linux kernel, the following vulnerability has been resolved: PCI/sysfs: Add CAP_SYS_ADMIN check to __resource_resize_store() Currently, the __resource_resize_store() allows writing to the resourceN_resize sysfs attribute to change a BAR's size without checking for capabilities, currently relying only on the file access check. Resizing a BAR modifies PCI device configuration and can disrupt active drivers. After the upcoming conversion to static attributes, it will also trigger resource file updates via sysfs_update_groups(). Add a CAP_SYS_ADMIN check to prevent unprivileged users from performing BAR resize operations.

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

    Без оценкиEPSS 0,15%Нет опубликованного исправления

    watchdog: lenovo_se10_wdt: Fix use-after-free and resource leak risk

    In the Linux kernel, the following vulnerability has been resolved: watchdog: lenovo_se10_wdt: Fix use-after-free and resource leak risk Review by sashiko.dev highlighted potential use after free and resource leak instances. Set se10_pdev to null to prevent use after free Remove DMI call back and instead directly call se10_create_platform_device. Handle error cases appropriately

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

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

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

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