p PatchFirst

PatchFirst · Latest vulnerabilities

linux-aws-5.15 vulnerabilities · Page 60

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

Filter vulnerabilities
Clear filters

Vulnerabilities: 4244

  1. CVE-2022-50080

    Medium · CVSS 5.5EPSS 0.27%Fix available

    tee: add overflow check in register_shm_helper()

    In the Linux kernel, the following vulnerability has been resolved: tee: add overflow check in register_shm_helper() With special lengths supplied by user space, register_shm_helper() has an integer overflow when calculating the number of pages covered by a supplied user space memory region. This causes internal_get_user_pages_fast() a helper function of pin_user_pages_fast() to do a NULL pointer dereference: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010 Modules linked in: CPU: 1 PID: 173 Comm: optee_example_a Not tainted 5.19.0 #11 Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  2. CVE-2022-50079

    High · CVSS 7EPSS 0.27%Fix available

    drm/amd/display: Check correct bounds for stream encoder instances for DCN303

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check correct bounds for stream encoder instances for DCN303 [Why & How] eng_id for DCN303 cannot be more than 1, since we have only two instances of stream encoders. Check the correct boundary condition for engine ID for DCN303 prevent the potential out of bounds access.

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  3. CVE-2022-50078

    Medium · CVSS 5.5EPSS 0.24%Fix available

    tracing/eprobes: Do not allow eprobes to use $stack, or % for regs

    In the Linux kernel, the following vulnerability has been resolved: tracing/eprobes: Do not allow eprobes to use $stack, or % for regs While playing with event probes (eprobes), I tried to see what would happen if I attempted to retrieve the instruction pointer (%rip) knowing that event probes do not use pt_regs. The result was: BUG: kernel NULL pointer dereference, address: 0000000000000024 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 1847 Comm: trace-cmd Not tainted 5.19.0-rc5-test+ #309 Hardware name: Hewlett-Packard HP Compaq Pro 630

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  4. CVE-2022-50077

    Medium · CVSS 5.5EPSS 0.19%Fix available

    apparmor: fix reference count leak in aa_pivotroot()

    In the Linux kernel, the following vulnerability has been resolved: apparmor: fix reference count leak in aa_pivotroot() The aa_pivotroot() function has a reference counting bug in a specific path. When aa_replace_current_label() returns on success, the function forgets to decrement the reference count of “target”, which is increased earlier by build_pivotroot(), causing a reference leak. Fix it by decreasing the refcount of “target” in that path.

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  5. CVE-2022-50076

    Medium · CVSS 5.5EPSS 0.19%Fix available

    cifs: Fix memory leak on the deferred close

    In the Linux kernel, the following vulnerability has been resolved: cifs: Fix memory leak on the deferred close xfstests on smb21 report kmemleak as below: unreferenced object 0xffff8881767d6200 (size 64): comm "xfs_io", pid 1284, jiffies 4294777434 (age 20.789s) hex dump (first 32 bytes): 80 5a d0 11 81 88 ff ff 78 8a aa 63 81 88 ff ff .Z......x..c.... 00 71 99 76 81 88 ff ff 00 00 00 00 00 00 00 00 .q.v............ backtrace: [<00000000ad04e6ea>] cifs_close+0x92/0x2c0 [<0000000028b93c82>] __fput+0xff/0x3f0 [<00000000d8116851>] task_work_run+0x85/0xc0 [<0000000027e14f9e>] do_exit+0x5e5/0

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  6. CVE-2022-50075

    Medium · CVSS 5.5EPSS 0.19%Fix available

    tracing/eprobes: Have event probes be consistent with kprobes and uprobes

    In the Linux kernel, the following vulnerability has been resolved: tracing/eprobes: Have event probes be consistent with kprobes and uprobes Currently, if a symbol "@" is attempted to be used with an event probe (eprobes), it will cause a NULL pointer dereference crash. Both kprobes and uprobes can reference data other than the main registers. Such as immediate address, symbols and the current task name. Have eprobes do the same thing. For "comm", if "comm" is used and the event being attached to does not have the "comm" field, then make it the "$comm" that kprobes has. This is consistent to the way histograms and filters work.

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  7. CVE-2022-50074

    Medium · CVSS 5.5EPSS 0.19%Fix available

    apparmor: Fix memleak in aa_simple_write_to_buffer()

    In the Linux kernel, the following vulnerability has been resolved: apparmor: Fix memleak in aa_simple_write_to_buffer() When copy_from_user failed, the memory is freed by kvfree. however the management struct and data blob are allocated independently, so only kvfree(data) cause a memleak issue here. Use aa_put_loaddata(data) to fix this issue.

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  8. CVE-2022-50072

    High · CVSS 7.8EPSS 0.2%Fix available

    NFSv4/pnfs: Fix a use-after-free bug in open

    In the Linux kernel, the following vulnerability has been resolved: NFSv4/pnfs: Fix a use-after-free bug in open If someone cancels the open RPC call, then we must not try to free either the open slot or the layoutget operation arguments, since they are likely still in use by the hung RPC call.

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  9. CVE-2022-50069

    Medium · CVSS 5.5EPSS 0.24%Fix available

    BPF: Fix potential bad pointer dereference in bpf_sys_bpf()

    In the Linux kernel, the following vulnerability has been resolved: BPF: Fix potential bad pointer dereference in bpf_sys_bpf() The bpf_sys_bpf() helper function allows an eBPF program to load another eBPF program from within the kernel. In this case the argument union bpf_attr pointer (as well as the insns and license pointers inside) is a kernel address instead of a userspace address (which is the case of a usual bpf() syscall). To make the memory copying process in the syscall work in both cases, bpfptr_t was introduced to wrap around the pointer and distinguish its origin. Specifically, when copying memory contents from a bpfptr_t, a co

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  10. CVE-2022-50068

    Medium · CVSS 5.5EPSS 0.24%Fix available

    drm/ttm: Fix dummy res NULL ptr deref bug

    In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Fix dummy res NULL ptr deref bug Check the bo->resource value before accessing the resource mem_type. v2: Fix commit description unwrapped warning <log snip> [ 40.191227][ T184] general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] SMP KASAN PTI [ 40.192995][ T184] KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] [ 40.194411][ T184] CPU: 1 PID: 184 Comm: systemd-udevd Not tainted 5.19.0-rc4-00721-gb297c22b7070 #1 [ 40.196063][ T184] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  11. CVE-2022-50067

    High · CVSS 7.8EPSS 0.23%Fix available

    btrfs: unset reloc control if transaction commit fails in prepare_to_relocate()

    In the Linux kernel, the following vulnerability has been resolved: btrfs: unset reloc control if transaction commit fails in prepare_to_relocate() In btrfs_relocate_block_group(), the rc is allocated. Then btrfs_relocate_block_group() calls relocate_block_group() prepare_to_relocate() set_reloc_control() that assigns rc to the variable fs_info->reloc_ctl. When prepare_to_relocate() returns, it calls btrfs_commit_transaction() btrfs_start_dirty_block_groups() btrfs_alloc_path() kmem_cache_zalloc() which may fail for example (or other errors could happen). When the failure occurs, btrfs_relocate_block_group() detects t

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  12. CVE-2022-50066

    High · CVSS 7.8EPSS 0.2%Fix available

    net: atlantic: fix aq_vec index out of range error

    In the Linux kernel, the following vulnerability has been resolved: net: atlantic: fix aq_vec index out of range error The final update statement of the for loop exceeds the array range, the dereference of self->aq_vec[i] is not checked and then leads to the index out of range error. Also fixed this kind of coding style in other for loop. [ 97.937604] UBSAN: array-index-out-of-bounds in drivers/net/ethernet/aquantia/atlantic/aq_nic.c:1404:48 [ 97.937607] index 8 is out of range for type 'aq_vec_s *[8]' [ 97.937608] CPU: 38 PID: 3767 Comm: kworker/u256:18 Not tainted 5.19.0+ #2 [ 97.937610] Hardware name: Dell Inc. Precision 7865 To

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  13. CVE-2022-50065

    Medium · CVSS 5.5EPSS 0.19%Fix available

    virtio_net: fix memory leak inside XPD_TX with mergeable

    In the Linux kernel, the following vulnerability has been resolved: virtio_net: fix memory leak inside XPD_TX with mergeable When we call xdp_convert_buff_to_frame() to get xdpf, if it returns NULL, we should check if xdp_page was allocated by xdp_linearize_page(). If it is newly allocated, it should be freed here alone. Just like any other "goto err_xdp".

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  14. CVE-2022-50062

    High · CVSS 7.5EPSS 0.44%Fix available

    net: bgmac: Fix a BUG triggered by wrong bytes_compl

    In the Linux kernel, the following vulnerability has been resolved: net: bgmac: Fix a BUG triggered by wrong bytes_compl On one of our machines we got: kernel BUG at lib/dynamic_queue_limits.c:27! Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM CPU: 0 PID: 1166 Comm: irq/41-bgmac Tainted: G W O 4.14.275-rt132 #1 Hardware name: BRCM XGS iProc task: ee3415c0 task.stack: ee32a000 PC is at dql_completed+0x168/0x178 LR is at bgmac_poll+0x18c/0x6d8 pc : [<c03b9430>] lr : [<c04b5a18>] psr: 800a0313 sp : ee32be14 ip : 000005ea fp : 00000bd4 r10: ee558500 r9 : c0116298 r8 : 00000002 r7 : 00000000 r6 : ef128810 r5 : 0199326

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  15. CVE-2022-50061

    Medium · CVSS 5.5EPSS 0.19%Fix available

    pinctrl: nomadik: Fix refcount leak in nmk_pinctrl_dt_subnode_to_map

    In the Linux kernel, the following vulnerability has been resolved: pinctrl: nomadik: Fix refcount leak in nmk_pinctrl_dt_subnode_to_map of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak."

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  16. CVE-2022-50060

    Medium · CVSS 5.5EPSS 0.19%Fix available

    octeontx2-af: Fix mcam entry resource leak

    In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: Fix mcam entry resource leak The teardown sequence in FLR handler returns if no NIX LF is attached to PF/VF because it indicates that graceful shutdown of resources already happened. But there is a chance of all allocated MCAM entries not being freed by PF/VF. Hence free mcam entries even in case of detached LF.

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  17. CVE-2022-50059

    High · CVSS 7.5EPSS 0.44%Fix available

    ceph: don't leak snap_rwsem in handle_cap_grant

    In the Linux kernel, the following vulnerability has been resolved: ceph: don't leak snap_rwsem in handle_cap_grant When handle_cap_grant is called on an IMPORT op, then the snap_rwsem is held and the function is expected to release it before returning. It currently fails to do that in all cases which could lead to a deadlock.

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  18. CVE-2022-50057

    Medium · CVSS 5.5EPSS 0.19%Fix available

    fs/ntfs3: Fix NULL deref in ntfs_update_mftmirr

    In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix NULL deref in ntfs_update_mftmirr If ntfs_fill_super() wasn't called then sbi->sb will be equal to NULL. Code should check this ptr before dereferencing. Syzbot hit this issue via passing wrong mount param as can be seen from log below Fail log: ntfs3: Unknown parameter 'iochvrset' general protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f] CPU: 1 PID: 3589 Comm: syz-executor210 Not tainted 5.18.0-rc3-syzkaller-00016-gb253435746d9 #0 ... Cal

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  19. CVE-2022-50056

    Medium · CVSS 5.5EPSS 0.19%Fix available

    fs/ntfs3: Fix missing i_op in ntfs_read_mft

    In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix missing i_op in ntfs_read_mft There is null pointer dereference because i_op == NULL. The bug happens because we don't initialize i_op for records in $Extend.

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated
  20. CVE-2022-50055

    Medium · CVSS 5.5EPSS 0.19%Fix available

    iavf: Fix adminq error handling

    In the Linux kernel, the following vulnerability has been resolved: iavf: Fix adminq error handling iavf_alloc_asq_bufs/iavf_alloc_arq_bufs allocates with dma_alloc_coherent memory for VF mailbox. Free DMA regions for both ASQ and ARQ in case error happens during configuration of ASQ/ARQ registers. Without this change it is possible to see when unloading interface: 74626.583369: dma_debug_device_change: device driver has pending DMA allocations while released from device [count=32] One of leaked entries details: [device address=0x0000000b27ff9000] [size=4096 bytes] [mapped with DMA_BIDIRECTIONAL] [mapped as coherent]

    • Update to 5.15.0-1023.27~20.04.1
    Published Updated

Check your server

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

Check your server →