p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-lts-xenial · Seite 27

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 5695

  1. CVE-2026-93798

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

    btrfs: fix reloc root cleanup in merge_reloc_roots()

    In the Linux kernel, the following vulnerability has been resolved: btrfs: fix reloc root cleanup in merge_reloc_roots() If the root we got has zero root refs in its root item, we are resetting the root's ->reloc_root without using barriers like we do everywhere else. Sashiko complained about this while reviewing another patch, and it's correct (see the Link tag below). Also, we should not clear BTRFS_ROOT_DEAD_RELOC_TREE from the root unless the root points to the reloc root we have. Fix this by using clear_reloc_root(), which issues the memory barrier after setting the root's ->reloc_root to NULL and before clearing the bit BTRFS_ROOT_D

    Veröffentlicht Aktualisiert
  2. CVE-2026-93796

    Hoch · CVSS 7EPSS 0,12%Keine Korrektur veröffentlicht

    wifi: iwlwifi: pcie: null RX pointers after free

    In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: pcie: null RX pointers after free When iwl_pcie_tx_init() fails after RX init, nic init unwinds via iwl_pcie_rx_free(). The freed RX members stayed non-NULL on the live transport object, so later teardown or retry could touch stale RX state. Set rx_pool, global_table, rxq, and alloc_page to NULL after free to make repeated cleanup and retry paths safe.

    Veröffentlicht Aktualisiert
  3. CVE-2026-93795

    Nicht bewertetEPSS 0,17%Keine Korrektur veröffentlicht

    blk-cgroup: fix leaks and online flag on radix_tree_insert failure

    In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix leaks and online flag on radix_tree_insert failure When radix_tree_insert() fails in blkg_create(), the error path has two issues: 1. blkg->online is set to true unconditionally, even when the blkg was never fully inserted. Move the assignment inside the success block. 2. The error path calls blkg_put() without first calling percpu_ref_kill(). Because the refcount is still in percpu mode, percpu_ref_put() only does this_cpu_sub() without checking for zero, so blkg_release() is never triggered. This permanently leaks the blkg memory, its p

    Veröffentlicht Aktualisiert
  4. CVE-2026-93794

    Mittel · CVSS 4.8EPSS 0,17%Keine Korrektur veröffentlicht

    smb/client: flush dirty data before punching a hole

    In the Linux kernel, the following vulnerability has been resolved: smb/client: flush dirty data before punching a hole Punching a hole after a large buffered write may leave the range reported as data. Reproduce it with: xfs_io -f \ -c "pwrite -b 3m -S 0x61 0 3m" \ -c "fpunch 1m 1m" \ -c "seek -h 0" \ -c "seek -d 1m" \ /mnt/test/repro Punching 1 MiB at offset 1 MiB should produce: 0 1 MiB 2 MiB 3 MiB | DATA | HOLE | DATA | EOF Instead, the entire file is reported as data. SEEK_HOLE(0) returns EOF, and SEEK_DATA(1M) returns 1M. This happens because a dirty folio spanning the

    Veröffentlicht Aktualisiert
  5. CVE-2026-93793

    Hoch · CVSS 8.8EPSS 0,24%Keine Korrektur veröffentlicht

    wifi: iwlwifi: mvm: validate TX_CMD response layout

    In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: validate TX_CMD response layout TX_CMD parsing uses frame_count to walk status entries and then read the trailing SCD SSN. Make the minimum-length check follow that exact runtime layout calculation before parsing the payload. For new TX API, reject TX_CMD responses with frame_count != 1 and warn/return in the aggregation handler to document that aggregated accounting is expected via BA notifications.

    Veröffentlicht Aktualisiert
  6. CVE-2026-93791

    Mittel · CVSS 6EPSS 0,17%Keine Korrektur veröffentlicht

    wifi: iwlwifi: mvm: add a check on the tid coming from the firmware

    In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: add a check on the tid coming from the firmware ba_notif->tid is a firmware-controlled u8 that is used directly as an array index into tid_data[] without any validation. Add a bounds check against IWL_MAX_TID_COUNT before dereferencing the array.

    Veröffentlicht Aktualisiert
  7. CVE-2026-93790

    Hoch · CVSS 8.8EPSS 0,24%Keine Korrektur veröffentlicht

    wifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif

    In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif mvmsta->tid_data was indexed by the TFD loop counter 'i' instead of the actual TID value 'tid'. This writes lq_color into a random tid_data slot unrelated to the BA entry. Since multi-TID blockack is not really in use, 'i' was always 0 and no harm was done. Add a out-of-bound check before accessing the array.

    Veröffentlicht Aktualisiert
  8. CVE-2026-93789

    Nicht bewertetEPSS 0,17%Keine Korrektur veröffentlicht

    wifi: iwlwifi: bound aligned TLV advance in FW parser

    In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: bound aligned TLV advance in FW parser Validate ALIGN(tlv_len, 4) against remaining parser length before consuming bytes from the firmware image. This avoids length underflow on malformed TLVs.

    Veröffentlicht Aktualisiert
  9. CVE-2026-93788

    Nicht bewertetEPSS 0,17%Keine Korrektur veröffentlicht

    wifi: iwlwifi: acpi: validate WGDS table revision index

    In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: acpi: validate WGDS table revision index Check tbl_rev bounds before BIT(tbl_rev) to avoid undefined shifts when firmware reports an invalid revision value.

    Veröffentlicht Aktualisiert
  10. CVE-2026-93787

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

    smb: client: bound dirent name against end of SMB response in cifs_filldir

    In the Linux kernel, the following vulnerability has been resolved: smb: client: bound dirent name against end of SMB response in cifs_filldir cifs_filldir() copies the entry name out of an SMB1 TRANS2_FIND_FIRST / FIND_NEXT response using a length (de.namelen) supplied by the server. The kmalloc'd SMB response buffer is bounded, but nothing checks that de.name + de.namelen still lies inside that buffer before the eventual filldir64() -> verify_dirent_name() -> memchr() reads namelen bytes. A hostile SMB1 server that returns an oversized FileNameLength in a directory entry therefore causes memchr() to read past the end of the response slab

    Veröffentlicht Aktualisiert
  11. CVE-2026-93786

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

    ksmbd: preserve VFS inherited POSIX ACL mask

    In the Linux kernel, the following vulnerability has been resolved: ksmbd: preserve VFS inherited POSIX ACL mask The VFS initializes a child's POSIX ACL from the parent's default ACL and the requested creation mode. Do not mutate the parent ACL or overwrite the child's VFS-computed access and default ACLs afterwards. This preserves restrictive ACL_MASK entries and prevents SMB object creation from widening effective permissions.

    Veröffentlicht Aktualisiert
  12. CVE-2026-93785

    Nicht bewertetEPSS 0,17%Keine Korrektur veröffentlicht

    cifs: validate idmap key payload length

    In the Linux kernel, the following vulnerability has been resolved: cifs: validate idmap key payload length The cifs.idmap key type stores its payload length in key->datalen, which is limited to U16_MAX. Accepting a larger key payload truncates the recorded length and can make later users interpret the payload using inconsistent bounds. Reject oversized preparsed payloads before allocating or copying them. This keeps key->datalen consistent with the stored data for both inline and separately allocated idmap payloads.

    Veröffentlicht Aktualisiert
  13. CVE-2026-93784

    Nicht bewertetEPSS 0,17%Keine Korrektur veröffentlicht

    wifi: cfg80211: validate IEs in cfg80211_wext_siwgenie()

    In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: validate IEs in cfg80211_wext_siwgenie() The KASAN allocation trace shows that a malformed IE buffer is stored via SIOCSIWGENIE (cfg80211_wext_siwgenie()) without any validation. The crash trace shows that a subsequent SIOCSIWESSID triggers a connection attempt which calls cfg80211_sme_get_conn_ies() to process the stored IE buffer, causing: - An out-of-bounds read in skip_ie() which reads ies[pos+1] (the length byte) past the end of the 1-byte buffer. - An integer underflow in the memcpy size argument when offs returned by ieee80211_ie_split() exc

    Veröffentlicht Aktualisiert
  14. CVE-2026-93783

    Nicht bewertetEPSS 0,17%Keine Korrektur veröffentlicht

    Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame rfcomm_recv_frame() casts skb->data to struct rfcomm_hdr and dereferences hdr->addr and hdr->ctrl without validating skb->len first. A truncated frame with skb->len less than the minimum header size causes an out-of-bounds read of uninitialized memory. Additionally, a zero-length frame causes skb->len-- to underflow to UINT_MAX, making skb_tail_pointer() read far past the buffer. Commit 23882b828c3c ("Bluetooth: RFCOMM: validate skb length in MCC handlers") fixed the same class of missing-length-check bugs in the

    Veröffentlicht Aktualisiert
  15. CVE-2026-93782

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

    vhost-scsi: flush backend after device ioctls

    In the Linux kernel, the following vulnerability has been resolved: vhost-scsi: flush backend after device ioctls vhost-scsi translates guest response descriptors into userspace iovecs when commands are submitted. Target-core completes those commands asynchronously, so VHOST_SET_MEM_TABLE can replace the memory table while an in-flight command still retains response iovecs translated through the old table. If the old mapping is reused after VHOST_SET_MEM_TABLE returns, command completion can write the response to an unrelated userspace object. Flush the vhost-scsi backend after vhost_dev_ioctl() handles a device ioctl. This waits for in

    Veröffentlicht Aktualisiert
  16. CVE-2026-93781

    Mittel · CVSS 5.7EPSS 0,17%Keine Korrektur veröffentlicht

    scsi: core: Do not block on tag allocation in scsi_eh_lock_door()

    In the Linux kernel, the following vulnerability has been resolved: scsi: core: Do not block on tag allocation in scsi_eh_lock_door() scsi_eh_lock_door() is called from scsi_restart_operations() while the host is still in the SHOST_RECOVERY state, i.e. before the host is switched back to SHOST_RUNNING and scsi_run_host_queues() restarts the queues. It allocates a request via scsi_alloc_request() with no flags, so blk_mq_get_tag() may block waiting for a free sched tag when all tags are already in use. Those tags can be held by commands that were just requeued by scsi_eh_flush_done_q() during error handling. Such commands cannot be dispatch

    Veröffentlicht Aktualisiert
  17. CVE-2026-93288

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

    netfilter: nfnetlink_log: wait for rcu grace period before freeing pernet state

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nfnetlink_log: wait for rcu grace period before freeing pernet state sashiko reports: "nfnl_log_net_exit() calls nf_log_unset(), which clears the logger pointer without an RCU grace period. Immediately after, ops_free_list() frees the per-net state while concurrent packets might still be executing nf_log_packet() under rcu_read_lock()." Clear the pointer via .pre_exit to make sure rcu readers have completed before pernet storage is free'd. The change in nf_log_syslog.c is only done for consistency: it doesn't use pernet data.

    Veröffentlicht Aktualisiert
  18. CVE-2026-93287

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

    i2c: smbus: reject oversized block transfers in the common path

    In the Linux kernel, the following vulnerability has been resolved: i2c: smbus: reject oversized block transfers in the common path The SMBus block transfer length data->block[0] is validated in i2c_smbus_xfer_emulated() but that check runs too late for tracepoints and is skipped entirely when the adapter provides a native smbus_xfer implementation. This allows user-controlled oversized block lengths to reach tracepoint memcpy calls and driver callbacks unchecked. Add an early validation in __i2c_smbus_xfer() that rejects block transfers whose caller-supplied length is zero or exceeds I2C_SMBUS_BLOCK_MAX before any tracepoint fires or driv

    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 →