p PatchFirst

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

Уязвимости linux-oem-5.17 · Страница 97

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

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

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

  1. CVE-2026-92493

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

    cpufreq: amd-pstate-ut: Skip tests when amd-pstate driver is not active

    In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate-ut: Skip tests when amd-pstate driver is not active The crash issue may occur when modprobe amd_pstate_ut on intel platform. amd_pstate_ut: 1 amd_pstate_ut_acpi_cpc_valid success! amd_pstate_ut: 2 amd_pstate_ut_check_enabled success! BUG: kernel NULL pointer dereference, address: 0000000000000080 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI CPU: 0 PID: 20300 Comm: modprobe Kdump: loaded Tainted: G O 6.6.0-0010.rc1.ctl4.x86_64 #1 Hardware

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

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

    cpufreq/amd-pstate: handle missing policy in dynamic EPP callbacks

    In the Linux kernel, the following vulnerability has been resolved: cpufreq/amd-pstate: handle missing policy in dynamic EPP callbacks cpufreq_cpu_get() returns NULL when no cpufreq policy is associated with the requested CPU, for example because the CPU is offline or the policy has already been torn down. Both amd_pstate_power_supply_notifier() and amd_pstate_profile_set() acquire a policy via cpufreq_cpu_get() and then pass that pointer to amd_pstate_get_balanced_epp() and amd_pstate_set_epp(), which dereference it unconditionally. A racing CPU hotplug or driver teardown can therefore lead to a NULL pointer dereference on either of thes

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

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

    firmware: arm_scmi: Roll back partial protocol table registration

    In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Roll back partial protocol table registration scmi_protocol_table_register() can leave earlier requests registered when a later entry in the same ID table fails. Each request retains a pointer to the driver's ID table, so a failed module load can leave a dangling pointer after the module storage is released. Unrequest only the successfully registered prefix, in reverse order, before returning the failure. Leave the failed entry and the remaining entries untouched because matching requests can be owned by another driver.

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

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

    firmware: arm_scmi: Unrequest devices if driver registration fails

    In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Unrequest devices if driver registration fails scmi_driver_register() requests protocol devices before registering the driver. If driver_register() fails, those requests remain in the global IDR and retain pointers to the module's ID table. Once the failed module load releases that storage, later request matching or SCMI device creation can dereference the stale pointers. Unrequest the complete protocol table before returning the registration failure. At this point table registration succeeded, so every entry is owned by the current registration attempt

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

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

    xfrm: Fix skb double-free in xfrm_dev_direct_output()

    In the Linux kernel, the following vulnerability has been resolved: xfrm: Fix skb double-free in xfrm_dev_direct_output() A return value other than 1 from local_out() means that the skb has been consumed or its ownership was transferred. xfrm_dev_direct_output() nevertheless frees the skb on this path, causing a double-free when netfilter drops the packet and invalidating any other owner. Return the local_out() result directly, matching the ownership handling in xfrm_output_resume().

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

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

    RDMA/erdma: complete object teardown when the destroy command fails

    In the Linux kernel, the following vulnerability has been resolved: RDMA/erdma: complete object teardown when the destroy command fails erdma_destroy_qp(), erdma_destroy_cq(), erdma_dereg_mr(), and erdma_destroy_ah() returned early when erdma_post_cmd_wait() failed, leaking the queue buffers, MTTs, doorbells and the STAG, QPN, CQN and AHN identifiers. A command timeout clears ERDMA_CMDQ_STATE_OK_BIT and permanently disables the command queue, so no retry can succeed; the RDMA core keeps the object after a failed destructor and forced uverbs cleanup then nulls the pointers, making the resources unreachable. Warn on failure but release every

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

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

    exfat: fix valid_size extension over a shared writable mapping

    In the Linux kernel, the following vulnerability has been resolved: exfat: fix valid_size extension over a shared writable mapping When a shared writable mapping has its valid_size extended by a buffered write or a page fault, exfat zeroes the page-cache gap below the new valid_size. A store through the mapping can race with this zeroing and be overwritten. Fix this by zeroing the gap lazily. Drop ->map_pages so that every first write fault goes through exfat_page_mkwrite(), which advances valid_size to cover the faulting page. With fault-around enabled, a store could install a writable PTE, skip ->page_mkwrite(), and land past valid_size

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

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

    bpf: Fix CFI mismatch in task work callback

    In the Linux kernel, the following vulnerability has been resolved: bpf: Fix CFI mismatch in task work callback BPF subprograms use the bpf_callback_t ABI, but task work invokes the callback through a three-argument function pointer. This trips kCFI. Store and invoke the callback as bpf_callback_t.

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

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

    bpf: Fix WARNING in bpf_tracing_link_release

    In the Linux kernel, the following vulnerability has been resolved: bpf: Fix WARNING in bpf_tracing_link_release The trampoline could be corrupted by the blindly 'tr->flags = BPF_TRAMP_F_TAIL_CALL_CTX' in verifier. 1. A fexit attached to a tail_call_reachable prog. 'tr->flags' became 'BPF_TRAMP_F_CALL_ORIG | BPF_TRAMP_F_TAIL_CALL_CTX'. And, the trampoline would poke the target prog's nop insn using jmp insn instead of call insn. 2. Another fexit loaded with the same tail_call_reachable prog target. 'tr->flags' became 'BPF_TRAMP_F_TAIL_CALL_CTX'. 3. Close the first fexit link. Due to no BPF_TRAMP_F_CALL_ORIG in 'tr->flags', t

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

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

    cxl/region: Fix use-after-free in find_pos_and_ways() error path

    In the Linux kernel, the following vulnerability has been resolved: cxl/region: Fix use-after-free in find_pos_and_ways() error path The error path releases its reference to a switch decoder before logging an error that includes the decoder name. If the released reference is the last one, the decoder can be freed before the error message accesses its name. Drop the reference after the error is reported.

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

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

    liveupdate: Remember FLB retrieve() status

    In the Linux kernel, the following vulnerability has been resolved: liveupdate: Remember FLB retrieve() status LUO keeps track of successful retrieve attempts on an FLB. It does so to avoid multiple retrievals of the same FLB. Multiple retrievals cause problems because once the FLB is retrieved, the serialized data structures are likely freed and the FLB is likely in a very different state from what the code expects. All this works well when retrieve succeeds. When it fails, luo_flb_retrieve_one() returns the error immediately, without ever storing anywhere that a retrieve was attempted or what its error code was. If the user attempts to r

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

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

    pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip

    In the Linux kernel, the following vulnerability has been resolved: pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip The gpio_chip is allocated with device-managed memory but registered with the non-managed gpiochip_add_data(). This was harmless while the drivers were built-in, but once they can be built as modules and unbound/rmmod'd, devm frees the gpio_chip's memory while it is still registered, causing a use-after-free. Register it with devm_gpiochip_add_data() so it shares the same device-managed lifecycle, which also lets the manual gpiochip_remove() error paths go away.

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

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

    pinctrl: mediatek: free EINT resources on unbind

    In the Linux kernel, the following vulnerability has been resolved: pinctrl: mediatek: free EINT resources on unbind mtk_eint_do_init() creates an IRQ domain, populates it with a mapping for every EINT line and installs a chained handler on the parent interrupt, but none of these are ever released. This was harmless while the drivers were built-in, but now that they can be built as modules and unbound/rmmod'd it leaves behind a dangling IRQ domain, interrupt mappings whose chip data points at freed memory, and a chained handler that keeps firing into that freed data. The plain allocations in mtk_eint_do_init() already use the device-manage

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

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

    scsi: ufs: core: Validate string descriptors

    In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Validate string descriptors The string descriptor length includes a two-byte header while the UTF-16 payload starts after it. utf16s_to_utf8s() expects a count of UTF-16 code units, not bytes. Passing the payload byte count can make it read beyond the descriptor buffer. Validate that the payload has an even byte count, pass a code-unit count to the converter, and allocate sufficient UTF-8 output space. The raw string buffer starts after the descriptor header but its size is bLength. Copying bLength bytes from that pointer can read beyond the response buff

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

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

    scsi: ufs: Avoid NULL CQE dereference when reporting invalid tags

    In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: Avoid NULL CQE dereference when reporting invalid tags The single-doorbell completion path can call ufshcd_compl_one_cqe() with a NULL CQE. If no command is associated with the completion tag, the warning message dereferences the CQE while reporting the error. Avoid that dereference and include the invalid tag in the warning.

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

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

    scsi: ufs: core: Validate connected lane counts

    In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Validate connected lane counts The connected lane count is used by TX equalization code to index arrays sized by UFS_MAX_LANES. Reject zero and out-of-range RX or TX lane counts before they can be propagated.

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

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

    scsi: ufs: debugfs: Reserve space for a string terminator

    In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: debugfs: Reserve space for a string terminator ufs_saved_err_write() copies user input into a zero-initialized stack buffer and passes it to kstrtoint(). A write that fills the entire buffer overwrites its only terminator. Reject an input whose length leaves no room for the trailing NUL.

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

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

    crypto: keembay - Initialize completion before requesting IRQ

    In the Linux kernel, the following vulnerability has been resolved: crypto: keembay - Initialize completion before requesting IRQ kmb_ocs_aes_probe() requests the device IRQ before initializing irq_completion. Once the handler is registered it can run immediately, and ocs_aes_irq_handler() unconditionally calls complete(). An interrupt in this window would therefore use an uninitialized completion. Initialize the completion before requesting the IRQ, as the sibling OCS HCU and ECC drivers already do.

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

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

    RDMA/mlx5: Fix integer overflow of user QP buffer size

    In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix integer overflow of user QP buffer size set_user_buf_size() computes the QP buffer size by left-shifting the user-supplied rq.wqe_cnt and rq.wqe_shift values as signed integers. A sufficiently large rq.wqe_cnt causes signed integer overflow, which is undefined behavior, and yields a small or negative buf_size, causing ib_umem_get() to map a buffer smaller than the hardware will actually write into. Replace the shifts and addition with check_shl_overflow() and check_add_overflow(), rejecting invalid user inputs. Moreover, guard the identical shift computing

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

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

    isofs: release zisofs block pointer buffer head

    In the Linux kernel, the following vulnerability has been resolved: isofs: release zisofs block pointer buffer head zisofs_fill_pages() reads the compressed block pointer table. The error paths release the current buffer_head, the loop also releases the old buffer_head when it advances. However, the success path leaves the last buffer_head referenced. Release it before returning success.

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

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

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

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