p PatchFirst

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

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

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

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

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

  1. CVE-2026-74318

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

    btrfs: fix deadlock cloning inline extent when using flushoncommit

    In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock cloning inline extent when using flushoncommit In commit b48c980b6a7e ("btrfs: fix deadlock between reflink and transaction commit when using flushoncommit") a deadlock was fixed between reflinks and transaction commits when the fs is mounted with the flushoncommit option. This happened when we had to copy an inline extent's data to the destination file. However the issue was fixed only for the case where the destination offset is 0, it missed the case when the offset is greater than zero. Fix this by ensuring we get i_size update whenever we copied an

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

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

    ixgbe: do not configure xps for XDP queues

    In the Linux kernel, the following vulnerability has been resolved: ixgbe: do not configure xps for XDP queues netif_set_xps_queue() should not be called for an XDP Tx queue, since such queues are not netdev-exposed. On systems with number of CPUs >=64, on E610 adapter, netdev is configured with maximum number queue pairs being 63 (due to MSI-X assignment), but configuring XDP results in 64 XDP queues. So, during XDP program load, when netif_set_xps_queue() is called for the last XDP queue, we get a WARNING with a call trace and KASAN report afterwards (if enabled). [ 2012.699800] WARNING: net/core/dev.c:2854 at __netif_set_xps_queue+0x11

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

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

    vduse: hold vduse_lock across IDR lookup in open path

    In the Linux kernel, the following vulnerability has been resolved: vduse: hold vduse_lock across IDR lookup in open path vduse_dev_open() looks up struct vduse_dev through the IDR and then acquires dev->lock only after vduse_lock has been dropped. This leaves a window where a concurrent VDUSE_DESTROY_DEV can remove the same object from the IDR and free it before the open path locks the device, leading to a use-after-free. Close this race by keeping vduse_lock held until dev->lock has been acquired in the open path, matching the lock ordering already used by the destroy path.

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

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

    vhost/vdpa: validate virtqueue index in mmap and fault paths

    In the Linux kernel, the following vulnerability has been resolved: vhost/vdpa: validate virtqueue index in mmap and fault paths vhost_vdpa_mmap() and vhost_vdpa_fault() use vma->vm_pgoff as a virtqueue index for get_vq_notification(), but they do not validate that the index is smaller than v->nvqs. The ioctl path already performs both a bounds check and array_index_nospec(), but the mmap/fault path only checks that the index fits in u16. This allows an out-of-range queue index to reach driver-specific get_vq_notification() callbacks. Fix this by extracting a unified vhost_vdpa_get_vq_notification() helper that validates the queue index a

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

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

    vhost/net: complete zerocopy ubufs only once

    In the Linux kernel, the following vulnerability has been resolved: vhost/net: complete zerocopy ubufs only once vhost-net initializes one ubuf_info per outstanding zerocopy TX descriptor and hands it to the backend socket. The networking stack may then clone a zerocopy skb before all skb references are released. For example, batman-adv fragmentation reaches skb_split(), which calls skb_zerocopy_clone() and increments the same ubuf_info refcount. vhost_zerocopy_complete() currently treats every ubuf callback as a completed vhost descriptor. It dereferences ubuf->ctx, writes the descriptor completion state, and drops the vhost_net_ubuf_r

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

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

    ext4: fix kernel BUG in ext4_write_inline_data_end

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix kernel BUG in ext4_write_inline_data_end When the data=journal mount option is used, the ext4_journalled_write_end() function incorrectly calls ext4_write_inline_data_end() without checking if the EXT4_STATE_MAY_INLINE_DATA flag is still set on the inode. If a previous attempt to convert the inline data to an extent failed (e.g. due to ENOSPC), the EXT4_STATE_MAY_INLINE_DATA flag is cleared, but the EXT4_INODE_INLINE_DATA flag remains set. In this scenario, the next call to ext4_write_begin() will not prepare the inline data xattr for writing, but ext4_journalled

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

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

    ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT

    In the Linux kernel, the following vulnerability has been resolved: ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT Reject the EXT4_IOC_MOVE_EXT ioctl early if the donor file does not belong to the same superblock as the original file. Currently, this validation is performed inside ext4_move_extents() by mext_check_validity(), but only after lock_two_nondirectories() has already acquired the inode locks. When the donor fd refers to a file on a different filesystem (e.g., overlayfs), this late validation creates a circular lock dependency: CPU0 (overlayfs write) CPU1 (ext4 ioctl) ----

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

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

    RDMA/mlx5: Fix undefined shift of user RQ WQE size

    In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix undefined shift of user RQ WQE size set_rq_size() computes the RQ WQE size as "1 << rq_wqe_shift" based on the user-provided rq_wqe_shift, which is only checked to be greater than 32, so shifts of 32 are still accepted. A shift of 31 also overflows a signed integer, leading to undefined behavior. Use check_shl_overflow() to compute the RQ WQE size and reject any invalid values.

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

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

    RDMA/mlx5: Release the HW‑provided UAR index rather than the SW one

    In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Release the HW‑provided UAR index rather than the SW one Free the UAR index returned by the hardware.

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

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

    ASoC: codecs: hdac_hdmi: Validate written enum value

    In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: hdac_hdmi: Validate written enum value hdac_hdmi_set_pin_port_mux() uses the written enum value to index the texts array before calling snd_soc_dapm_put_enum_double(), which validates that the value is within the enum item range. An out-of-range value can therefore make the driver read past the texts array before the helper rejects the write. Move the lookup after the helper has accepted the value.

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

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

    ASoC: meson: aiu: Validate written enum values

    In the Linux kernel, the following vulnerability has been resolved: ASoC: meson: aiu: Validate written enum values The AIU HDMI and internal codec mux put callbacks use the written enum value with snd_soc_enum_item_to_val() before checking whether the value is valid for the enumeration. Reject out-of-range values before converting the enum item, matching the validation already done by the G12A HDMI and internal codec mux controls.

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

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

    ASoC: fsl: fsl_audmix: Validate written enum values

    In the Linux kernel, the following vulnerability has been resolved: ASoC: fsl: fsl_audmix: Validate written enum values fsl_audmix_put_mix_clk_src() and fsl_audmix_put_out_src() convert the user-provided enum item with snd_soc_enum_item_to_val() before checking whether the item is within the enum's item count. The generic snd_soc_put_enum_double() helper performs that validation, but these callbacks use the converted value first: the clock-source path tests it with BIT(), and the output-source path indexes the prms transition table with it. Reject out-of-range enum items before converting them.

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

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

    ASoC: tegra: tegra210_ahub: Validate written enum value

    In the Linux kernel, the following vulnerability has been resolved: ASoC: tegra: tegra210_ahub: Validate written enum value tegra_ahub_put_value_enum() reads e->values[item[0]] before checking whether item[0] is within the enum item range. The existing check therefore happens too late to prevent an out-of-range read of the values array. Move the check before the array access.

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

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

    ASoC: topology: Check PCM and DAI name strings before use

    In the Linux kernel, the following vulnerability has been resolved: ASoC: topology: Check PCM and DAI name strings before use Topology objects store several PCM and DAI names in fixed-size UAPI arrays. Other topology parser paths validate these fields with bounded strnlen() checks before using them as C strings, but the PCM and DAI paths still pass some fixed-size arrays directly to strlen(), devm_kstrdup(), DAI lookup, and diagnostic prints. A malformed topology blob with a non-NUL-terminated PCM, DAI, or stream capability name can therefore make the parser read past the end of the fixed-size field. Reject unterminated PCM and DAI name f

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

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

    net/sched: cls_flow: Dont expose folded kernel pointers

    In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_flow: Dont expose folded kernel pointers The flow classifier falls back to addr_fold() for fields that are missing from packet headers. In map mode, userspace controls mask, xor, rshift, addend and divisor, and can observe the resulting classid through class statistics. This allows a tc classifier in a user/network namespace to recover the 32-bit folded value of skb->sk, skb_dst() or skb_nfct(). Align with standard kernel practices for pointer hashing and replace the XOR folding with a keyed siphash (which is cryptographically secure)

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

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

    ipv4: fib: Don't dump dying fib_info in fib_leaf_notify().

    In the Linux kernel, the following vulnerability has been resolved: ipv4: fib: Don't dump dying fib_info in fib_leaf_notify(). syzbot reported use-after-free in nsim_fib4_prepare_event(). [0] The problem is that the following functions call fib_info_hold() / refcount_inc() while dumping fib_info under RCU, which is unsafe. * mlxsw_sp_router_fib4_event() * rocker_router_fib_event() * nsim_fib4_prepare_event() refcount_inc_not_zero() must be used, but it would be too late there. Let's guarantee the lifetime of fib_info in fib_leaf_notify(). Note that IPv6 does not need the corresponding change since fib6_table_dump() holds fib6_tab

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

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

    net: fib_rules: Don't dump dying fib_rule in fib_rules_dump().

    In the Linux kernel, the following vulnerability has been resolved: net: fib_rules: Don't dump dying fib_rule in fib_rules_dump(). rocker_router_fib_event() calls fib_rule_get() during RCU dump. If the fib_rule is dying, refcount_inc() will complain about it. Let's call refcount_inc_not_zero() in fib_rules_dump().

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

    Критический · CVSS 9.1EPSS 0,73%Нет опубликованного исправления

    sctp: validate embedded address parameter length

    In the Linux kernel, the following vulnerability has been resolved: sctp: validate embedded address parameter length sctp_verify_asconf() and sctp_verify_param() only validate ADD_IP, DEL_IP, and SET_PRIMARY parameters against a fixed minimum size of sizeof(struct sctp_addip_param) + sizeof(struct sctp_paramhdr). This ensures the outer parameter is large enough to contain an embedded address parameter header, but does not verify that the embedded address parameter's declared length fits within the bounds of the outer parameter. Later, sctp_process_param() and sctp_process_asconf_param() extract the embedded address parameter and pass it to

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

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

    tipc: require net admin for TIPCv2 netlink mutators

    In the Linux kernel, the following vulnerability has been resolved: tipc: require net admin for TIPCv2 netlink mutators TIPCv2 registers mutating generic-netlink operations without admin permission flags. Generic netlink only checks CAP_NET_ADMIN when an operation sets GENL_ADMIN_PERM or GENL_UNS_ADMIN_PERM, so a local unprivileged process can currently change TIPC state through commands such as TIPC_NL_NET_SET, TIPC_NL_KEY_SET, TIPC_NL_KEY_FLUSH, and bearer enable/disable. The legacy TIPC netlink API already checks netlink_net_capable(..., CAP_NET_ADMIN) for administrative commands. Give the TIPCv2 mutators the equivalent generic-netlink

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

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

    tipc: prevent snt_unacked underflow on CONN_ACK

    In the Linux kernel, the following vulnerability has been resolved: tipc: prevent snt_unacked underflow on CONN_ACK tipc_sk_conn_proto_rcv() subtracts the peer-supplied connection ack count from the unsigned 16-bit send counter snt_unacked without checking that it does not exceed the number of messages actually outstanding: tsk->snt_unacked -= msg_conn_ack(hdr); msg_conn_ack() is read straight from a received CONN_MANAGER/CONN_ACK message. If the ack count is larger than snt_unacked, the subtraction wraps to a near-maximum value, leaving tsk_conn_cong() permanently true and starving the connection of further transmits. Validate the ACK

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

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

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

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