p PatchFirst

PatchFirst · Latest vulnerabilities

linux-lowlatency-hwe-5.15 vulnerabilities · Page 88

Vulnerabilities published for linux-lowlatency-hwe-5.15 in the last 30 days: 0. Listed in the KEV catalogue: 0.

RSS ↗ JSON ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 4519

  1. CVE-2022-49642

    Medium · CVSS 5.5EPSS 0.26%Fix available

    net: stmmac: dwc-qos: Disable split header for Tegra194

    In the Linux kernel, the following vulnerability has been resolved: net: stmmac: dwc-qos: Disable split header for Tegra194 There is a long-standing issue with the Synopsys DWC Ethernet driver for Tegra194 where random system crashes have been observed [0]. The problem occurs when the split header feature is enabled in the stmmac driver. In the bad case, a larger than expected buffer length is received and causes the calculation of the total buffer length to overflow. This results in a very large buffer length that causes the kernel to crash. Why this larger buffer length is received is not clear, however, the feedback from the NVIDIA desig

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  2. CVE-2022-49641

    Medium · CVSS 4.7EPSS 0.18%Fix available

    sysctl: Fix data races in proc_douintvec().

    In the Linux kernel, the following vulnerability has been resolved: sysctl: Fix data races in proc_douintvec(). 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_douintvec() to use READ_ONCE() and WRITE_ONCE() internally to fix data-races on the sysctl side. For now, proc_douintvec() itself is tolerant to a data-race, but we still need to add annotations on the other subsystem's side.

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  3. CVE-2022-49640

    Medium · CVSS 4.7EPSS 0.18%Fix available

    sysctl: Fix data races in proc_douintvec_minmax().

    In the Linux kernel, the following vulnerability has been resolved: sysctl: Fix data races in proc_douintvec_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_douintvec_minmax() to use READ_ONCE() and WRITE_ONCE() internally to fix data-races on the sysctl side. For now, proc_douintvec_minmax() itself is tolerant to a data-race, but we still need to add annotations on the other subsystem's side.

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  4. CVE-2022-49639

    Medium · CVSS 4.7EPSS 0.18%Fix available

    cipso: Fix data-races around sysctl.

    In the Linux kernel, the following vulnerability has been resolved: cipso: Fix data-races around sysctl. While reading cipso sysctl variables, they can be changed concurrently. So, we need to add READ_ONCE() to avoid data-races.

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  6. CVE-2022-49637

    Medium · CVSS 4.7EPSS 0.18%Fix available

    ipv4: Fix a data-race around sysctl_fib_sync_mem.

    In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix a data-race around sysctl_fib_sync_mem. While reading sysctl_fib_sync_mem, it can be changed concurrently. So, we need to add READ_ONCE() to avoid a data-race.

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  7. CVE-2022-49634

    Medium · CVSS 4.7EPSS 0.18%Fix available

    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.

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  8. CVE-2022-49633

    Medium · CVSS 4.7EPSS 0.18%Fix available

    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.

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  9. CVE-2022-49632

    Medium · CVSS 4.7EPSS 0.18%Fix available

    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.

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  10. CVE-2022-49631

    Medium · CVSS 4.7EPSS 0.18%Fix available

    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.

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  11. CVE-2022-49630

    Medium · CVSS 4.7EPSS 0.18%Fix available

    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.

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  12. CVE-2022-49629

    Medium · CVSS 4.7EPSS 0.18%Fix available

    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.

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  14. CVE-2022-49627

    Medium · CVSS 5.5EPSS 0.27%Fix available

    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.

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  15. CVE-2022-49626

    High · CVSS 7.8EPSS 0.28%Fix available

    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

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  16. CVE-2022-49625

    Medium · CVSS 5.7EPSS 0.29%Fix available

    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:

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  17. CVE-2022-49623

    High · CVSS 7.1EPSS 0.28%Fix available

    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

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  18. CVE-2022-49621

    Medium · CVSS 5.5EPSS 0.26%Fix available

    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().

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  20. CVE-2022-49619

    Medium · CVSS 5.5EPSS 0.27%Fix available

    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().

    linux-lowlatency-hwe-5.15Operating systems
    • Update to 5.15.0-50.56~20.04.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →