p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-fips · Seite 184

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 6635

  1. CVE-2025-38540

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

    HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras

    In the Linux kernel, the following vulnerability has been resolved: HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras The Chicony Electronics HP 5MP Cameras (USB ID 04F2:B824 & 04F2:B82C) report a HID sensor interface that is not actually implemented. Attempting to access this non-functional sensor via iio_info causes system hangs as runtime PM tries to wake up an unresponsive sensor. Add these 2 devices to the HID ignore list since the sensor interface is non-functional by design and should not be exposed to userspace.

    Veröffentlicht Aktualisiert
  2. CVE-2025-38539

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

    tracing: Add down_write(trace_event_sem) when adding trace event

    In the Linux kernel, the following vulnerability has been resolved: tracing: Add down_write(trace_event_sem) when adding trace event When a module is loaded, it adds trace events defined by the module. It may also need to modify the modules trace printk formats to replace enum names with their values. If two modules are loaded at the same time, the adding of the event to the ftrace_events list can corrupt the walking of the list in the code that is modifying the printk format strings and crash the kernel. The addition of the event should take the trace_event_sem for write while it adds the new event. Also add a lockdep_assert_held() on t

    Veröffentlicht Aktualisiert
  3. CVE-2025-38538

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

    dmaengine: nbpfaxi: Fix memory corruption in probe()

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: nbpfaxi: Fix memory corruption in probe() The nbpf->chan[] array is allocated earlier in the nbpf_probe() function and it has "num_channels" elements. These three loops iterate one element farther than they should and corrupt memory. The changes to the second loop are more involved. In this case, we're copying data from the irqbuf[] array into the nbpf->chan[] array. If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync. I added a check to ensure that we don't go beyond the end of the irqbuf[] array. I'm pretty sure thi

    Veröffentlicht Aktualisiert
  4. CVE-2025-38530

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

    comedi: pcl812: Fix bit shift out of bounds

    In the Linux kernel, the following vulnerability has been resolved: comedi: pcl812: Fix bit shift out of bounds When checking for a supported IRQ number, the following test is used: if ((1 << it->options[1]) & board->irq_bits) { However, `it->options[i]` is an unchecked `int` value from userspace, so the shift amount could be negative or out of bounds. Fix the test by requiring `it->options[1]` to be within bounds before proceeding with the original test. Valid `it->options[1]` values that select the IRQ will be in the range [1,15]. The value 0 explicitly disables the use of interrupts.

    Veröffentlicht Aktualisiert
  5. CVE-2025-38529

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

    comedi: aio_iiro_16: Fix bit shift out of bounds

    In the Linux kernel, the following vulnerability has been resolved: comedi: aio_iiro_16: Fix bit shift out of bounds When checking for a supported IRQ number, the following test is used: if ((1 << it->options[1]) & 0xdcfc) { However, `it->options[i]` is an unchecked `int` value from userspace, so the shift amount could be negative or out of bounds. Fix the test by requiring `it->options[1]` to be within bounds before proceeding with the original test. Valid `it->options[1]` values that select the IRQ will be in the range [1,15]. The value 0 explicitly disables the use of interrupts.

    Veröffentlicht Aktualisiert
  6. CVE-2025-38527

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

    smb: client: fix use-after-free in cifs_oplock_break

    In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-after-free in cifs_oplock_break A race condition can occur in cifs_oplock_break() leading to a use-after-free of the cinode structure when unmounting: cifs_oplock_break() _cifsFileInfo_put(cfile) cifsFileInfo_put_final() cifs_sb_deactive() [last ref, start releasing sb] kill_sb() kill_anon_super() generic_shutdown_super() evict_inodes() dispose_list() evict() destroy_inode()

    Veröffentlicht Aktualisiert
  7. CVE-2025-38524

    Hoch · CVSS 7.5EPSS 0,3%Keine Korrektur veröffentlicht

    rxrpc: Fix recv-recv race of completed call

    In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix recv-recv race of completed call If a call receives an event (such as incoming data), the call gets placed on the socket's queue and a thread in recvmsg can be awakened to go and process it. Once the thread has picked up the call off of the queue, further events will cause it to be requeued, and once the socket lock is dropped (recvmsg uses call->user_mutex to allow the socket to be used in parallel), a second thread can come in and its recvmsg can pop the call off the socket queue again. In such a case, the first thread will be receiving stuff from the call an

    Veröffentlicht Aktualisiert
  8. CVE-2025-38516

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

    pinctrl: qcom: msm: mark certain pins as invalid for interrupts

    In the Linux kernel, the following vulnerability has been resolved: pinctrl: qcom: msm: mark certain pins as invalid for interrupts On some platforms, the UFS-reset pin has no interrupt logic in TLMM but is nevertheless registered as a GPIO in the kernel. This enables the user-space to trigger a BUG() in the pinctrl-msm driver by running, for example: `gpiomon -c 0 113` on RB2. The exact culprit is requesting pins whose intr_detection_width setting is not 1 or 2 for interrupts. This hits a BUG() in msm_gpio_irq_set_type(). Potentially crashing the kernel due to an invalid request from user-space is not optimal, so let's go through the pins

    Veröffentlicht Aktualisiert
  9. CVE-2025-38514

    Hoch · CVSS 7.5EPSS 0,37%Keine Korrektur veröffentlicht

    rxrpc: Fix oops due to non-existence of prealloc backlog struct

    In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix oops due to non-existence of prealloc backlog struct If an AF_RXRPC service socket is opened and bound, but calls are preallocated, then rxrpc_alloc_incoming_call() will oops because the rxrpc_backlog struct doesn't get allocated until the first preallocation is made. Fix this by returning NULL from rxrpc_alloc_incoming_call() if there is no backlog struct. This will cause the incoming call to be aborted.

    Veröffentlicht Aktualisiert
  10. CVE-2025-38513

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

    wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev()

    In the Linux kernel, the following vulnerability has been resolved: wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() There is a potential NULL pointer dereference in zd_mac_tx_to_dev(). For example, the following is possible: T0 T1 zd_mac_tx_to_dev() /* len == skb_queue_len(q) */ while (len > ZD_MAC_MAX_ACK_WAITERS) { filter_ack() spin_lock_irqsave(&q->lock, flags); /* position == skb_queue_len(q) */ for (i=1; i<position; i++) skb = __skb_dequeue(q) if (mac->type == NL80211_IFTYPE_AP) skb = __skb_dequeue(q); spin_unl

    Veröffentlicht Aktualisiert
  11. CVE-2025-38498

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

    do_change_type(): refuse to operate on unmounted/not ours mounts

    In the Linux kernel, the following vulnerability has been resolved: do_change_type(): refuse to operate on unmounted/not ours mounts Ensure that propagation settings can only be changed for mounts located in the caller's mount namespace. This change aligns permission checking with the rest of mount(2).

    Veröffentlicht Aktualisiert
  12. CVE-2025-38497

    Hoch · CVSS 7.1EPSS 0,19%Keine Korrektur veröffentlicht

    usb: gadget: configfs: Fix OOB read on empty string write

    In the Linux kernel, the following vulnerability has been resolved: usb: gadget: configfs: Fix OOB read on empty string write When writing an empty string to either 'qw_sign' or 'landingPage' sysfs attributes, the store functions attempt to access page[l - 1] before validating that the length 'l' is greater than zero. This patch fixes the vulnerability by adding a check at the beginning of os_desc_qw_sign_store() and webusb_landingPage_store() to handle the zero-length input case gracefully by returning immediately.

    Veröffentlicht Aktualisiert
  13. CVE-2025-38495

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

    HID: core: ensure the allocated report buffer can contain the reserved report ID

    In the Linux kernel, the following vulnerability has been resolved: HID: core: ensure the allocated report buffer can contain the reserved report ID When the report ID is not used, the low level transport drivers expect the first byte to be 0. However, currently the allocated buffer not account for that extra byte, meaning that instead of having 8 guaranteed bytes for implement to be working, we only have 7.

    Veröffentlicht Aktualisiert
  14. CVE-2025-38494

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

    HID: core: do not bypass hid_hw_raw_request

    In the Linux kernel, the following vulnerability has been resolved: HID: core: do not bypass hid_hw_raw_request hid_hw_raw_request() is actually useful to ensure the provided buffer and length are valid. Directly calling in the low level transport driver function bypassed those checks and allowed invalid paramto be used.

    Veröffentlicht Aktualisiert
  15. CVE-2025-38487

    Mittel · CVSS 5.5EPSS 0,18%Keine Korrektur veröffentlicht

    soc: aspeed: lpc-snoop: Don't disable channels that aren't enabled

    In the Linux kernel, the following vulnerability has been resolved: soc: aspeed: lpc-snoop: Don't disable channels that aren't enabled Mitigate e.g. the following: # echo 1e789080.lpc-snoop > /sys/bus/platform/drivers/aspeed-lpc-snoop/unbind ... [ 120.363594] Unable to handle kernel NULL pointer dereference at virtual address 00000004 when write [ 120.373866] [00000004] *pgd=00000000 [ 120.377910] Internal error: Oops: 805 [#1] SMP ARM [ 120.383306] CPU: 1 UID: 0 PID: 315 Comm: sh Not tainted 6.15.0-rc1-00009-g926217bc7d7d-dirty #20 NONE ... [ 120.679543] Call trace: [ 120.679559] misc_deregister

    Veröffentlicht Aktualisiert
  16. CVE-2025-38483

    Hoch · CVSS 7.1EPSS 0,19%Keine Korrektur veröffentlicht

    comedi: das16m1: Fix bit shift out of bounds

    In the Linux kernel, the following vulnerability has been resolved: comedi: das16m1: Fix bit shift out of bounds When checking for a supported IRQ number, the following test is used: /* only irqs 2, 3, 4, 5, 6, 7, 10, 11, 12, 14, and 15 are valid */ if ((1 << it->options[1]) & 0xdcfc) { However, `it->options[i]` is an unchecked `int` value from userspace, so the shift amount could be negative or out of bounds. Fix the test by requiring `it->options[1]` to be within bounds before proceeding with the original test.

    Veröffentlicht Aktualisiert
  17. CVE-2025-38482

    Hoch · CVSS 7.1EPSS 0,19%Keine Korrektur veröffentlicht

    comedi: das6402: Fix bit shift out of bounds

    In the Linux kernel, the following vulnerability has been resolved: comedi: das6402: Fix bit shift out of bounds When checking for a supported IRQ number, the following test is used: /* IRQs 2,3,5,6,7, 10,11,15 are valid for "enhanced" mode */ if ((1 << it->options[1]) & 0x8cec) { However, `it->options[i]` is an unchecked `int` value from userspace, so the shift amount could be negative or out of bounds. Fix the test by requiring `it->options[1]` to be within bounds before proceeding with the original test. Valid `it->options[1]` values that select the IRQ will be in the range [1,15]. The value 0 explicitly disables the use of interru

    Veröffentlicht Aktualisiert
  18. CVE-2025-38481

    Mittel · CVSS 5.5EPSS 0,19%Keine Korrektur veröffentlicht

    comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large

    In the Linux kernel, the following vulnerability has been resolved: comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large The handling of the `COMEDI_INSNLIST` ioctl allocates a kernel buffer to hold the array of `struct comedi_insn`, getting the length from the `n_insns` member of the `struct comedi_insnlist` supplied by the user. The allocation will fail with a WARNING and a stack dump if it is too large. Avoid that by failing with an `-EINVAL` error if the supplied `n_insns` value is unreasonable. Define the limit on the `n_insns` value in the `MAX_INSNS` macro. Set this to the same value as `MAX_SAMPLES` (65536), which is the ma

    Veröffentlicht Aktualisiert
  19. CVE-2025-38480

    Mittel · CVSS 5.5EPSS 0,19%Keine Korrektur veröffentlicht

    comedi: Fix use of uninitialized data in insn_rw_emulate_bits()

    In the Linux kernel, the following vulnerability has been resolved: comedi: Fix use of uninitialized data in insn_rw_emulate_bits() For Comedi `INSN_READ` and `INSN_WRITE` instructions on "digital" subdevices (subdevice types `COMEDI_SUBD_DI`, `COMEDI_SUBD_DO`, and `COMEDI_SUBD_DIO`), it is common for the subdevice driver not to have `insn_read` and `insn_write` handler functions, but to have an `insn_bits` handler function for handling Comedi `INSN_BITS` instructions. In that case, the subdevice's `insn_read` and/or `insn_write` function handler pointers are set to point to the `insn_rw_emulate_bits()` function by `__comedi_device_postcon

    Veröffentlicht Aktualisiert
  20. CVE-2025-38478

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

    comedi: Fix initialization of data for instructions that write to subdevice

    In the Linux kernel, the following vulnerability has been resolved: comedi: Fix initialization of data for instructions that write to subdevice Some Comedi subdevice instruction handlers are known to access instruction data elements beyond the first `insn->n` elements in some cases. The `do_insn_ioctl()` and `do_insnlist_ioctl()` functions allocate at least `MIN_SAMPLES` (16) data elements to deal with this, but they do not initialize all of that. For Comedi instruction codes that write to the subdevice, the first `insn->n` data elements are copied from user-space, but the remaining elements are left uninitialized. That could be a proble

    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 →