Skip to content
OpenAdvisories
High USN-7195-2 39 CVEs

linux-azure-5.4 vulnerabilities

Published Jan 14, 2025 · Updated Oct 29, 2026

Summary

Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not
properly handle certain error conditions, leading to a NULL pointer
dereference. A local attacker could possibly trigger this vulnerability to
cause a denial of service. (CVE-2022-38096)

Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
- ARM32 architecture;
- ARM64 architecture;
- S390 architecture;
- x86 architecture;
- Power management core;
- GPU drivers;
- InfiniBand drivers;
- Network drivers;
- S/390 drivers;
- SCSI subsystem;
- TTY drivers;
- BTRFS file system;
- Ext4 file system;
- EROFS file system;
- F2FS file system;
- File systems infrastructure;
- BPF subsystem;
- Socket messages infrastructure;
- Bluetooth subsystem;
- Memory management;
- Amateur Radio drivers;
- Ethernet bridge;
- Networking core;
- IPv4 networking;
- Network traffic control;
- Sun RPC protocol;
- VMware vSockets driver;
- SELinux security module;
(CVE-2024-42240, CVE-2024-36938, CVE-2024-35967, CVE-2024-36953,
CVE-2022-48938, CVE-2024-38553, CVE-2024-35904, CVE-2024-35965,
CVE-2024-26947, CVE-2024-36968, CVE-2024-43892, CVE-2024-38597,
CVE-2023-52498, CVE-2021-47501, CVE-2024-44942, CVE-2024-42077,
CVE-2024-53057, CVE-2024-46724, CVE-2024-35963, CVE-2022-48943,
CVE-2024-42068, CVE-2024-42156, CVE-2022-48733, CVE-2023-52639,
CVE-2021-47101, CVE-2023-52821, CVE-2024-44940, CVE-2024-36952,
CVE-2021-47001, CVE-2024-38538, CVE-2024-40910, CVE-2021-47076,
CVE-2024-35966, CVE-2024-50264, CVE-2024-35951, CVE-2023-52488,
CVE-2023-52497, CVE-2024-49967)

Fixed packages 1

ReleasePackageFixed in
Ubuntu · Pro 18.04 LTS Pro:18.04:LTS linux-azure-5.4 5.4.0-1142.149~18.04.1

