p PatchFirst

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

Уязвимости linux-lowlatency-hwe-5.15 · Страница 88

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

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

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

  1. CVE-2022-49634

    Средний · CVSS 4.7EPSS 0,18%Есть исправление

    sysctl: Fix data-races in proc_dou8vec_minmax().

    In the Linux kernel, the following vulnerability has been resolved: sysctl: Fix data-races in proc_dou8vec_minmax(). A sysctl variable is accessed concurrently, and there is always a chance of data-race. So, all readers and writers need some basic protection to avoid load/store-tearing. This patch changes proc_dou8vec_minmax() to use READ_ONCE() and WRITE_ONCE() internally to fix data-races on the sysctl side. For now, proc_dou8vec_minmax() itself is tolerant to a data-race, but we still need to add annotations on the other subsystem's side.

    • Обновитесь до 5.15.0-50.56~20.04.1
  2. CVE-2022-49633

    Средний · CVSS 4.7EPSS 0,18%Есть исправление

    icmp: Fix data-races around sysctl_icmp_echo_enable_probe.

    In the Linux kernel, the following vulnerability has been resolved: icmp: Fix data-races around sysctl_icmp_echo_enable_probe. While reading sysctl_icmp_echo_enable_probe, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers.

    • Обновитесь до 5.15.0-50.56~20.04.1
  3. CVE-2022-49632

    Средний · CVSS 4.7EPSS 0,18%Есть исправление

    icmp: Fix a data-race around sysctl_icmp_errors_use_inbound_ifaddr.

    In the Linux kernel, the following vulnerability has been resolved: icmp: Fix a data-race around sysctl_icmp_errors_use_inbound_ifaddr. While reading sysctl_icmp_errors_use_inbound_ifaddr, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader.

    • Обновитесь до 5.15.0-50.56~20.04.1
  4. CVE-2022-49631

    Средний · CVSS 4.7EPSS 0,18%Есть исправление

    raw: Fix a data-race around sysctl_raw_l3mdev_accept.

    In the Linux kernel, the following vulnerability has been resolved: raw: Fix a data-race around sysctl_raw_l3mdev_accept. While reading sysctl_raw_l3mdev_accept, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader.

    • Обновитесь до 5.15.0-50.56~20.04.1
  5. CVE-2022-49630

    Средний · CVSS 4.7EPSS 0,18%Есть исправление

    tcp: Fix a data-race around sysctl_tcp_ecn_fallback.

    In the Linux kernel, the following vulnerability has been resolved: tcp: Fix a data-race around sysctl_tcp_ecn_fallback. While reading sysctl_tcp_ecn_fallback, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader.

    • Обновитесь до 5.15.0-50.56~20.04.1
  6. CVE-2022-49629

    Средний · CVSS 4.7EPSS 0,18%Есть исправление

    nexthop: Fix data-races around nexthop_compat_mode.

    In the Linux kernel, the following vulnerability has been resolved: nexthop: Fix data-races around nexthop_compat_mode. While reading nexthop_compat_mode, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers.

    • Обновитесь до 5.15.0-50.56~20.04.1
  7. CVE-2022-49628

    Средний · CVSS 5.5EPSS 0,26%Есть исправление

    net: stmmac: fix leaks in probe

    In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix leaks in probe These two error paths should clean up before returning.

    • Обновитесь до 5.15.0-50.56~20.04.1
  8. CVE-2022-49627

    Средний · CVSS 5.5EPSS 0,27%Есть исправление

    ima: Fix potential memory leak in ima_init_crypto()

    In the Linux kernel, the following vulnerability has been resolved: ima: Fix potential memory leak in ima_init_crypto() On failure to allocate the SHA1 tfm, IMA fails to initialize and exits without freeing the ima_algo_array. Add the missing kfree() for ima_algo_array to avoid the potential memory leak.

    • Обновитесь до 5.15.0-50.56~20.04.1
  9. CVE-2022-49626

    Высокий · CVSS 7.8EPSS 0,28%Есть исправление

    sfc: fix use after free when disabling sriov

    In the Linux kernel, the following vulnerability has been resolved: sfc: fix use after free when disabling sriov Use after free is detected by kfence when disabling sriov. What was read after being freed was vf->pci_dev: it was freed from pci_disable_sriov and later read in efx_ef10_sriov_free_vf_vports, called from efx_ef10_sriov_free_vf_vswitching. Set the pointer to NULL at release time to not trying to read it later. Reproducer and dmesg log (note that kfence doesn't detect it every time): $ echo 1 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs $ echo 0 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs BUG: KFENCE: use-after-free

    • Обновитесь до 5.15.0-50.56~20.04.1
  10. CVE-2022-49625

    Средний · CVSS 5.7EPSS 0,29%Есть исправление

    sfc: fix kernel panic when creating VF

    In the Linux kernel, the following vulnerability has been resolved: sfc: fix kernel panic when creating VF When creating VFs a kernel panic can happen when calling to efx_ef10_try_update_nic_stats_vf. When releasing a DMA coherent buffer, sometimes, I don't know in what specific circumstances, it has to unmap memory with vunmap. It is disallowed to do that in IRQ context or with BH disabled. Otherwise, we hit this line in vunmap, causing the crash: BUG_ON(in_interrupt()); This patch reenables BH to release the buffer. Log messages when the bug is hit: kernel BUG at mm/vmalloc.c:2727! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU:

    • Обновитесь до 5.15.0-50.56~20.04.1
  11. CVE-2022-49623

    Высокий · CVSS 7.1EPSS 0,28%Есть исправление

    powerpc/xive/spapr: correct bitmap allocation size

    In the Linux kernel, the following vulnerability has been resolved: powerpc/xive/spapr: correct bitmap allocation size kasan detects access beyond the end of the xibm->bitmap allocation: BUG: KASAN: slab-out-of-bounds in _find_first_zero_bit+0x40/0x140 Read of size 8 at addr c00000001d1d0118 by task swapper/0/1 CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.19.0-rc2-00001-g90df023b36dd #28 Call Trace: [c00000001d98f770] [c0000000012baab8] dump_stack_lvl+0xac/0x108 (unreliable) [c00000001d98f7b0] [c00000000068faac] print_report+0x37c/0x710 [c00000001d98f880] [c0000000006902c0] kasan_report+0x110/0x354 [c00000001d98f950] [c000000000692324] __a

    • Обновитесь до 5.15.0-50.56~20.04.1
  12. CVE-2022-49621

    Средний · CVSS 5.5EPSS 0,26%Есть исправление

    cpufreq: pmac32-cpufreq: Fix refcount leak bug

    In the Linux kernel, the following vulnerability has been resolved: cpufreq: pmac32-cpufreq: Fix refcount leak bug In pmac_cpufreq_init_MacRISC3(), we need to add corresponding of_node_put() for the three node pointers whose refcount have been incremented by of_find_node_by_name().

    • Обновитесь до 5.15.0-50.56~20.04.1
  13. CVE-2022-49620

    Средний · CVSS 5.5EPSS 0,27%Есть исправление

    net: tipc: fix possible refcount leak in tipc_sk_create()

    In the Linux kernel, the following vulnerability has been resolved: net: tipc: fix possible refcount leak in tipc_sk_create() Free sk in case tipc_sk_insert() fails.

    • Обновитесь до 5.15.0-50.56~20.04.1
  14. CVE-2022-49619

    Средний · CVSS 5.5EPSS 0,27%Есть исправление

    net: sfp: fix memory leak in sfp_probe()

    In the Linux kernel, the following vulnerability has been resolved: net: sfp: fix memory leak in sfp_probe() sfp_probe() allocates a memory chunk from sfp with sfp_alloc(). When devm_add_action() fails, sfp is not freed, which leads to a memory leak. We should use devm_add_action_or_reset() instead of devm_add_action().

    • Обновитесь до 5.15.0-50.56~20.04.1
  15. CVE-2022-49618

    Средний · CVSS 5.5EPSS 0,26%Есть исправление

    pinctrl: aspeed: Fix potential NULL dereference in aspeed_pinmux_set_mux()

    In the Linux kernel, the following vulnerability has been resolved: pinctrl: aspeed: Fix potential NULL dereference in aspeed_pinmux_set_mux() pdesc could be null but still dereference pdesc->name and it will lead to a null pointer access. So we move a null check before dereference.

    • Обновитесь до 5.15.0-50.56~20.04.1
    Опубликовано Обновлено
  16. CVE-2022-49617

    Средний · CVSS 5.5EPSS 0,26%Есть исправление

    ASoC: Intel: sof_sdw: handle errors on card registration

    In the Linux kernel, the following vulnerability has been resolved: ASoC: Intel: sof_sdw: handle errors on card registration If the card registration fails, typically because of deferred probes, the device properties added for headset codecs are not removed, which leads to kernel oopses in driver bind/unbind tests. We already clean-up the device properties when the card is removed, this code can be moved as a helper and called upon card registration errors.

    • Обновитесь до 5.15.0-50.56~20.04.1
  17. CVE-2022-49616

    Средний · CVSS 5.5EPSS 0,26%Есть исправление

    ASoC: rt7*-sdw: harden jack_detect_handler

    In the Linux kernel, the following vulnerability has been resolved: ASoC: rt7*-sdw: harden jack_detect_handler Realtek headset codec drivers typically check if the card is instantiated before proceeding with the jack detection. The rt700, rt711 and rt711-sdca are however missing a check on the card pointer, which can lead to NULL dereferences encountered in driver bind/unbind tests.

    • Обновитесь до 5.15.0-50.56~20.04.1
  18. CVE-2022-49615

    Средний · CVSS 5.5EPSS 0,26%Есть исправление

    ASoC: rt711-sdca: fix kernel NULL pointer dereference when IO error

    In the Linux kernel, the following vulnerability has been resolved: ASoC: rt711-sdca: fix kernel NULL pointer dereference when IO error The initial settings will be written before the codec probe function. But, the rt711->component doesn't be assigned yet. If IO error happened during initial settings operations, it will cause the kernel panic. This patch changed component->dev to slave->dev to fix this issue.

    • Обновитесь до 5.15.0-50.56~20.04.1
  19. CVE-2022-49613

    Средний · CVSS 5.5EPSS 0,26%Есть исправление

    serial: 8250: Fix PM usage_count for console handover

    In the Linux kernel, the following vulnerability has been resolved: serial: 8250: Fix PM usage_count for console handover When console is enabled, univ8250_console_setup() calls serial8250_console_setup() before .dev is set to uart_port. Therefore, it will not call pm_runtime_get_sync(). Later, when the actual driver is going to take over univ8250_console_exit() is called. As .dev is already set, serial8250_console_exit() makes pm_runtime_put_sync() call with usage count being zero triggering PM usage count warning (extra debug for univ8250_console_setup(), univ8250_console_exit(), and serial8250_register_ports()): [ 0.068987] univ8250_

    • Обновитесь до 5.15.0-50.56~20.04.1
  20. CVE-2022-49611

    Средний · CVSS 6.9EPSS 0,28%Есть исправление

    x86/speculation: Fill RSB on vmexit for IBRS

    In the Linux kernel, the following vulnerability has been resolved: x86/speculation: Fill RSB on vmexit for IBRS Prevent RSB underflow/poisoning attacks with RSB. While at it, add a bunch of comments to attempt to document the current state of tribal knowledge about RSB attacks and what exactly is being mitigated.

    • Обновитесь до 5.15.0-46.49~20.04.1

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

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

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