Vulnerabilidades

Con el objetivo de informar, advertir y ayudar a los profesionales sobre las ultimas vulnerabilidades de seguridad en sistemas tecnológicos, ponemos a disposición de los usuarios interesados en esta información una base de datos con información en castellano sobre cada una de las ultimas vulnerabilidades documentadas y conocidas.

Este repositorio con más de 75.000 registros esta basado en la información de NVD (https://nvd.nist.gov/) (National Vulnerability Database) – en función de un acuerdo de colaboración – por el cual desde INCIBE realizamos la traducción al castellano de la información incluida. En ocasiones este listado mostrará vulnerabilidades que aún no han sido traducidas debido a que se recogen en el transcurso del tiempo en el que el equipo de INCIBE realiza el proceso de traducción.

Se emplea el estándar de nomenclatura de vulnerabilidades CVE (https://cve.mitre.org/) (Common Vulnerabilities and Exposures), con el fin de facilitar el intercambio de información entre diferentes bases de datos y herramientas. Cada una de las vulnerabilidades recogidas enlaza a diversas fuentes de información así como a parches disponibles o soluciones aportadas por los fabricantes y desarrolladores. Es posible realizar búsquedas avanzadas teniendo la opción de seleccionar diferentes criterios como el tipo de vulnerabilidad, fabricante, tipo de impacto entre otros, con el fin de acortar los resultados.

Mediante suscripción RSS (https://www.incibe.es/feed/vulnerabilities) o Boletines (https://www.incibe.es/incibe/suscripciones) podemos estar informados diariamente de las ultimas vulnerabilidades incorporadas al repositorio.

CVE-2021-47449

Fecha de publicación:
22/05/2024
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ice: fix locking for Tx timestamp tracking flush<br /> <br /> Commit 4dd0d5c33c3e ("ice: add lock around Tx timestamp tracker flush")<br /> added a lock around the Tx timestamp tracker flow which is used to<br /> cleanup any left over SKBs and prepare for device removal.<br /> <br /> This lock is problematic because it is being held around a call to<br /> ice_clear_phy_tstamp. The clear function takes a mutex to send a PHY<br /> write command to firmware. This could lead to a deadlock if the mutex<br /> actually sleeps, and causes the following warning on a kernel with<br /> preemption debugging enabled:<br /> <br /> [ 715.419426] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:573<br /> [ 715.427900] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 3100, name: rmmod<br /> [ 715.435652] INFO: lockdep is turned off.<br /> [ 715.439591] Preemption disabled at:<br /> [ 715.439594] [] 0x0<br /> [ 715.446678] CPU: 52 PID: 3100 Comm: rmmod Tainted: G W OE 5.15.0-rc4+ #42 bdd7ec3018e725f159ca0d372ce8c2c0e784891c<br /> [ 715.458058] Hardware name: Intel Corporation S2600STQ/S2600STQ, BIOS SE5C620.86B.02.01.0010.010620200716 01/06/2020<br /> [ 715.468483] Call Trace:<br /> [ 715.470940] dump_stack_lvl+0x6a/0x9a<br /> [ 715.474613] ___might_sleep.cold+0x224/0x26a<br /> [ 715.478895] __mutex_lock+0xb3/0x1440<br /> [ 715.482569] ? stack_depot_save+0x378/0x500<br /> [ 715.486763] ? ice_sq_send_cmd+0x78/0x14c0 [ice 9a7e1ec00971c89ecd3fe0d4dc7da2b3786a421d]<br /> [ 715.494979] ? kfree+0xc1/0x520<br /> [ 715.498128] ? mutex_lock_io_nested+0x12a0/0x12a0<br /> [ 715.502837] ? kasan_set_free_info+0x20/0x30<br /> [ 715.507110] ? __kasan_slab_free+0x10b/0x140<br /> [ 715.511385] ? slab_free_freelist_hook+0xc7/0x220<br /> [ 715.516092] ? kfree+0xc1/0x520<br /> [ 715.519235] ? ice_deinit_lag+0x16c/0x220 [ice 9a7e1ec00971c89ecd3fe0d4dc7da2b3786a421d]<br /> [ 715.527359] ? ice_remove+0x1cf/0x6a0 [ice 9a7e1ec00971c89ecd3fe0d4dc7da2b3786a421d]<br /> [ 715.535133] ? pci_device_remove+0xab/0x1d0<br /> [ 715.539318] ? __device_release_driver+0x35b/0x690<br /> [ 715.544110] ? driver_detach+0x214/0x2f0<br /> [ 715.548035] ? bus_remove_driver+0x11d/0x2f0<br /> [ 715.552309] ? pci_unregister_driver+0x26/0x250<br /> [ 715.556840] ? ice_module_exit+0xc/0x2f [ice 9a7e1ec00971c89ecd3fe0d4dc7da2b3786a421d]<br /> [ 715.564799] ? __do_sys_delete_module.constprop.0+0x2d8/0x4e0<br /> [ 715.570554] ? do_syscall_64+0x3b/0x90<br /> [ 715.574303] ? entry_SYSCALL_64_after_hwframe+0x44/0xae<br /> [ 715.579529] ? start_flush_work+0x542/0x8f0<br /> [ 715.583719] ? ice_sq_send_cmd+0x78/0x14c0 [ice 9a7e1ec00971c89ecd3fe0d4dc7da2b3786a421d]<br /> [ 715.591923] ice_sq_send_cmd+0x78/0x14c0 [ice 9a7e1ec00971c89ecd3fe0d4dc7da2b3786a421d]<br /> [ 715.599960] ? wait_for_completion_io+0x250/0x250<br /> [ 715.604662] ? lock_acquire+0x196/0x200<br /> [ 715.608504] ? do_raw_spin_trylock+0xa5/0x160<br /> [ 715.612864] ice_sbq_rw_reg+0x1e6/0x2f0 [ice 9a7e1ec00971c89ecd3fe0d4dc7da2b3786a421d]<br /> [ 715.620813] ? ice_reset+0x130/0x130 [ice 9a7e1ec00971c89ecd3fe0d4dc7da2b3786a421d]<br /> [ 715.628497] ? __debug_check_no_obj_freed+0x1e8/0x3c0<br /> [ 715.633550] ? trace_hardirqs_on+0x1c/0x130<br /> [ 715.637748] ice_write_phy_reg_e810+0x70/0xf0 [ice 9a7e1ec00971c89ecd3fe0d4dc7da2b3786a421d]<br /> [ 715.646220] ? do_raw_spin_trylock+0xa5/0x160<br /> [ 715.650581] ? ice_ptp_release+0x910/0x910 [ice 9a7e1ec00971c89ecd3fe0d4dc7da2b3786a421d]<br /> [ 715.658797] ? ice_ptp_release+0x255/0x910 [ice 9a7e1ec00971c89ecd3fe0d4dc7da2b3786a421d]<br /> [ 715.667013] ice_clear_phy_tstamp+0x2c/0x110 [ice 9a7e1ec00971c89ecd3fe0d4dc7da2b3786a421d]<br /> [ 715.675403] ice_ptp_release+0x408/0x910 [ice 9a7e1ec00971c89ecd3fe0d4dc7da2b3786a421d]<br /> [ 715.683440] ice_remove+0x560/0x6a0 [ice 9a7e1ec00971c89ecd3fe0d4dc7da2b3786a421d]<br /> [ 715.691037] ? _raw_spin_unlock_irqrestore+0x46/0x73<br /> [ 715.696005] pci_device_remove+0xab/0x1d0<br /> [ 715.700018] __device_release_driver+0x35b/0x690<br /> [ 715.704637] driver_detach+0x214/0x2f0<br /> [ 715.708389] bus_remove_driver+0x11d/0x2f0<br /> [ 715.712489] pci_unregister_driver+0x26/0x250<br /> [ 71<br /> ---truncated---
Severidad: Pendiente de análisis
Última modificación:
22/05/2024

CVE-2021-47451

Fecha de publicación:
22/05/2024
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> netfilter: xt_IDLETIMER: fix panic that occurs when timer_type has garbage value<br /> <br /> Currently, when the rule related to IDLETIMER is added, idletimer_tg timer<br /> structure is initialized by kmalloc on executing idletimer_tg_create<br /> function. However, in this process timer-&gt;timer_type is not defined to<br /> a specific value. Thus, timer-&gt;timer_type has garbage value and it occurs<br /> kernel panic. So, this commit fixes the panic by initializing<br /> timer-&gt;timer_type using kzalloc instead of kmalloc.<br /> <br /> Test commands:<br /> # iptables -A OUTPUT -j IDLETIMER --timeout 1 --label test<br /> $ cat /sys/class/xt_idletimer/timers/test<br /> Killed<br /> <br /> Splat looks like:<br /> BUG: KASAN: user-memory-access in alarm_expires_remaining+0x49/0x70<br /> Read of size 8 at addr 0000002e8c7bc4c8 by task cat/917<br /> CPU: 12 PID: 917 Comm: cat Not tainted 5.14.0+ #3 79940a339f71eb14fc81aee1757a20d5bf13eb0e<br /> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014<br /> Call Trace:<br /> dump_stack_lvl+0x6e/0x9c<br /> kasan_report.cold+0x112/0x117<br /> ? alarm_expires_remaining+0x49/0x70<br /> __asan_load8+0x86/0xb0<br /> alarm_expires_remaining+0x49/0x70<br /> idletimer_tg_show+0xe5/0x19b [xt_IDLETIMER 11219304af9316a21bee5ba9d58f76a6b9bccc6d]<br /> dev_attr_show+0x3c/0x60<br /> sysfs_kf_seq_show+0x11d/0x1f0<br /> ? device_remove_bin_file+0x20/0x20<br /> kernfs_seq_show+0xa4/0xb0<br /> seq_read_iter+0x29c/0x750<br /> kernfs_fop_read_iter+0x25a/0x2c0<br /> ? __fsnotify_parent+0x3d1/0x570<br /> ? iov_iter_init+0x70/0x90<br /> new_sync_read+0x2a7/0x3d0<br /> ? __x64_sys_llseek+0x230/0x230<br /> ? rw_verify_area+0x81/0x150<br /> vfs_read+0x17b/0x240<br /> ksys_read+0xd9/0x180<br /> ? vfs_write+0x460/0x460<br /> ? do_syscall_64+0x16/0xc0<br /> ? lockdep_hardirqs_on+0x79/0x120<br /> __x64_sys_read+0x43/0x50<br /> do_syscall_64+0x3b/0xc0<br /> entry_SYSCALL_64_after_hwframe+0x44/0xae<br /> RIP: 0033:0x7f0cdc819142<br /> Code: c0 e9 c2 fe ff ff 50 48 8d 3d 3a ca 0a 00 e8 f5 19 02 00 0f 1f 44 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 0f 05 3d 00 f0 ff ff 77 56 c3 0f 1f 44 00 00 48 83 ec 28 48 89 54 24<br /> RSP: 002b:00007fff28eee5b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000<br /> RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 00007f0cdc819142<br /> RDX: 0000000000020000 RSI: 00007f0cdc032000 RDI: 0000000000000003<br /> RBP: 00007f0cdc032000 R08: 00007f0cdc031010 R09: 0000000000000000<br /> R10: 0000000000000022 R11: 0000000000000246 R12: 00005607e9ee31f0<br /> R13: 0000000000000003 R14: 0000000000020000 R15: 0000000000020000
Severidad: Pendiente de análisis
Última modificación:
22/05/2024

CVE-2021-47452

Fecha de publicación:
22/05/2024
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> netfilter: nf_tables: skip netdev events generated on netns removal<br /> <br /> syzbot reported following (harmless) WARN:<br /> <br /> WARNING: CPU: 1 PID: 2648 at net/netfilter/core.c:468<br /> nft_netdev_unregister_hooks net/netfilter/nf_tables_api.c:230 [inline]<br /> nf_tables_unregister_hook include/net/netfilter/nf_tables.h:1090 [inline]<br /> __nft_release_basechain+0x138/0x640 net/netfilter/nf_tables_api.c:9524<br /> nft_netdev_event net/netfilter/nft_chain_filter.c:351 [inline]<br /> nf_tables_netdev_event+0x521/0x8a0 net/netfilter/nft_chain_filter.c:382<br /> <br /> reproducer:<br /> unshare -n bash -c &amp;#39;ip link add br0 type bridge; nft add table netdev t ; \<br /> nft add chain netdev t ingress \{ type filter hook ingress device "br0" \<br /> priority 0\; policy drop\; \}&amp;#39;<br /> <br /> Problem is that when netns device exit hooks create the UNREGISTER<br /> event, the .pre_exit hook for nf_tables core has already removed the<br /> base hook. Notifier attempts to do this again.<br /> <br /> The need to do base hook unregister unconditionally was needed in the past,<br /> because notifier was last stage where reg-&gt;dev dereference was safe.<br /> <br /> Now that nf_tables does the hook removal in .pre_exit, this isn&amp;#39;t<br /> needed anymore.
Severidad: Pendiente de análisis
Última modificación:
22/05/2024

CVE-2021-47454

Fecha de publicación:
22/05/2024
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> powerpc/smp: do not decrement idle task preempt count in CPU offline<br /> <br /> With PREEMPT_COUNT=y, when a CPU is offlined and then onlined again, we<br /> get:<br /> <br /> BUG: scheduling while atomic: swapper/1/0/0x00000000<br /> no locks held by swapper/1/0.<br /> CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.0-rc2+ #100<br /> Call Trace:<br /> dump_stack_lvl+0xac/0x108<br /> __schedule_bug+0xac/0xe0<br /> __schedule+0xcf8/0x10d0<br /> schedule_idle+0x3c/0x70<br /> do_idle+0x2d8/0x4a0<br /> cpu_startup_entry+0x38/0x40<br /> start_secondary+0x2ec/0x3a0<br /> start_secondary_prolog+0x10/0x14<br /> <br /> This is because powerpc&amp;#39;s arch_cpu_idle_dead() decrements the idle task&amp;#39;s<br /> preempt count, for reasons explained in commit a7c2bb8279d2 ("powerpc:<br /> Re-enable preemption before cpu_die()"), specifically "start_secondary()<br /> expects a preempt_count() of 0."<br /> <br /> However, since commit 2c669ef6979c ("powerpc/preempt: Don&amp;#39;t touch the idle<br /> task&amp;#39;s preempt_count during hotplug") and commit f1a0a376ca0c ("sched/core:<br /> Initialize the idle task with preemption disabled"), that justification no<br /> longer holds.<br /> <br /> The idle task isn&amp;#39;t supposed to re-enable preemption, so remove the<br /> vestigial preempt_enable() from the CPU offline path.<br /> <br /> Tested with pseries and powernv in qemu, and pseries on PowerVM.
Severidad: Pendiente de análisis
Última modificación:
22/05/2024

CVE-2021-47457

Fecha de publicación:
22/05/2024
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible()<br /> <br /> Using wait_event_interruptible() to wait for complete transmission,<br /> but do not check the result of wait_event_interruptible() which can be<br /> interrupted. It will result in TX buffer has multiple accessors and<br /> the later process interferes with the previous process.<br /> <br /> Following is one of the problems reported by syzbot.<br /> <br /> =============================================================<br /> WARNING: CPU: 0 PID: 0 at net/can/isotp.c:840 isotp_tx_timer_handler+0x2e0/0x4c0<br /> CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.13.0-rc7+ #68<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1 04/01/2014<br /> RIP: 0010:isotp_tx_timer_handler+0x2e0/0x4c0<br /> Call Trace:<br /> <br /> ? isotp_setsockopt+0x390/0x390<br /> __hrtimer_run_queues+0xb8/0x610<br /> hrtimer_run_softirq+0x91/0xd0<br /> ? rcu_read_lock_sched_held+0x4d/0x80<br /> __do_softirq+0xe8/0x553<br /> irq_exit_rcu+0xf8/0x100<br /> sysvec_apic_timer_interrupt+0x9e/0xc0<br /> <br /> asm_sysvec_apic_timer_interrupt+0x12/0x20<br /> <br /> Add result check for wait_event_interruptible() in isotp_sendmsg()<br /> to avoid multiple accessers for tx buffer.
Severidad: Pendiente de análisis
Última modificación:
22/05/2024

CVE-2021-47460

Fecha de publicación:
22/05/2024
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ocfs2: fix data corruption after conversion from inline format<br /> <br /> Commit 6dbf7bb55598 ("fs: Don&amp;#39;t invalidate page buffers in<br /> block_write_full_page()") uncovered a latent bug in ocfs2 conversion<br /> from inline inode format to a normal inode format.<br /> <br /> The code in ocfs2_convert_inline_data_to_extents() attempts to zero out<br /> the whole cluster allocated for file data by grabbing, zeroing, and<br /> dirtying all pages covering this cluster. However these pages are<br /> beyond i_size, thus writeback code generally ignores these dirty pages<br /> and no blocks were ever actually zeroed on the disk.<br /> <br /> This oversight was fixed by commit 693c241a5f6a ("ocfs2: No need to zero<br /> pages past i_size.") for standard ocfs2 write path, inline conversion<br /> path was apparently forgotten; the commit log also has a reasoning why<br /> the zeroing actually is not needed.<br /> <br /> After commit 6dbf7bb55598, things became worse as writeback code stopped<br /> invalidating buffers on pages beyond i_size and thus these pages end up<br /> with clean PageDirty bit but with buffers attached to these pages being<br /> still dirty. So when a file is converted from inline format, then<br /> writeback triggers, and then the file is grown so that these pages<br /> become valid, the invalid dirtiness state is preserved,<br /> mark_buffer_dirty() does nothing on these pages (buffers are already<br /> dirty) but page is never written back because it is clean. So data<br /> written to these pages is lost once pages are reclaimed.<br /> <br /> Simple reproducer for the problem is:<br /> <br /> xfs_io -f -c "pwrite 0 2000" -c "pwrite 2000 2000" -c "fsync" \<br /> -c "pwrite 4000 2000" ocfs2_file<br /> <br /> After unmounting and mounting the fs again, you can observe that end of<br /> &amp;#39;ocfs2_file&amp;#39; has lost its contents.<br /> <br /> Fix the problem by not doing the pointless zeroing during conversion<br /> from inline format similarly as in the standard write path.<br /> <br /> [akpm@linux-foundation.org: fix whitespace, per Joseph]
Severidad: Pendiente de análisis
Última modificación:
22/05/2024