p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-azure-fips · Seite 182

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 7653

  1. CVE-2026-64425

    Mittel · CVSS 5.5EPSS 0,13%Korrektur verfügbar

    io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item

    In the Linux kernel, the following vulnerability has been resolved: io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item commit 10dc95939817 ("io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop") fixed the obvious case where io_worker_handle_work() took one exit-bit snapshot before draining pending work, but the fix stops one level too early. io_worker_handle_work() now re-checks IO_WQ_BIT_EXIT in its outer work run loop, yet it still snapshots that bit once before processing a whole dependent linked-work chain. If io_wq_exit_start() sets IO_WQ_BIT_EXIT after the first linked item has started, the remaining linked items

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-64424

    Hoch · CVSS 7.8EPSS 0,12%Korrektur verfügbar

    netpoll: fix a use-after-free on shutdown path

    In the Linux kernel, the following vulnerability has been resolved: netpoll: fix a use-after-free on shutdown path There is a use-after-free error on netpoll, which is clearly detected by KASAN. BUG: KASAN: slab-use-after-free in _raw_spin_lock_irqsave+0x3b/0x80 Read of size 1 at addr ... by task kworker/9:1 Workqueue: events queue_process Call Trace: skb_dequeue+0x1e/0xb0 queue_process+0x2c/0x600 process_scheduled_works+0x4b6/0x850 worker_thread+0x414/0x5a0 Allocated by task 242: __netpoll_setup+0x201/0x4a0 netpoll_setup+0x249/0x550 enabled_store+0x32f/0x380

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2026-64423

    Hoch · CVSS 7.8EPSS 0,13%Korrektur verfügbar

    ipv4: igmp: remove multicast group from hash table on device destruction

    In the Linux kernel, the following vulnerability has been resolved: ipv4: igmp: remove multicast group from hash table on device destruction When a device is destroyed under RTNL, ip_mc_destroy_dev() iterates through the multicast list and calls ip_ma_put() on each membership, scheduling them for RCU reclamation. However, they are not unlinked from the device's multicast hash table (mc_hash). Since the device remains published in dev->ip_ptr until after ip_mc_destroy_dev() completes, concurrent RCU readers traversing mc_hash can still locate and access the multicast group after its refcount is decremented. If the RCU callback runs and free

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2026-64422

    Hoch · CVSS 7.1EPSS 0,14%Korrektur verfügbar

    net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes

    In the Linux kernel, the following vulnerability has been resolved: net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes Reject invalid `net.ipv4.tcp_reordering` values before they reach TCP socket state. The sysctl is stored as an `int` but copied into the `u32` `tp->reordering` field for new sockets, so negative writes wrap to large values. With `tcp_mtu_probing=2`, the wrapped value can overflow the `tcp_mtu_probe()` size calculation and drive the MTU probing path into an out-of-bounds read. Route `tcp_reordering` writes through `proc_dointvec_minmax()` and require it to be at least 1. Also require `tcp_max_reordering` to b

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2026-64421

    Hoch · CVSS 7.8EPSS 0,12%Korrektur verfügbar

    media: nxp: imx8-isi: Fix use-after-free on remove

    In the Linux kernel, the following vulnerability has been resolved: media: nxp: imx8-isi: Fix use-after-free on remove KASAN reports a slab-use-after-free in __media_entity_remove_link() during rmmod of imx8_isi: BUG: KASAN: slab-use-after-free in __media_entity_remove_link+0x608/0x650 Read of size 2 at addr ffff0000d47cb02a by task rmmod/724 Call trace: __media_entity_remove_link+0x608/0x650 __media_entity_remove_links+0x78/0x144 __media_device_unregister_entity+0x150/0x280 media_device_unregister_entity+0x48/0x68 v4l2_device_unregister_subdev+0x158/0x300 v4l2_async_unbind_subdev_one+0x22c/0x358 v4l2_async_nf_u

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2026-64420

    Hoch · CVSS 7EPSS 0,12%Korrektur verfügbar

    mfd: cros_ec: Delay dev_set_drvdata() until probe success

    In the Linux kernel, the following vulnerability has been resolved: mfd: cros_ec: Delay dev_set_drvdata() until probe success If ec_device_probe() fails, cros_ec_class_release releases memory for the cros_ec_dev structure. However, because the drvdata was already set, sub-drivers like cros_ec_typec can still retrieve the stale pointer via the platform device. This leads to a use-after-free when cros_ec_typec attempts to access &typec->ec->ec->dev on a device that has already been released. Move dev_set_drvdata() to ensure that the pointer is only made available once all initialization steps have succeeded. sysfs: cannot create duplicate f

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2026-64419

    Mittel · CVSS 5.5EPSS 0,12%Korrektur verfügbar

    mm/shrinker: do not hold RCU lock in shrinker_debugfs_count_show()

    In the Linux kernel, the following vulnerability has been resolved: mm/shrinker: do not hold RCU lock in shrinker_debugfs_count_show() Reading the debugfs "count" file of a memcg-aware shrinker can sleep inside an RCU read-side critical section: BUG: sleeping function called from invalid context at kernel/cgroup/rstat.c:421 RCU nest depth: 1, expected: 0 css_rstat_flush mem_cgroup_flush_stats zswap_shrinker_count shrinker_debugfs_count_show shrinker_debugfs_count_show() invokes the ->count_objects() callback under rcu_read_lock(). The zswap callback flushes memcg stats via css_rstat_flush(), which may sleep, so it must no

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2026-64418

    Hoch · CVSS 7.8EPSS 0,1%Korrektur verfügbar

    mm: shrinker: fix shrinker_info teardown race with expansion

    In the Linux kernel, the following vulnerability has been resolved: mm: shrinker: fix shrinker_info teardown race with expansion expand_shrinker_info() iterates all visible memcgs under shrinker_mutex, including memcgs that have not finished ->css_online() yet. Once pn->shrinker_info has been published, teardown must stay serialized with expand_shrinker_info() until that memcg is either fully online or no longer visible to iteration. Today alloc_shrinker_info() breaks that rule by dropping shrinker_mutex before freeing a partially initialized shrinker_info array, which may cause the following race: CPU0 CPU1 ====

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2026-64417

    Mittel · CVSS 5.5EPSS 0,12%Korrektur verfügbar

    mm: shrinker: fix NULL pointer dereference in debugfs

    In the Linux kernel, the following vulnerability has been resolved: mm: shrinker: fix NULL pointer dereference in debugfs shrinker_debugfs_add() creates both "count" and "scan" debugfs files unconditionally. That assumes every shrinker implements both count_objects() and scan_objects(), which is not guaranteed. For example, the xen-backend shrinker sets count_objects() but leaves scan_objects() NULL, so writing to its scan file calls through a NULL function pointer and panics the kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:0x0 Code: Unable to access opcode bytes at 0xffffffffffffffd6. Call Trace: <T

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2026-64413

    Hoch · CVSS 7EPSS 0,13%Korrektur verfügbar

    netfilter: ebtables: zero chainstack array

    In the Linux kernel, the following vulnerability has been resolved: netfilter: ebtables: zero chainstack array sashiko reports: looking at ebtables table translation, could a sparse cpu_possible_mask lead to an uninitialized pointer free? If cpu_possible_mask is sparse (for example, CPU 0 and CPU 2 are possible, but CPU 1 is not), the allocation loop skips CPU 1. If vmalloc_node() fails at CPU 2, the cleanup loop will blindly decrement and call vfree() on newinfo->chainstack[1]. Not a real-world bug, such allocation isn't expected to fail in the first place.

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2026-64412

    Hoch · CVSS 7.1EPSS 0,13%Korrektur verfügbar

    netfilter: ebtables: module names must be null-terminated

    In the Linux kernel, the following vulnerability has been resolved: netfilter: ebtables: module names must be null-terminated We need to explicitly check the length, else we may pass non-null terminated string to request_module().

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2026-64411

    Hoch · CVSS 7.1EPSS 0,13%Korrektur verfügbar

    netfilter: ebtables: terminate table name before find_table_lock()

    In the Linux kernel, the following vulnerability has been resolved: netfilter: ebtables: terminate table name before find_table_lock() update_counters() and compat_update_counters() forward a user-supplied 32-byte table name to find_table_lock() without NUL-terminating it. On a lookup miss, find_inlist_lock() calls try_then_request_module(..., "%s%s", "ebtable_", name), and vsnprintf() reads past the name field and the stack object until it hits a zero byte. BUG: KASAN: stack-out-of-bounds in string (lib/vsprintf.c:648 lib/vsprintf.c:730) Read of size 1 at addr ffff8880119dfb20 by task exploit/147 Call Trace: ... string (lib/vsp

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2026-64409

    Mittel · CVSS 5.5EPSS 0,12%Korrektur verfügbar

    Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work()

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work() Every once in a while we see a hung btmtksdio_flush() task: INFO: task kworker/u17:0:189 blocked for more than 122 seconds. __cancel_work_timer+0x3f4/0x460 cancel_work_sync+0x1c/0x2c btmtksdio_flush+0x2c/0x40 hci_dev_open_sync+0x10c4/0x2190 [..] It all boils down to incorrect time_is_before_jiffies() usage in btmtksdio_txrx_work(). The btmtksdio_txrx_work() loop is expected to be terminated if running for longer than 5*HZ. However the timeout check is twisted: time_is_before_jiffies(old_jiffies + 5*

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2026-64408

    Hoch · CVSS 8.8EPSS 0,26%Korrektur verfügbar

    Bluetooth: bnep: pin L2CAP connection during netdev registration

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: bnep: pin L2CAP connection during netdev registration bnep_add_connection() reads the L2CAP connection without holding the channel lock, then passes its HCI device to register_netdev(). Controller teardown can clear and release that connection concurrently, leaving the network device registration path to dereference a freed parent device. Take a reference to the L2CAP connection while holding the channel lock. Retain it until register_netdev() has taken the parent device reference.

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2026-64407

    Hoch · CVSS 7.1EPSS 0,12%Korrektur verfügbar

    Bluetooth: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3()

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3() During the v3 firmware download the controller sends a v3_data_req with a 32 bit offset and a 16 bit len. nxp_recv_fw_req_v3() checks only the lower bound of the offset and then sends firmware from that offset. nxpdev->fw_dnld_v3_offset = offset - nxpdev->fw_v3_offset_correction; serdev_device_write_buf(nxpdev->serdev, nxpdev->fw->data + nxpdev->fw_dnld_v3_offset, len); Nothing checks that fw_dnld_v3_offset + len stays within nxpdev->fw->size, so a controller that a

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2026-64406

    Hoch · CVSS 8EPSS 0,27%Korrektur verfügbar

    Bluetooth: fix UAF in bt_accept_dequeue()

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix UAF in bt_accept_dequeue() bt_accept_get() takes a temporary reference before dropping the accept queue lock. bt_accept_dequeue() currently drops that reference before bt_accept_unlink(), leaving only the queue reference. bt_accept_unlink() drops the queue reference. The subsequent sock_hold() therefore accesses freed memory if it was the final reference, as observed by KASAN during listening L2CAP socket cleanup. Retain the temporary queue-walk reference through unlink and hand it to the caller on success. Drop it explicitly on the closed and not-yet-conne

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2026-64405

    Mittel · CVSS 5.7EPSS 0,12%Korrektur verfügbar

    Bluetooth: hci_conn: Fix null ptr deref in hci_abort_conn()

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: Fix null ptr deref in hci_abort_conn() hci_abort_conn() read hci_skb_event(hdev->sent_cmd) when a connection was pending, but hdev->sent_cmd can be NULL while req_status is still HCI_REQ_PEND, leading to a NULL pointer dereference and a general protection fault from the hci_rx_work() receive path. Instead of inspecting hdev->sent_cmd, track the in-flight create connection command with a new per-connection HCI_CONN_CREATE flag and route all cancellation through hci_cancel_connect_sync(), which dispatches to a dedicated per-type cancel function. The crea

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  18. CVE-2026-64404

    Mittel · CVSS 5.5EPSS 0,12%Korrektur verfügbar

    Bluetooth: ISO: avoid NULL deref of conn in iso_conn_big_sync()

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: avoid NULL deref of conn in iso_conn_big_sync() iso_conn_big_sync() drops the socket lock to call hci_get_route() and then re-acquires it, but dereferences iso_pi(sk)->conn->hcon afterwards without re-checking that conn is still valid. While the lock is dropped, the connection can be torn down under the same socket lock: iso_disconn_cfm() -> iso_conn_del() -> iso_chan_del() sets iso_pi(sk)->conn to NULL (and the broadcast teardown path can also clear conn->hcon on its own). When iso_conn_big_sync() re-acquires the lock and reads conn->hcon, conn may be NULL

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  19. CVE-2026-64403

    Hoch · CVSS 7.1EPSS 0,27%Korrektur verfügbar

    Bluetooth: L2CAP: validate option length before reading conf opt value

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: validate option length before reading conf opt value l2cap_get_conf_opt() derives the option length from the attacker-controlled opt->len field and immediately dereferences opt->val (as u8, get_unaligned_le16() or get_unaligned_le32(), or a raw pointer for the default case) before any caller has confirmed that opt->len bytes are present in the buffer. The callers (l2cap_parse_conf_req(), l2cap_parse_conf_rsp() and l2cap_conf_rfc_get()) only detect a malformed option afterwards, once the running length has gone negative, by which point the out-of-bounds rea

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  20. CVE-2026-64402

    Hoch · CVSS 7.8EPSS 0,13%Korrektur verfügbar

    coresight: ultrasoc-smb: Fix OOB write in smb_sync_perf_buffer()

    In the Linux kernel, the following vulnerability has been resolved: coresight: ultrasoc-smb: Fix OOB write in smb_sync_perf_buffer() When the SMB sink is used as a perf AUX sink, smb_update_buffer() calls smb_sync_perf_buffer() to copy hardware trace data into the perf AUX ring buffer pages. It derives pg_idx = head >> PAGE_SHIFT from @head, which is handle->head, and indexes dst_pages[pg_idx]. The pg_idx %= nr_pages normalization is only applied after the first loop iteration. This leaves the initial page index underived from the buffer size, which can result in an out-of-bounds write past dst_pages[] when head exceeds the AUX buffer size

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    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 →