Vulnerabilities 39

  • High 8.8

    ax25: Fix refcount imbalance on inbound connections

    In the Linux kernel, the following vulnerability has been resolved: ax25: Fix refcount imbalance on inbound connections When releasing a socket in ax25_release(), we call netdev_put() to decrease the refcount on the associated ax.25 device. However, the execu…

  • High 7.8

    btrfs: fix use-after-free after failure to create a snapshot

    In the Linux kernel, the following vulnerability has been resolved: btrfs: fix use-after-free after failure to create a snapshot At ioctl.c:create_snapshot(), we allocate a pending snapshot structure and then attach it to the transaction's list of pending sna…

  • High 7.8

    drm/panfrost: Fix the error path in panfrost_mmu_map_fault_addr()

    In the Linux kernel, the following vulnerability has been resolved: drm/panfrost: Fix the error path in panfrost_mmu_map_fault_addr() Subject: [PATCH] drm/panfrost: Fix the error path in panfrost_mmu_map_fault_addr() If some the pages or sgt allocation failed…

  • High 7.8

    bpf: Take return from set_memory_ro() into account with bpf_prog_lock_ro()

    In the Linux kernel, the following vulnerability has been resolved: bpf: Take return from set_memory_ro() into account with bpf_prog_lock_ro() set_memory_ro() can fail, leaving memory unprotected. Check its return and take it into account as an error.

  • High 7.8

    memcg: protect concurrent access to mem_cgroup_idr

    In the Linux kernel, the following vulnerability has been resolved: memcg: protect concurrent access to mem_cgroup_idr Commit 73f576c04b94 ("mm: memcontrol: fix cgroup creation failure after many small jobs") decoupled the memcg IDs from the CSS ID space to f…

  • High 7.8

    f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GC

    In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GC syzbot reports a f2fs bug as below: ------------[ cut here ]------------ kernel BUG at fs/f2fs/inline.c:258! CPU: 1 PI…

  • High 7.8

    vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans

    In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans During loopback communication, a dangling pointer can be created in vsk->trans, potentially leading to a Use-After…

  • High 7.8

    net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT

    In the Linux kernel, the following vulnerability has been resolved: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT In qdisc_tree_reduce_backlog, Qdiscs with major handle ffff: are assumed to be either root or ingress. This assumption is bogus since it…

  • High 7.6

    Bluetooth: L2CAP: Fix div-by-zero in l2cap_le_flowctl_init()

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix div-by-zero in l2cap_le_flowctl_init() l2cap_le_flowctl_init() can cause both div-by-zero and an integer overflow since hdev->le_mtu may not fall in the valid range. Mov…

  • High 7.5

    xprtrdma: Fix cwnd update ordering

    In the Linux kernel, the following vulnerability has been resolved: xprtrdma: Fix cwnd update ordering After a reconnect, the reply handler is opening the cwnd (and thus enabling more RPC Calls to be sent) /before/ rpcrdma_post_recvs() can post enough Receive…

  • High 7.5

    fou: remove warn in gue_gro_receive on unsupported protocol

    In the Linux kernel, the following vulnerability has been resolved: fou: remove warn in gue_gro_receive on unsupported protocol Drop the WARN_ON_ONCE inn gue_gro_receive if the encapsulated type is not known or does not have a GRO handler. Such a packet is ea…

  • High 7.3

    net: bridge: xmit: make sure we have at least eth header len bytes

    In the Linux kernel, the following vulnerability has been resolved: net: bridge: xmit: make sure we have at least eth header len bytes syzbot triggered an uninit value[1] error in bridge device's xmit path by sending a short (less than ETH_HLEN bytes) skb. To…

  • High 7.1

    KVM: x86/mmu: make apf token non-zero to fix bug

    In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: make apf token non-zero to fix bug In current async pagefault logic, when a page is ready, KVM relies on kvm_arch_can_dequeue_async_page_present() to determine whether to delive…

  • High 7.1

    erofs: fix lz4 inplace decompression

    In the Linux kernel, the following vulnerability has been resolved: erofs: fix lz4 inplace decompression Currently EROFS can map another compressed buffer for inplace decompression, that was used to handle the cases that some pages of compressed data are actu…

  • High 7.1

    Bluetooth: hci_sock: Fix not validating setsockopt user input

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sock: Fix not validating setsockopt user input Check user input length before copying data.

  • High 7.1

    Bluetooth: SCO: Fix not validating setsockopt user input

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: Fix not validating setsockopt user input syzbot reported sco_sock_setsockopt() is copying data without checking user input length. BUG: KASAN: slab-out-of-bounds in copy_from_…

  • Medium 6.3

    There is a NULL pointer vulnerability in vmwgfx driver

    A NULL pointer dereference vulnerability was found in vmwgfx driver in drivers/gpu/vmxgfx/vmxgfx_execbuf.c in GPU component of Linux kernel with device file '/dev/dri/renderD128 (or Dxxx)'. This flaw allows a local attacker with a user account on the system t…

  • Medium 4.4

    KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr()

    In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr() vgic_v2_parse_attr() is responsible for finding the vCPU that matches the user-provided CPUID, which (of course) may not b…

  • Unscored —

    RDMA/rxe: Return CQE error if invalid lkey was supplied

    In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Return CQE error if invalid lkey was supplied RXE is missing update of WQE status in LOCAL_WRITE failures. This caused the following kernel panic if someone sent an atomic operation…

  • Unscored —

    asix: fix uninit-value in asix_mdio_read()

    In the Linux kernel, the following vulnerability has been resolved: asix: fix uninit-value in asix_mdio_read() asix_read_cmd() may read less than sizeof(smsr) bytes and in this case smsr will be uninitialized. Fail log: BUG: KMSAN: uninit-value in asix_check_…

  • Unscored —

    i40e: Fix NULL pointer dereference in i40e_dbg_dump_desc

    In the Linux kernel, the following vulnerability has been resolved: i40e: Fix NULL pointer dereference in i40e_dbg_dump_desc When trying to dump VFs VSI RX/TX descriptors using debugfs there was a crash due to NULL pointer dereference in i40e_dbg_dump_desc. A…

  • Unscored —

    CDC-NCM: avoid overflow in sanity checking

    In the Linux kernel, the following vulnerability has been resolved: CDC-NCM: avoid overflow in sanity checking A broken device may give an extreme offset like 0xFFF0 and a reasonable length for a fragment. In the sanity check as formulated now, this will crea…

  • Unscored —

    serial: sc16is7xx: convert from _raw_ to _noinc_ regmap functions for FIFO

    In the Linux kernel, the following vulnerability has been resolved: serial: sc16is7xx: convert from _raw_ to _noinc_ regmap functions for FIFO The SC16IS7XX IC supports a burst mode to access the FIFOs where the initial register address is sent ($00), followe…

  • Unscored —

    PM: sleep: Fix possible deadlocks in core system-wide PM code

    In the Linux kernel, the following vulnerability has been resolved: PM: sleep: Fix possible deadlocks in core system-wide PM code It is reported that in low-memory situations the system-wide resume core code deadlocks, because async_schedule_dev() executes it…

  • Unscored —

    KVM: s390: vsie: fix race during shadow creation

    In the Linux kernel, the following vulnerability has been resolved: KVM: s390: vsie: fix race during shadow creation Right now it is possible to see gmap->private being zero in kvm_s390_vsie_gmap_notifier resulting in a crash. This is due to the fact that we …

  • Unscored —

    drm/panel: fix a possible null pointer dereference

    In the Linux kernel, the following vulnerability has been resolved: drm/panel: fix a possible null pointer dereference In versatile_panel_get_modes(), the return value of drm_mode_duplicate() is assigned to mode, which will lead to a NULL pointer dereference …

  • Unscored —

    ARM: 9359/1: flush: check if the folio is reserved for no-mapping addresses

    In the Linux kernel, the following vulnerability has been resolved: ARM: 9359/1: flush: check if the folio is reserved for no-mapping addresses Since commit a4d5613c4dc6 ("arm: extend pfn_valid to take into account freed memory map alignment") changes the sem…

  • Unscored —

    selinux: avoid dereference of garbage after mount failure

    In the Linux kernel, the following vulnerability has been resolved: selinux: avoid dereference of garbage after mount failure In case kern_mount() fails and returns an error pointer return in the error branch instead of continuing and dereferencing the error …

  • Unscored —

    Bluetooth: L2CAP: Fix not validating setsockopt user input

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix not validating setsockopt user input Check user input length before copying data.

  • Unscored —

    Bluetooth: RFCOMM: Fix not validating setsockopt user input

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: Fix not validating setsockopt user input syzbot reported rfcomm_sock_setsockopt_old() is copying data without checking user input length. BUG: KASAN: slab-out-of-bounds in …

  • Unscored —

    bpf, skmsg: Fix NULL pointer dereference in sk_psock_skb_ingress_enqueue

    In the Linux kernel, the following vulnerability has been resolved: bpf, skmsg: Fix NULL pointer dereference in sk_psock_skb_ingress_enqueue Fix NULL pointer data-races in sk_psock_skb_ingress_enqueue() which syzbot reported [1]. [1] BUG: KCSAN: data-race in …

  • Unscored —

    scsi: lpfc: Move NPIV's transport unregistration to after resource clean up

    In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Move NPIV's transport unregistration to after resource clean up There are cases after NPIV deletion where the fabric switch still believes the NPIV is logged into the fabric. This…

  • Unscored —

    net: fec: remove .ndo_poll_controller to avoid deadlocks

    In the Linux kernel, the following vulnerability has been resolved: net: fec: remove .ndo_poll_controller to avoid deadlocks There is a deadlock issue found in sungem driver, please refer to the commit ac0a230f719b ("eth: sungem: remove .ndo_poll_controller t…

  • Unscored —

    eth: sungem: remove .ndo_poll_controller to avoid deadlocks

    In the Linux kernel, the following vulnerability has been resolved: eth: sungem: remove .ndo_poll_controller to avoid deadlocks Erhard reports netpoll warnings from sungem: netpoll_send_skb_on_dev(): eth0 enabled interrupts in poll (gem_start_xmit+0x0/0x398) …

  • Unscored —

    ocfs2: fix DIO failure due to insufficient transaction credits

    In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix DIO failure due to insufficient transaction credits The code in ocfs2_dio_end_io_write() estimates number of necessary transaction credits using ocfs2_calc_extend_credits(). This h…

  • Unscored —

    s390/pkey: Wipe copies of clear-key structures on failure

    In the Linux kernel, the following vulnerability has been resolved: s390/pkey: Wipe copies of clear-key structures on failure Wipe all sensitive data from stack for all IOCTLs, which convert a clear-key into a protected- or secure-key.

  • Unscored —

    x86/bhi: Avoid warning in #DB handler due to BHI mitigation

    In the Linux kernel, the following vulnerability has been resolved: x86/bhi: Avoid warning in #DB handler due to BHI mitigation When BHI mitigation is enabled, if SYSENTER is invoked with the TF flag set then entry_SYSENTER_compat() uses CLEAR_BRANCH_HISTORY …

  • Unscored —

    drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number Check the fb_channel_number range to avoid the array out-of-bounds read error

  • Unscored —
    CVE-2024-49967 Rejected

    This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

References

  • report
    https://ubuntu.com/security/CVE-2021-47001
  • report
    https://ubuntu.com/security/CVE-2021-47076
  • report
    https://ubuntu.com/security/CVE-2021-47101
  • report
    https://ubuntu.com/security/CVE-2021-47501
  • report
    https://ubuntu.com/security/CVE-2022-38096
  • report
    https://ubuntu.com/security/CVE-2022-48733
  • report
    https://ubuntu.com/security/CVE-2022-48938
  • report
    https://ubuntu.com/security/CVE-2022-48943
  • report
    https://ubuntu.com/security/CVE-2023-52488
  • report
    https://ubuntu.com/security/CVE-2023-52497
  • report
    https://ubuntu.com/security/CVE-2023-52498
  • report
    https://ubuntu.com/security/CVE-2023-52639
  • report
    https://ubuntu.com/security/CVE-2023-52821
  • report
    https://ubuntu.com/security/CVE-2024-26947
  • report
    https://ubuntu.com/security/CVE-2024-35904
  • report
    https://ubuntu.com/security/CVE-2024-35951
  • report
    https://ubuntu.com/security/CVE-2024-35963
  • report
    https://ubuntu.com/security/CVE-2024-35965
  • report
    https://ubuntu.com/security/CVE-2024-35966
  • report
    https://ubuntu.com/security/CVE-2024-35967
  • report
    https://ubuntu.com/security/CVE-2024-36938
  • report
    https://ubuntu.com/security/CVE-2024-36952
  • report
    https://ubuntu.com/security/CVE-2024-36953
  • report
    https://ubuntu.com/security/CVE-2024-36968
  • report
    https://ubuntu.com/security/CVE-2024-38538
  • report
    https://ubuntu.com/security/CVE-2024-38553
  • report
    https://ubuntu.com/security/CVE-2024-38597
  • report
    https://ubuntu.com/security/CVE-2024-40910
  • report
    https://ubuntu.com/security/CVE-2024-42068
  • report
    https://ubuntu.com/security/CVE-2024-42077
  • report
    https://ubuntu.com/security/CVE-2024-42156
  • report
    https://ubuntu.com/security/CVE-2024-42240
  • report
    https://ubuntu.com/security/CVE-2024-43892
  • report
    https://ubuntu.com/security/CVE-2024-44940
  • report
    https://ubuntu.com/security/CVE-2024-44942
  • report
    https://ubuntu.com/security/CVE-2024-46724
  • report
    https://ubuntu.com/security/CVE-2024-49967
  • report
    https://ubuntu.com/security/CVE-2024-50264
  • report
    https://ubuntu.com/security/CVE-2024-53057