p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-raspi-realtime · Seite 121

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für linux-raspi-realtime: 810. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 10733

  1. CVE-2026-80629

    Nicht bewertetEPSS 0,21%Keine Korrektur veröffentlicht

    octeontx2-af: npc: Fix size of entry2cntr_map

    In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: npc: Fix size of entry2cntr_map KASAN prints below splat. This is caused by allocating counter for reserved mcam entry for cpt 2nd pass entry. But mcam->entry2cntr_map is not allocated for reserved entries. BUG: KASAN: slab-out-of-bounds in npc_map_mcam_entry_and_cntr+0xb0/0x1a0 Write of size 2 at addr ffff0001033e7ffe by task kworker/0:1/14 CPU: 0 PID: 14 Comm: kworker/0:1 Not tainted 6.1.67 #1 Hardware name: Marvell CN106XX board (DT) Workqueue: events work_for_cpu_fn Call trace: dump_backtrace.part.0+0xe4/0xf0 show_stack+0x18/0x30 dump_stack_lvl+0x88/0

    Veröffentlicht Aktualisiert
  2. CVE-2026-80628

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

    ALSA: seq: oss: Serialize readq reset state with q->lock

    In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: oss: Serialize readq reset state with q->lock snd_seq_oss_readq_clear() resets qlen, head, and tail without q->lock even though the normal reader and producer paths serialize the same ring state under that spinlock. A reset can therefore race snd_seq_oss_readq_free() or snd_seq_oss_readq_put_event() and leave stale records in the queue, drop freshly queued ones, or report the wrong readiness after wakeup. KCSAN reports a data race between snd_seq_oss_readq_clear() and snd_seq_oss_readq_free(). Take q->lock while clearing the ring and resetting input_time. Factor

    Veröffentlicht Aktualisiert
  3. CVE-2026-80627

    Nicht bewertetEPSS 0,22%Keine Korrektur veröffentlicht

    MIPS: mm: Fix out-of-bounds write in maar_res_walk()

    In the Linux kernel, the following vulnerability has been resolved: MIPS: mm: Fix out-of-bounds write in maar_res_walk() maar_res_walk() uses wi->num_cfg as the index into the fixed-size wi->cfg array, but checks whether the array is full only after it has filled the selected entry. If walk_system_ram_range() reports more than 16 memory ranges, the overflow call writes one struct maar_config past the end of the array before WARN_ON() prevents num_cfg from advancing. Move the full-array check before taking the array slot and return non-zero when the scratch array is full, so walk_system_ram_range() terminates the walk instead of invoking th

    Veröffentlicht Aktualisiert
  4. CVE-2026-80626

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

    powerpc/perf: fix preempt count underflow in fsl_emb_pmu_del

    In the Linux kernel, the following vulnerability has been resolved: powerpc/perf: fix preempt count underflow in fsl_emb_pmu_del fsl_emb_pmu_del() unconditionally calls put_cpu_var(cpu_hw_events) at the 'out:' label, but only calls the matching get_cpu_var() after the 'i < 0' early-return check. When event->hw.idx is negative the function jumps to 'out:' without having taken get_cpu_var(), and the trailing put_cpu_var() then issues an unmatched preempt_enable(), underflowing preempt_count. On a CONFIG_PREEMPT=y kernel preempt_count would underflow and eventually present as a 'scheduling while atomic' BUG. Move put_cpu_var() to pair with g

    Veröffentlicht Aktualisiert
  5. CVE-2026-80624

    Nicht bewertetEPSS 0,21%Keine Korrektur veröffentlicht

    mfd: cs42l43: Sanity check firmware size

    In the Linux kernel, the following vulnerability has been resolved: mfd: cs42l43: Sanity check firmware size Currently the code checks if a firmware was received, however it does not verify that the firmware size is larger than the firmware header. As the firmware pointer is dereferenced as a pointer to the header structure this could lead to an out of bounds memory access. Add the missing check.

    Veröffentlicht Aktualisiert
  6. CVE-2026-80623

    Niedrig · CVSS 2EPSS 0,21%Keine Korrektur veröffentlicht

    coresight: ete: Always save state on power down

    In the Linux kernel, the following vulnerability has been resolved: coresight: ete: Always save state on power down System register ETMs and ETE are unlikely to be preserved on CPU power down. The ETE DT binding also never documented "arm,coresight-loses-context-with-cpu" so nobody would have legitimately been able to use that binding to fix it and ACPI has no such binding at all. Fix it by hard coding the setting for sysreg ETMs (ETE is always sysreg) or ACPI boots. Use a local variable when setting up save_state so that it's immune to concurrent probing when devices have different configurations which is an issue with modifying the globa

    Veröffentlicht Aktualisiert
  7. CVE-2026-80622

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

    char: tlclk: fix use-after-free in tlclk_cleanup()

    In the Linux kernel, the following vulnerability has been resolved: char: tlclk: fix use-after-free in tlclk_cleanup() This patch improves the module cleanup process in the tlclk driver to prevent potential use-after-free and race conditions. Currently, the file_operations structure does not specify the .owner field, which could allow the module to be unloaded while user-space processes are still interacting with the device. Additionally, the tlclk_cleanup() function frees the alarm_events memory before ensuring that blocked processes in the waitqueue are fully awakened and that the switchover_timer has completed. To address these cases,

    Veröffentlicht Aktualisiert
  8. CVE-2026-80620

    Nicht bewertetEPSS 0,21%Keine Korrektur veröffentlicht

    Revert "PCI/MSI: Unmap MSI-X region on error"

    In the Linux kernel, the following vulnerability has been resolved: Revert "PCI/MSI: Unmap MSI-X region on error" This reverts commit 1a8d4c6ecb4c81261bcdf13556abd4a958eca202. Commit 1a8d4c6ecb4c ("PCI/MSI: Unmap MSI-X region on error") added an iounmap(dev->msix_base) on the error path of msix_capability_init() to release the MSI-X region when msix_setup_interrupts() fails. When msix_setup_interrupts() fails, the call chain is: msix_setup_interrupts() -> __msix_setup_interrupts() struct pci_dev *dev __free(free_msi_irqs) = __dev; ... return ret; // __free cleanup fires on error The __free(free_msi_irqs

    Veröffentlicht Aktualisiert
  9. CVE-2026-80619

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

    apparmor: fix potential UAF in aa_replace_profiles

    In the Linux kernel, the following vulnerability has been resolved: apparmor: fix potential UAF in aa_replace_profiles The function aa_replace_profiles was accessing udata->size after calling aa_put_loaddata(udata), causing a potential UAF. Fixed this by saving the size to a local variable before dropping the reference.

    Veröffentlicht Aktualisiert
  10. CVE-2026-80618

    Nicht bewertetEPSS 0,21%Keine Korrektur veröffentlicht

    drm/amdkfd: Avoid double-unpin of DOORBELL/MMIO BOs on free

    In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Avoid double-unpin of DOORBELL/MMIO BOs on free amdgpu_amdkfd_gpuvm_free_memory_of_gpu() unpinned DOORBELL and MMIO remap BOs (which are pinned at allocation time) before checking whether the BO is still mapped to the GPU. When the BO is still mapped, the function returns -EBUSY and leaves the BO alive, but it has already been unpinned. The BO is then unpinned again when it is finally freed during process teardown, triggering a ttm_bo_unpin() underflow warning: WARNING: CPU: 18 PID: 15066 at ttm/ttm_bo.c:650 amdttm_bo_unpin+0x6d/0x80 [amdttm] Workqueue: kfd

    Veröffentlicht Aktualisiert
  11. CVE-2026-80616

    Niedrig · CVSS 1.8EPSS 0,23%Keine Korrektur veröffentlicht

    ieee802154: Avoid calling WARN_ON() on -ENOMEM in cfg802154_switch_netns()

    In the Linux kernel, the following vulnerability has been resolved: ieee802154: Avoid calling WARN_ON() on -ENOMEM in cfg802154_switch_netns() It's pointless to call WARN_ON() in case of an allocation failure in dev_change_net_namespace() and device_rename(), since it only leads to useless splats caused by deliberate fault injections, so avoid it. Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

    Veröffentlicht Aktualisiert
  12. CVE-2026-80613

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

    veth: fix NAPI leak in XDP enable error path

    In the Linux kernel, the following vulnerability has been resolved: veth: fix NAPI leak in XDP enable error path During XDP enablement in veth, if xdp_rxq_info_reg() or xdp_rxq_info_reg_mem_model() fails, the driver rolls back the changes. However, the rollback loop: for (i--; i >= start; i--) { decrements the loop index 'i' before the first iteration. This correctly skips unregistering the rxq for the failed index 'i' (as registration failed or was already cleaned up), but it also erroneously skips calling netif_napi_deli() for rq[i].xdp_napi. Since netif_napi_add() was already called for index 'i', this leaves a dangling napi_struct i

    Veröffentlicht Aktualisiert
  13. CVE-2026-80611

    Nicht bewertetEPSS 0,21%Keine Korrektur veröffentlicht

    ACPI: processor_idle: Mark LPI enter functions as __cpuidle

    In the Linux kernel, the following vulnerability has been resolved: ACPI: processor_idle: Mark LPI enter functions as __cpuidle When function tracing or Kprobes is enabled, entering an ACPI Low Power Idle (LPI) state triggers the following RCU splat: RCU not on for: acpi_idle_lpi_enter+0x4/0xd8 WARNING: CPU: 8 PID: 0 at include/linux/trace_recursion.h:162 function_trace_call+0x1e8/0x228 The acpi_idle_lpi_enter() function is invoked within the cpuidle path after RCU has already been disabled for the current local CPU. Consequently, ftrace's function_trace_call() expects RCU to be actively watching before recording trace data, emitting

    Veröffentlicht Aktualisiert
  14. CVE-2026-80607

    Nicht bewertetEPSS 0,21%Keine Korrektur veröffentlicht

    tracing/probes: Remove WARN_ON_ONCE from parse_btf_arg

    In the Linux kernel, the following vulnerability has been resolved: tracing/probes: Remove WARN_ON_ONCE from parse_btf_arg Sashiko found that user can cause this WARN_ON_ONCE() easily with adding a kprobe event based on a raw address with BTF parameter. Since this is not an unexpected condition, remove the WARN_ON_ONCE().

    Veröffentlicht Aktualisiert
  15. CVE-2026-80605

    Nicht bewertetEPSS 0,22%Keine Korrektur veröffentlicht

    HID: picolcd: prevent NULL pointer dereference in picolcd_send_and_wait()

    In the Linux kernel, the following vulnerability has been resolved: HID: picolcd: prevent NULL pointer dereference in picolcd_send_and_wait() In picolcd_send_and_wait(), an integer overflow of the signed loop counter 'k' can theoretically lead to a NULL pointer dereference of 'raw_data'. If the loop executes more than INT_MAX times, 'k' becomes negative, making the condition 'k < size' true even when 'size' is 0. Change the type of 'k' to 'unsigned int' to prevent the overflow and eliminate the out-of-bounds access. Found by Linux Verification Center (linuxtesting.org) with the Svace static analysis tool. [[email protected]: extended hash

    Veröffentlicht Aktualisiert
  16. CVE-2026-80603

    Kritisch · CVSS 9.1EPSS 0,6%Keine Korrektur veröffentlicht

    netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read parse_dcc() treats data_end as an inclusive end pointer, but its only caller passes data_limit = ib_ptr + datalen, which points one past the last valid byte. The newline search loop iterates while tmp <= data_end, so when no newline is present, *tmp is read at tmp == data_end, one byte beyond the region filled by skb_header_pointer(). irc_buffer is kmalloc'd as MAX_SEARCH_SIZE + 1 bytes and datalen is capped at MAX_SEARCH_SIZE, so the stray read does not fault. The byte is uninitialized or stale; if it cont

    Veröffentlicht Aktualisiert
  17. CVE-2026-80602

    Nicht bewertetEPSS 0,21%Keine Korrektur veröffentlicht

    perf/x86/amd/lbr: Fix kernel address leakage

    In the Linux kernel, the following vulnerability has been resolved: perf/x86/amd/lbr: Fix kernel address leakage A user-only branch stack can contain branches that originate from the kernel. As a result, kernel addresses are exposed to user space even when PERF_SAMPLE_BRANCH_USER is requested. On AMD processors supporting X86_FEATURE_AMD_LBR_V2, perf can still report SYSRET/ERET entries for which the branch-from addresses are in the kernel. E.g. $ perf record -e cycles -o - -j any,save_type,u -- \ perf bench syscall basic --loop 1000 | \ perf script -i - -F brstack|tr ' ' '\n'| \ grep -E '0x[89a-f][0-9a-f]{15}'

    Veröffentlicht Aktualisiert
  18. CVE-2026-80601

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

    batman-adv: gw: acquire ethernet header only after skb realloc

    In the Linux kernel, the following vulnerability has been resolved: batman-adv: gw: acquire ethernet header only after skb realloc The pskb_may_pull() called by batadv_get_vid() could reallocate the buffer behind the skb. Variables which were pointing to the old buffer need to be reassigned to avoid an use-after-free.

    Veröffentlicht Aktualisiert
  19. CVE-2026-80600

    Kritisch · CVSS 9.8EPSS 0,73%Keine Korrektur veröffentlicht

    batman-adv: dat: acquire ARP hw source only after skb realloc

    In the Linux kernel, the following vulnerability has been resolved: batman-adv: dat: acquire ARP hw source only after skb realloc The pskb_may_pull() called by batadv_get_vid() could reallocate the buffer behind the skb. Variables which were pointing to the old buffer need to be reassigned to avoid an use-after-free.

    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 →