Mexico extradita a Rafael Caro Quintero y otros 28 líderes del crimen organizado a Estados Unidos

Sin anuncio previo, el gobierno de México ha extraditado a Estados Unidos a 29 figuras clave del crimen organizado, incluyendo a Rafael Caro Quintero. La medida ocurre en un contexto de crecientes presiones por parte del presidente estadounidense Donald Trump, quien ha amenazado con imponer aranceles del 25% a las importaciones mexicanas si no se intensifican los esfuerzos para frenar el tráfico de fentanilo y la migración irregular.

La Fiscalía General de la República y la Secretaría de Seguridad y Protección Ciudadana de México confirmaron la extradición en un comunicado, aunque sin revelar los nombres de los detenidos. Sin embargo, fuentes de seguridad han informado que entre los extraditados se encuentran Rafael Caro Quintero, el exlíder del Cártel de Guadalajara condenado por el asesinato del agente de la DEA Enrique «Kiki» Camarena en 1985, y Antonio Oseguera Cervantes, hermano de Nemesio Oseguera Cervantes, alias «El Mencho», líder del Cártel Jalisco Nueva Generación (CJNG). De acuerdo con El País, a ellos se suman los exlíderes de los Zetas, Miguel Ángel “el Z-40”, y Omar Treviño Morales, “el Z-42”, conocidos por su brutalidad; también Antonio Oseguera Cervantes, “Tony Montana”, operador financiero del Cártel Jalisco Nueva Generación (CJNG), así como y José Ángel Canobbio, el Güerito, uno de los principales distribuidores del Cártel de Sinaloa.

El traslado de Caro Quintero a Nueva York marca el punto culminante de una larga persecución judicial en su contra. Capturado en 2022 tras casi una década de evasión, su extradición ha sido interpretada por exfuncionarios estadounidenses como un mensaje claro: «Nunca olvidamos si dañas o matas a uno de nuestros agentes».


Claudia Sheinbaum aranceles China Estados Unidos 2200985016
EE UU estaría presionando a México para imponer aranceles a China; Sheinbaum niega que esta solicitud sea un requisito

Sheinbaum asegura que México ha privilegiado la integración comercial con Estados Unidos. Advierte que si los aranceles entran en vigor, será necesario evaluar otros destinos de exportación.


El masivo operativo de extradición ocurre en un momento de tensas negociaciones comerciales entre México y Estados Unidos. Trump ha amenazado con imponer aranceles generalizados a los productos mexicanos a partir del 4 de marzo, lo que podría asestar un duro golpe a la economía del país. El 80% de las exportaciones mexicanas tienen como destino el mercado estadounidense. La extradición podría interpretarse como un gesto de «buena fe» por parte del gobierno mexicano en un intento de mitigar estas presiones.

Sin embargo, aún no está claro si las autoridades mexicanas siguieron los procedimientos formales de extradición o si se optó por una vía expedita, lo que podría generar controversias legales en el futuro.

Mientras tanto, ni la Casa Blanca ni el Departamento de Estado han emitido declaraciones oficiales sobre la operación. No obstante, esta acción representa un cambio significativo en la cooperación bilateral en materia de seguridad y podría redefinir la relación entre ambos países en los próximos meses.

Tensiones en plano de la seguridad entre México y Estados Unidos

Trump ha intensificado su retórica contra los cárteles mexicanos al catalogarlos oficialmente como organizaciones terroristas. Esta medida abre la puerta a una mayor intervención de las agencias estadounidenses en territorio mexicano y podría justificar acciones militares directas bajo la doctrina antiterrorista de EE UU.

En reacción a esta situación, Sheinbaum ha propuesto dos reformas constitucionales con el objetivo de impedir cualquier posible «violación a la soberanía» de México. Asimismo, anunció que la Secretaría de Relaciones Exteriores (SRE) reforzará sus acciones legales contra fabricantes y distribuidores de armas en Estados Unidos, acusándolos de facilitar actividades terroristas.

“Queremos dejar claro que no negociamos la soberanía. Esta designación no debe convertirse en una excusa para que Estados Unidos viole nuestra autonomía”, advirtió la mandataria hace una semana. Sheinbaum aseguró que ambos países trabajan de manera coordinada en temas de seguridad. No obstante, precisó que la designación de los cárteles mexicanos como organizaciones terroristas no fue consultada con su administración.

CVE-2025-22952

