Skip to content
OpenAdvisories
High ALAS2023-2025-1053 9 CVEs

Important: kernel6.12 security update (Amazon Linux 2023)

Published Jul 1, 2025 · Updated Jul 29, 2025

Summary

Package updates are available for Amazon Linux 2023 that fix the following vulnerabilities: CVE-2025-38095: In the Linux kernel, the following vulnerability has been resolved: dma-buf: insert memory barrier before updating num_fences CVE-2025-38023: In the Linux kernel, the following vulnerability has been resolved: nfs: handle failure of nfs_get_lock_context in unlock path CVE-2025-38022: In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem CVE-2025-38020: In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Disable MACsec offload for uplink representor profile CVE-2025-38018: In the Linux kernel, the following vulnerability has been resolved: net/tls: fix kernel panic when alloc_page failed CVE-2025-38016: In the Linux kernel, the following vulnerability has been resolved: HID: bpf: abort dispatch if device destroyed CVE-2025-38012: In the Linux kernel, the following vulnerability has been resolved: sched_ext: bpf_iter_scx_dsq_new() should always initialize iterator CVE-2025-38008: In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: fix race condition in unaccepted memory handling CVE-2025-37992: In the Linux kernel, the following vulnerability has been resolved: net_sched: Flush gso_skb list too during ->change()

Fixed packages 22

ReleasePackageFixed in
Amazon Linux · 2023 bpftool 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 bpftool-debuginfo 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel-devel 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel-headers 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel-libbpf 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel-libbpf-debuginfo 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel-libbpf-devel 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel-libbpf-static 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel-livepatch-6.12.30-34.92 0:1.0-0.amzn2023
Amazon Linux · 2023 kernel-modules-extra-common 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel-tools 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel-tools-debuginfo 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel-tools-devel 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel6.12 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel6.12-debuginfo 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel6.12-debuginfo-common-aarch64 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel6.12-debuginfo-common-x86_64 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 kernel6.12-modules-extra 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 perf6.12 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 perf6.12-debuginfo 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 python3-perf6.12 0:6.12.30-34.92.amzn2023
Amazon Linux · 2023 python3-perf6.12-debuginfo 0:6.12.30-34.92.amzn2023

Vulnerabilities 9

  • High 8.8

    HID: bpf: abort dispatch if device destroyed

    In the Linux kernel, the following vulnerability has been resolved: HID: bpf: abort dispatch if device destroyed The current HID bpf implementation assumes no output report/request will go through it after hid_bpf_destroy_device() has been called. This leads …

  • High 7.8

    sched_ext: bpf_iter_scx_dsq_new() should always initialize iterator

    In the Linux kernel, the following vulnerability has been resolved: sched_ext: bpf_iter_scx_dsq_new() should always initialize iterator BPF programs may call next() and destroy() on BPF iterators even after new() returns an error value (e.g. bpf_for_each() ma…

  • High 7.8

    RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem

    In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_addr…

  • High 7.8

    dma-buf: insert memory barrier before updating num_fences

    In the Linux kernel, the following vulnerability has been resolved: dma-buf: insert memory barrier before updating num_fences smp_store_mb() inserts memory barrier after storing operation. It is different with what the comment is originally aiming so Null poi…

  • High 7.5

    net/tls: fix kernel panic when alloc_page failed

    In the Linux kernel, the following vulnerability has been resolved: net/tls: fix kernel panic when alloc_page failed We cannot set frag_list to NULL pointer when alloc_page failed. It will be used in tls_strp_check_queue_ok when the next time tls_strp_read_so…

  • Unscored —

    net_sched: Flush gso_skb list too during ->change()

    In the Linux kernel, the following vulnerability has been resolved: net_sched: Flush gso_skb list too during ->change() Previously, when reducing a qdisc's limit via the ->change() operation, only the main skb queue was trimmed, potentially leaving packets in…

  • Unscored —

    mm/page_alloc: fix race condition in unaccepted memory handling

    In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: fix race condition in unaccepted memory handling The page allocator tracks the number of zones that have unaccepted memory using static_branch_enc/dec() and uses that static br…

  • Unscored —

    net/mlx5e: Disable MACsec offload for uplink representor profile

    In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Disable MACsec offload for uplink representor profile MACsec offload is not supported in switchdev mode for uplink representors. When switching to the uplink representor profile, t…

  • Unscored —

    nfs: handle failure of nfs_get_lock_context in unlock path

    In the Linux kernel, the following vulnerability has been resolved: nfs: handle failure of nfs_get_lock_context in unlock path When memory is insufficient, the allocation of nfs_lock_context in nfs_get_lock_context() fails and returns -ENOMEM. If we mistakenl…

References

  • web
    https://alas.aws.amazon.com/cve/html/CVE-2025-37992.html
  • web
    https://alas.aws.amazon.com/cve/html/CVE-2025-38008.html
  • web
    https://alas.aws.amazon.com/cve/html/CVE-2025-38012.html
  • web
    https://alas.aws.amazon.com/cve/html/CVE-2025-38016.html
  • web
    https://alas.aws.amazon.com/cve/html/CVE-2025-38018.html
  • web
    https://alas.aws.amazon.com/cve/html/CVE-2025-38020.html
  • web
    https://alas.aws.amazon.com/cve/html/CVE-2025-38022.html
  • web
    https://alas.aws.amazon.com/cve/html/CVE-2025-38023.html
  • web
    https://alas.aws.amazon.com/cve/html/CVE-2025-38095.html