Vulnerabilidades
Resumen — últimos 7 días
Vulnerabilidades nuevas2739▼ 510 respecto a la semana anterior
Críticas / altas1303▼ 212 respecto a la semana anterior
Nueva explotación activa (KEV)3▼ 5 respecto a la semana anterior
Sin puntuar (sin CVSS)225▼ 276 respecto a la semana anterior
34.312 resultados, ordenados por fecha de publicación (más recientes primero)
| CVE | Estado | Severidad | EPSS | Explotación activa | Tecnologías afectadas | Publicada ▼ | Modificada | Descripción |
|---|---|---|---|---|---|---|---|---|
| Recibida | Alta (7.8) | 0.15% | — | Linux KernelAI | 25/9/2026 | 25/9/2026 | In the Linux kernel, the following vulnerability has been resolved: mm/slab: take n->list_lock in __slab_try_return_freelist() to avoid race Commit ba7425312607 ("mm, slab: add an optimistic __slab_try_return_freelist()") incorrectly assumed that nobody has freed an object to the slab as long as slab->freelist is NULL… | |
| Recibida | Alta (7.8) | 0.16% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: ipv6: fix fib6 walker UAF on seq stop ipv6_route_iter_active() treats a walker in FWS_U at the table root as already unlinked. fib6_del_route() can move a still-linked walker into that same state when the current leaf is the last route at the root, so… | |
| Recibida | Sin puntuar | 0.20% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: ipmr: account multicast table and route memory A netadmin in a user+net namespace can create many IPv4 and IPv6 multicast routing tables with MRT_TABLE and MRT6_TABLE. Each unseen id allocates an mr_table via the shared mr_table_alloc(), links it into… | |
| Recibida | Sin puntuar | 0.20% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: reboot: fix cad_pid use-after-free race cad_pid is a single kernel-wide struct pid pointer. proc_do_cad_pid() reads it and passes it to pid_vnr() without protecting the lifetime of the referenced struct pid. A concurrent writer can replace cad_pid and… | |
| Recibida | Alta (7.8) | 0.15% | — | Linux KernelAI | 25/9/2026 | 25/9/2026 | In the Linux kernel, the following vulnerability has been resolved: ftrace: fork: Initialize function graph state before copy_exec_state() dup_task_struct() copies the parent's task_struct, including ret_stack. ftrace_graph_init_task() clears the copied function graph state, but it currently runs after… | |
| Recibida | Sin puntuar | 0.20% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: tracing: Fix memory corruption from the histogram stacktrace modifier parse_field() sets HIST_FIELD_FL_STACKTRACE from the ".stacktrace" modifier before it looks the field name up, and nothing afterwards checks that the name resolved to a field which… | |
| Recibida | Sin puntuar | 0.17% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: tracing: Set the trace clock before registering the histogram trigger hist_register_trigger() puts the trigger on the global named_triggers list in cmd_ops->init(), and only then sets the trace clock: The clock string is not checked anywhere before… | |
| Recibida | Sin puntuar | 0.20% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: tracing: Fix memory corruption from a "STACKTRACE" histogram key "cpu", "CPU", "stacktrace" and "STACKTRACE" are generic fields, defined with an offset and a size of zero so that the filter code can match them by name. parse_field() maps them onto… | |
| Recibida | Sin puntuar | 0.20% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: tracing: Take trace_array reference when opening a tracer options file When a tracer option file is opened, it is passed a descriptor that points to an element on the trace_array's topts array. This element has information to find the trace array and… | |
| Recibida | Sin puntuar | 0.19% | — | Linux KernelAI | 25/9/2026 | 25/9/2026 | In the Linux kernel, the following vulnerability has been resolved: tracing: Don't dereference trace_event_file in deferred trigger free The enable_event trigger defers trace_event_put_ref() to the trigger free kthread, but the trace_event_file can already be freed when the instance is removed. Keep the… | |
| Recibida | Alta (7) | 0.14% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: ALSA: us122l: Prevent write upgrades for read mappings The hwdep mmap callback rejects read-buffer mappings that are initially writable, but leaves VM_MAYWRITE set on mappings created with PROT_READ. A process that can open the hwdep node O_RDWR can… | |
| Recibida | Sin puntuar | 0.21% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf The in04_last array in struct usx2ydev is declared as char[24], but in04_buf is allocated as sizeof(struct us428_ctls) which is 21 bytes. In i_usx2y_in04_int(), when ctl_snapshot_last ==… | |
| Recibida | Sin puntuar | 0.20% | — | Linux KernelAI | 25/9/2026 | 25/9/2026 | In the Linux kernel, the following vulnerability has been resolved: ALSA: usbusx2y: validate URB actual_length in interrupt callback i_usx2y_in04_int() processes the interrupt URB data without checking urb->actual_length. A short transfer from a malfunctioning device would cause the handler to process uninitialized… | |
| Recibida | Sin puntuar | 0.19% | — | Linux KernelAI | 25/9/2026 | 25/9/2026 | In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: skip the VMID 0 flush for VRAM Clear-on-release only runs on VRAM, which amdgpu_ttm_map_buffer() reaches via its direct MC address without programming a GART window, yet the wipe still forces a VMID 0 flush. On GFX11 (e.g. Navi33) that… | |
| Recibida | Sin puntuar | 0.21% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: ufs: create the root dentry after loading cylinder metadata ufs_fill_super() installed sb->s_root before it loaded the cylinder group structures for a writable mount: When ufs_read_cylinder_structures() failed, the error path freed the in-core… | |
| Recibida | Alta (7) | 0.15% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: ufs: validate cylinder group metadata before caching it ufs_read_cylinder() copies the cylinder group index and the rotor positions straight from the on-disk group and caches them without any check: They are then used as indices during allocation and… | |
| Recibida | Sin puntuar | 0.21% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: tick/broadcast: Plug clockevents replacement race 朱恺乾 reported and decoded the following race condition when a broadcast device is replaced: If the original broadcast device has a restricted interrupt affinity mask and the last CPU in that mask goes… | |
| Recibida | Sin puntuar | 0.20% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: tracing/user_events: Don't destroy fields when event removal fails destroy_user_event() destroys the event's fields before attempting to remove the trace event call. If user_event_set_call_visible() fails, e.g. because the event is still enabled and… | |
| Recibida | Sin puntuar | 0.21% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: tracing: Free histogram the var ref when its initialization fails create_var_ref() allocates a VAR_REF hist_field and then calls init_var_ref() to fill it in. When that fails the field is leaked. commit 656fe2ba85e8 ("tracing: Use hist trigger's… | |
| Recibida | Sin puntuar | 0.21% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: tracing: Free histogram var refs regardless of how often they are referenced Using the same variable three or more times in one hist trigger leaks the variable reference and its strings when the trigger is removed. commit 656fe2ba85e8 ("tracing: Use… | |
| Recibida | Sin puntuar | 0.21% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: tracing: Free histogram the field rejected for a bad modifier Writing a hist trigger whose value or variable carries a modifier that is not allowed there leaks the fields that were built for it. __create_val_field() takes the field from parse_expr()… | |
| Recibida | Sin puntuar | 0.21% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: tracing: Keep the entry count when the histogram stats allocation fails print_entries() uses n_entries both as the number of sort entries and as its own return value, so the -ENOMEM it stores when the stats allocation fails overwrites the count that… | |
| Recibida | Sin puntuar | 0.20% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: tracing: Take the reference before publishing the named histogram trigger event_hist_trigger_named_init() puts the trigger on the global named_triggers list and only then takes the reference on the trigger it shares its histogram with:… | |
| Recibida | Sin puntuar | 0.20% | — | Linux KernelAI | 25/9/2026 | 3/10/2026 | In the Linux kernel, the following vulnerability has been resolved: tracing: Undo the registration when enabling the histogram trigger fails Commit 6f86bdeab633 ("tracing: Fix bad hist from corrupting named_triggers list") described how a trigger that is registered but not on file->triggers ends up freed while still… | |
| Recibida | Sin puntuar | 0.20% | — | Linux KernelAI | 25/9/2026 | 25/9/2026 | In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr Add a size parameter to ivpu_to_cpu_addr() and validate that the whole [vpu_addr, vpu_addr + size) range stays within the BO. |