CVE-2025-22952

Título es
CVE-2025-22952

Jue, 27/02/2025 – 20:16

Gravedad 2.0 Txt
Pendiente de análisis

Título en

CVE-2025-22952

Descripción en
elestio memos v0.23.0 is vulnerable to Server-Side Request Forgery (SSRF) due to insufficient validation of user-supplied URLs, which can be exploited to perform SSRF attacks.

27/02/2025

27/02/2025

Gravedad 3.1 Txt Gravedad 3.1 (CVSS 3.1 Base Score)
Pendiente de análisis

Referencias


  • https://elest.io/open-source/memos

  • https://github.com/usememos/memos

  • https://github.com/usememos/memos/issues/4413

  • https://github.com/usememos/memos/pull/4428
  • Enviar en el boletín
    Off

    CVE-2025-21824

    CVE-2025-21824

    Título es
    CVE-2025-21824

    Jue, 27/02/2025 – 20:16

    Gravedad 2.0 Txt
    Pendiente de análisis

    Título en

    CVE-2025-21824

    Descripción en
    In the Linux kernel, the following vulnerability has been resolved:

    gpu: host1x: Fix a use of uninitialized mutex

    commit c8347f915e67 ("gpu: host1x: Fix boot regression for Tegra")
    caused a use of uninitialized mutex leading to below warning when
    CONFIG_DEBUG_MUTEXES and CONFIG_DEBUG_LOCK_ALLOC are enabled.

    [ 41.662843] ————[ cut here ]————
    [ 41.663012] DEBUG_LOCKS_WARN_ON(lock->magic != lock)
    [ 41.663035] WARNING: CPU: 4 PID: 794 at kernel/locking/mutex.c:587 __mutex_lock+0x670/0x878
    [ 41.663458] Modules linked in: rtw88_8822c(+) bluetooth(+) rtw88_pci rtw88_core mac80211 aquantia libarc4 crc_itu_t cfg80211 tegra194_cpufreq dwmac_tegra(+) arm_dsu_pmu stmmac_platform stmmac pcs_xpcs rfkill at24 host1x(+) tegra_bpmp_thermal ramoops reed_solomon fuse loop nfnetlink xfs mmc_block rpmb_core ucsi_ccg ina3221 crct10dif_ce xhci_tegra ghash_ce lm90 sha2_ce sha256_arm64 sha1_ce sdhci_tegra pwm_fan sdhci_pltfm sdhci gpio_keys rtc_tegra cqhci mmc_core phy_tegra_xusb i2c_tegra tegra186_gpc_dma i2c_tegra_bpmp spi_tegra114 dm_mirror dm_region_hash dm_log dm_mod
    [ 41.665078] CPU: 4 UID: 0 PID: 794 Comm: (udev-worker) Not tainted 6.11.0-29.31_1538613708.el10.aarch64+debug #1
    [ 41.665838] Hardware name: NVIDIA NVIDIA Jetson AGX Orin Developer Kit/Jetson, BIOS 36.3.0-gcid-35594366 02/26/2024
    [ 41.672555] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=–)
    [ 41.679636] pc : __mutex_lock+0x670/0x878
    [ 41.683834] lr : __mutex_lock+0x670/0x878
    [ 41.688035] sp : ffff800084b77090
    [ 41.691446] x29: ffff800084b77160 x28: ffffdd4bebf7b000 x27: ffffdd4be96b1000
    [ 41.698799] x26: 1fffe0002308361c x25: 1ffff0001096ee18 x24: 0000000000000000
    [ 41.706149] x23: 0000000000000000 x22: 0000000000000002 x21: ffffdd4be6e3c7a0
    [ 41.713500] x20: ffff800084b770f0 x19: ffff00011841b1e8 x18: 0000000000000000
    [ 41.720675] x17: 0000000000000000 x16: 0000000000000000 x15: 0720072007200720
    [ 41.728023] x14: 0000000000000000 x13: 0000000000000001 x12: ffff6001a96eaab3
    [ 41.735375] x11: 1fffe001a96eaab2 x10: ffff6001a96eaab2 x9 : ffffdd4be4838bbc
    [ 41.742723] x8 : 00009ffe5691554e x7 : ffff000d4b755593 x6 : 0000000000000001
    [ 41.749985] x5 : ffff000d4b755590 x4 : 1fffe0001d88f001 x3 : dfff800000000000
    [ 41.756988] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000ec478000
    [ 41.764251] Call trace:
    [ 41.766695] __mutex_lock+0x670/0x878
    [ 41.770373] mutex_lock_nested+0x2c/0x40
    [ 41.774134] host1x_intr_start+0x54/0xf8 [host1x]
    [ 41.778863] host1x_runtime_resume+0x150/0x228 [host1x]
    [ 41.783935] pm_generic_runtime_resume+0x84/0xc8
    [ 41.788485] __rpm_callback+0xa0/0x478
    [ 41.792422] rpm_callback+0x15c/0x1a8
    [ 41.795922] rpm_resume+0x698/0xc08
    [ 41.799597] __pm_runtime_resume+0xa8/0x140
    [ 41.803621] host1x_probe+0x810/0xbc0 [host1x]
    [ 41.807909] platform_probe+0xcc/0x1a8
    [ 41.811845] really_probe+0x188/0x800
    [ 41.815347] __driver_probe_device+0x164/0x360
    [ 41.819810] driver_probe_device+0x64/0x1a8
    [ 41.823834] __driver_attach+0x180/0x490
    [ 41.827773] bus_for_each_dev+0x104/0x1a0
    [ 41.831797] driver_attach+0x44/0x68
    [ 41.835296] bus_add_driver+0x23c/0x4e8
    [ 41.839235] driver_register+0x15c/0x3a8
    [ 41.843170] __platform_register_drivers+0xa4/0x208
    [ 41.848159] tegra_host1x_init+0x4c/0xff8 [host1x]
    [ 41.853147] do_one_initcall+0xd4/0x380
    [ 41.856997] do_init_module+0x1dc/0x698
    [ 41.860758] load_module+0xc70/0x1300
    [ 41.864435] __do_sys_init_module+0x1a8/0x1d0
    [ 41.868721] __arm64_sys_init_module+0x74/0xb0
    [ 41.873183] invoke_syscall.constprop.0+0xdc/0x1e8
    [ 41.877997] do_el0_svc+0x154/0x1d0
    [ 41.881671] el0_svc+0x54/0x140
    [ 41.884820] el0t_64_sync_handler+0x120/0x130
    [ 41.889285] el0t_64_sync+0x1a4/0x1a8
    [ 41.892960] irq event stamp: 69737
    [ 41.896370] hardirqs last enabled at (69737): [] _raw_spin_unlock_irqrestore+0x44/0xe8
    [ 41.905739] hardirqs last disabled at (69736):
    —truncated—

    27/02/2025

    27/02/2025

    Gravedad 3.1 Txt Gravedad 3.1 (CVSS 3.1 Base Score)
    Pendiente de análisis

    Referencias


  • https://git.kernel.org/stable/c/02458fbfaa0170aabf8506f7d4ed054f02414251

  • https://git.kernel.org/stable/c/127e91638ddcd02b80de92fec2240609a9f90426

  • https://git.kernel.org/stable/c/396d8e5136b4476672bc15b83ba312486bb4bf76
  • Enviar en el boletín
    Off

    CVE-2025-21823

    CVE-2025-21823

    Título es
    CVE-2025-21823

    Jue, 27/02/2025 – 20:16

    Gravedad 2.0 Txt
    Pendiente de análisis

    Título en

    CVE-2025-21823

    Descripción en
    In the Linux kernel, the following vulnerability has been resolved:

    batman-adv: Drop unmanaged ELP metric worker

    The ELP worker needs to calculate new metric values for all neighbors
    "reachable" over an interface. Some of the used metric sources require
    locks which might need to sleep. This sleep is incompatible with the RCU
    list iterator used for the recorded neighbors. The initial approach to work
    around of this problem was to queue another work item per neighbor and then
    run this in a new context.

    Even when this solved the RCU vs might_sleep() conflict, it has a major
    problems: Nothing was stopping the work item in case it is not needed
    anymore – for example because one of the related interfaces was removed or
    the batman-adv module was unloaded – resulting in potential invalid memory
    accesses.

    Directly canceling the metric worker also has various problems:

    * cancel_work_sync for a to-be-deactivated interface is called with
    rtnl_lock held. But the code in the ELP metric worker also tries to use
    rtnl_lock() – which will never return in this case. This also means that
    cancel_work_sync would never return because it is waiting for the worker
    to finish.
    * iterating over the neighbor list for the to-be-deactivated interface is
    currently done using the RCU specific methods. Which means that it is
    possible to miss items when iterating over it without the associated
    spinlock – a behaviour which is acceptable for a periodic metric check
    but not for a cleanup routine (which must "stop" all still running
    workers)

    The better approch is to get rid of the per interface neighbor metric
    worker and handle everything in the interface worker. The original problems
    are solved by:

    * creating a list of neighbors which require new metric information inside
    the RCU protected context, gathering the metric according to the new list
    outside the RCU protected context
    * only use rcu_trylock inside metric gathering code to avoid a deadlock
    when the cancel_delayed_work_sync is called in the interface removal code
    (which is called with the rtnl_lock held)

    27/02/2025

    27/02/2025

    Gravedad 3.1 Txt Gravedad 3.1 (CVSS 3.1 Base Score)
    Pendiente de análisis

    Referencias


  • https://git.kernel.org/stable/c/0fdc3c166ac17b26014313fa2b93696354511b24

  • https://git.kernel.org/stable/c/781a06fd265a8151f7601122d9c2e985663828ff

  • https://git.kernel.org/stable/c/8c8ecc98f5c65947b0070a24bac11e12e47cc65d

  • https://git.kernel.org/stable/c/a7aa2317285806640c844acd4cd2cd768e395264

  • https://git.kernel.org/stable/c/af264c2a9adc37f4bdf88ca7f3affa15d8c7de9e
  • Enviar en el boletín
    Off

    CVE-2025-21822

    CVE-2025-21822

    Título es
    CVE-2025-21822

    Jue, 27/02/2025 – 20:16

    Gravedad 2.0 Txt
    Pendiente de análisis

    Título en

    CVE-2025-21822

    Descripción en
    In the Linux kernel, the following vulnerability has been resolved:

    ptp: vmclock: Set driver data before its usage

    If vmclock_ptp_register() fails during probing, vmclock_remove() is
    called to clean up the ptp clock and misc device.
    It uses dev_get_drvdata() to access the vmclock state.
    However the driver data is not yet set at this point.

    Assign the driver data earlier.

    27/02/2025

    27/02/2025

    Gravedad 3.1 Txt Gravedad 3.1 (CVSS 3.1 Base Score)
    Pendiente de análisis

    Referencias


  • https://git.kernel.org/stable/c/6dbd8b91a065d1d8001446a28e72cd140f9acef0

  • https://git.kernel.org/stable/c/f7d07cd4f77d77f366c8ffbb8ba8b61f614e5fce
  • Enviar en el boletín
    Off

    CVE-2025-21821

    CVE-2025-21821

    Título es
    CVE-2025-21821

    Jue, 27/02/2025 – 20:16

    Gravedad 2.0 Txt
    Pendiente de análisis

    Título en

    CVE-2025-21821

    Descripción en
    In the Linux kernel, the following vulnerability has been resolved:

    fbdev: omap: use threaded IRQ for LCD DMA

    When using touchscreen and framebuffer, Nokia 770 crashes easily with:

    BUG: scheduling while atomic: irq/144-ads7846/82/0x00010000
    Modules linked in: usb_f_ecm g_ether usb_f_rndis u_ether libcomposite configfs omap_udc ohci_omap ohci_hcd
    CPU: 0 UID: 0 PID: 82 Comm: irq/144-ads7846 Not tainted 6.12.7-770 #2
    Hardware name: Nokia 770
    Call trace:
    unwind_backtrace from show_stack+0x10/0x14
    show_stack from dump_stack_lvl+0x54/0x5c
    dump_stack_lvl from __schedule_bug+0x50/0x70
    __schedule_bug from __schedule+0x4d4/0x5bc
    __schedule from schedule+0x34/0xa0
    schedule from schedule_preempt_disabled+0xc/0x10
    schedule_preempt_disabled from __mutex_lock.constprop.0+0x218/0x3b4
    __mutex_lock.constprop.0 from clk_prepare_lock+0x38/0xe4
    clk_prepare_lock from clk_set_rate+0x18/0x154
    clk_set_rate from sossi_read_data+0x4c/0x168
    sossi_read_data from hwa742_read_reg+0x5c/0x8c
    hwa742_read_reg from send_frame_handler+0xfc/0x300
    send_frame_handler from process_pending_requests+0x74/0xd0
    process_pending_requests from lcd_dma_irq_handler+0x50/0x74
    lcd_dma_irq_handler from __handle_irq_event_percpu+0x44/0x130
    __handle_irq_event_percpu from handle_irq_event+0x28/0x68
    handle_irq_event from handle_level_irq+0x9c/0x170
    handle_level_irq from generic_handle_domain_irq+0x2c/0x3c
    generic_handle_domain_irq from omap1_handle_irq+0x40/0x8c
    omap1_handle_irq from generic_handle_arch_irq+0x28/0x3c
    generic_handle_arch_irq from call_with_stack+0x1c/0x24
    call_with_stack from __irq_svc+0x94/0xa8
    Exception stack(0xc5255da0 to 0xc5255de8)
    5da0: 00000001 c22fc620 00000000 00000000 c08384a8 c106fc00 00000000 c240c248
    5dc0: c113a600 c3f6ec30 00000001 00000000 c22fc620 c5255df0 c22fc620 c0279a94
    5de0: 60000013 ffffffff
    __irq_svc from clk_prepare_lock+0x4c/0xe4
    clk_prepare_lock from clk_get_rate+0x10/0x74
    clk_get_rate from uwire_setup_transfer+0x40/0x180
    uwire_setup_transfer from spi_bitbang_transfer_one+0x2c/0x9c
    spi_bitbang_transfer_one from spi_transfer_one_message+0x2d0/0x664
    spi_transfer_one_message from __spi_pump_transfer_message+0x29c/0x498
    __spi_pump_transfer_message from __spi_sync+0x1f8/0x2e8
    __spi_sync from spi_sync+0x24/0x40
    spi_sync from ads7846_halfd_read_state+0x5c/0x1c0
    ads7846_halfd_read_state from ads7846_irq+0x58/0x348
    ads7846_irq from irq_thread_fn+0x1c/0x78
    irq_thread_fn from irq_thread+0x120/0x228
    irq_thread from kthread+0xc8/0xe8
    kthread from ret_from_fork+0x14/0x28

    As a quick fix, switch to a threaded IRQ which provides a stable system.

    27/02/2025

    27/02/2025

    Gravedad 3.1 Txt Gravedad 3.1 (CVSS 3.1 Base Score)
    Pendiente de análisis

    Referencias


  • https://git.kernel.org/stable/c/7bbbd311dd503653a2cc86d9226740883051dc92

  • https://git.kernel.org/stable/c/8392ea100f0b86c234c739c6662f39f0ccc0cefd

  • https://git.kernel.org/stable/c/aa8e22cbedeb626f2a6bda0aea362353d627cd0a

  • https://git.kernel.org/stable/c/e4b6b665df815b4841e71b72f06446884e8aad40

  • https://git.kernel.org/stable/c/fb6a5edb60921887d7d10619fcdcbee9759552cb
  • Enviar en el boletín
    Off

    CVE-2025-21819

    CVE-2025-21819

    Título es
    CVE-2025-21819

    Jue, 27/02/2025 – 20:16

    Gravedad 2.0 Txt
    Pendiente de análisis

    Título en

    CVE-2025-21819

    Descripción en
    In the Linux kernel, the following vulnerability has been resolved:

    Revert "drm/amd/display: Use HW lock mgr for PSR1"

    This reverts commit
    a2b5a9956269 ("drm/amd/display: Use HW lock mgr for PSR1")

    Because it may cause system hang while connect with two edp panel.

    27/02/2025

    27/02/2025

    Gravedad 3.1 Txt Gravedad 3.1 (CVSS 3.1 Base Score)
    Pendiente de análisis

    Referencias


  • https://git.kernel.org/stable/c/915697c2e69ac8d14dad498e6d6f43dbb7de3787

  • https://git.kernel.org/stable/c/95c75578c420110c43791295985abb961d6dc033

  • https://git.kernel.org/stable/c/a978864653e45d2671f99b09afcc1110e45d3dd9

  • https://git.kernel.org/stable/c/dcc3f2c06d80da39eee742b51ddf0781affb260c

  • https://git.kernel.org/stable/c/f245b400a223a71d6d5f4c72a2cb9b573a7fc2b6
  • Enviar en el boletín
    Off

    CVE-2025-21820

    CVE-2025-21820

    Título es
    CVE-2025-21820

    Jue, 27/02/2025 – 20:16

    Gravedad 2.0 Txt
    Pendiente de análisis

    Título en

    CVE-2025-21820

    Descripción en
    In the Linux kernel, the following vulnerability has been resolved:

    tty: xilinx_uartps: split sysrq handling

    lockdep detects the following circular locking dependency:

    CPU 0 CPU 1
    ========================== ============================
    cdns_uart_isr() printk()
    uart_port_lock(port) console_lock()
    cdns_uart_console_write()
    if (!port->sysrq)
    uart_port_lock(port)
    uart_handle_break()
    port->sysrq = …
    uart_handle_sysrq_char()
    printk()
    console_lock()

    The fixed commit attempts to avoid this situation by only taking the
    port lock in cdns_uart_console_write if port->sysrq unset. However, if
    (as shown above) cdns_uart_console_write runs before port->sysrq is set,
    then it will try to take the port lock anyway. This may result in a
    deadlock.

    Fix this by splitting sysrq handling into two parts. We use the prepare
    helper under the port lock and defer handling until we release the lock.

    27/02/2025

    27/02/2025

    Gravedad 3.1 Txt Gravedad 3.1 (CVSS 3.1 Base Score)
    Pendiente de análisis

    Referencias


  • https://git.kernel.org/stable/c/4410dba9807a17a93f649a9f5870ceaf30a675a3

  • https://git.kernel.org/stable/c/8ea0e7b3d7b8f2f0fc9db491ff22a0abe120801c

  • https://git.kernel.org/stable/c/9b88a7c4584ba67267a051069b8abe44fc9595b2

  • https://git.kernel.org/stable/c/b06f388994500297bb91be60ffaf6825ecfd2afe

  • https://git.kernel.org/stable/c/de5bd24197bd9ee37ec1e379a3d882bbd15c5065
  • Enviar en el boletín
    Off

    CVE-2025-21817

    CVE-2025-21817

    Título es
    CVE-2025-21817

    Jue, 27/02/2025 – 20:16

    Gravedad 2.0 Txt
    Pendiente de análisis

    Título en

    CVE-2025-21817

    Descripción en
    In the Linux kernel, the following vulnerability has been resolved:

    block: mark GFP_NOIO around sysfs ->store()

    sysfs ->store is called with queue freezed, meantime we have several
    ->store() callbacks(update_nr_requests, wbt, scheduler) to allocate
    memory with GFP_KERNEL which may run into direct reclaim code path,
    then potential deadlock can be caused.

    Fix the issue by marking NOIO around sysfs ->store()

    27/02/2025

    27/02/2025

    Gravedad 3.1 Txt Gravedad 3.1 (CVSS 3.1 Base Score)
    Pendiente de análisis

    Referencias


  • https://git.kernel.org/stable/c/2566ce907e5d5db8a039647208e029ce559baa31

  • https://git.kernel.org/stable/c/7c0be4ead1f8f5f8be0803f347de0de81e3b8e1c
  • Enviar en el boletín
    Off

    CVE-2025-21818

    CVE-2025-21818

    Título es
    CVE-2025-21818

    Jue, 27/02/2025 – 20:16

    Gravedad 2.0 Txt
    Pendiente de análisis

    Título en

    CVE-2025-21818

    Descripción en
    In the Linux kernel, the following vulnerability has been resolved:

    x86/xen: fix xen_hypercall_hvm() to not clobber %rbx

    xen_hypercall_hvm(), which is used when running as a Xen PVH guest at
    most only once during early boot, is clobbering %rbx. Depending on
    whether the caller relies on %rbx to be preserved across the call or
    not, this clobbering might result in an early crash of the system.

    This can be avoided by using an already saved register instead of %rbx.

    27/02/2025

    27/02/2025

    Gravedad 3.1 Txt Gravedad 3.1 (CVSS 3.1 Base Score)
    Pendiente de análisis

    Referencias


  • https://git.kernel.org/stable/c/23f6f420cd727d641f95478fcf3bbbee41e4e5d6

  • https://git.kernel.org/stable/c/242f7584da3ad041a9db809d33d27a8be8eccc29

  • https://git.kernel.org/stable/c/4890a0858c09d96f3234a8f94663de80a7201bc4

  • https://git.kernel.org/stable/c/522d726824cc570e0b6bf0b3af4d5a826f1b17c5

  • https://git.kernel.org/stable/c/98a5cfd2320966f40fe049a9855f8787f0126825
  • Enviar en el boletín
    Off