rpm package
suse/kernel-syms-azure&distro=SUSE Linux Enterprise Module for Public Cloud 15 SP7
pkg:rpm/suse/kernel-syms-azure&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Public%20Cloud%2015%20SP7
Vulnerabilities (2,117)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2025-40343 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: nvmet-fc: avoid scheduling association deletion twice When forcefully shutting down a port via the configfs interface, nvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and then nvmet_disable_por | ||
| CVE-2025-40342 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: nvme-fc: use lock accessing port_state and rport state nvme_fc_unregister_remote removes the remote port on a lport object at any point in time when there is no active association. This races with with the reco | ||
| CVE-2025-40340 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix oops in xe_gem_fault when running core_hotunplug test. I saw an oops in xe_gem_fault when running the xe-fast-feedback testlist against the realtime kernel without debug options enabled. The panic | ||
| CVE-2025-40339 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix nullptr err of vm_handle_moved If a amdgpu_bo_va is fpriv->prt_va, the bo of this one is always NULL. So, such kind of amdgpu_bo_va should be updated separately before amdgpu_vm_handle_moved. | ||
| CVE-2025-40338 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: ASoC: Intel: avs: Do not share the name pointer between components By sharing 'name' directly, tearing down components may lead to use-after-free errors. Duplicate the name to avoid that. At the same time, upd | ||
| CVE-2025-40337 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: net: stmmac: Correctly handle Rx checksum offload errors The stmmac_rx function would previously set skb->ip_summed to CHECKSUM_UNNECESSARY if hardware checksum offload (CoE) was enabled and the packet was of a | ||
| CVE-2025-40332 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix mmap write lock not release If mmap write lock is taken while draining retry fault, mmap write lock is not released because svm_range_restore_pages calls mmap_read_unlock then returns. This caus | ||
| CVE-2025-40331 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: sctp: Prevent TOCTOU out-of-bounds write For the following path not holding the sock lock, sctp_diag_dump() -> sctp_for_each_endpoint() -> sctp_ep_dump() make sure not to exceed bounds in case the address l | ||
| CVE-2025-40330 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Shutdown FW DMA in bnxt_shutdown() The netif_close() call in bnxt_shutdown() only stops packet DMA. There may be FW DMA for trace logging (recently added) that will continue. If we kexec to a new ker | ||
| CVE-2025-40329 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb The Mesa issue referenced below pointed out a possible deadlock: [ 1231.611031] Possible interrupt unsafe locking scenario: [ 1231.611033] CPU0 | ||
| CVE-2025-40328 | — | < 6.4.0-150700.20.27.1 | 6.4.0-150700.20.27.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in smb2_close_cached_fid() find_or_create_cached_dir() could grab a new reference after kref_put() had seen the refcount drop to zero but before cfid_list_lock is acquired in smb2 | ||
| CVE-2023-53865 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: btrfs: fix warning when putting transaction with qgroups enabled after abort If we have a transaction abort with qgroups enabled we get a warning triggered when doing the final put on the transaction, like this | ||
| CVE-2023-53864 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/mxsfb: Disable overlay plane in mxsfb_plane_overlay_atomic_disable() When disabling overlay plane in mxsfb_plane_overlay_atomic_update(), overlay plane's framebuffer pointer is NULL. So, dereferencing it w | ||
| CVE-2023-53863 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: netlink: do not hard code device address lenth in fdb dumps syzbot reports that some netdev devices do not have a six bytes address [1] Replace ETH_ALEN by dev->addr_len. [1] (Case of a device where dev->addr | ||
| CVE-2023-53861 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: ext4: correct grp validation in ext4_mb_good_group Group corruption check will access memory of grp and will trigger kernel crash if grp is NULL. So do NULL check before corruption check. | ||
| CVE-2023-53860 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: dm: don't attempt to queue IO under RCU protection dm looks up the table for IO based on the request type, with an assumption that if the request is marked REQ_NOWAIT, it's fine to attempt to submit that IO whi | ||
| CVE-2023-53858 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() in case of error If clk_get_rate() fails, the clk that has just been allocated needs to be freed. | ||
| CVE-2023-53857 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: bpf: bpf_sk_storage: Fix invalid wait context lockdep report './test_progs -t test_local_storage' reported a splat: [ 27.137569] ============================= [ 27.138122] [ BUG: Invalid wait context ] [ | ||
| CVE-2023-53856 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: of: overlay: Call of_changeset_init() early When of_overlay_fdt_apply() fails, the changeset may be partially applied, and the caller is still expected to call of_overlay_remove() to clean up this partial state | ||
| CVE-2023-53855 | — | < 6.4.0-150700.20.24.1 | 6.4.0-150700.20.24.1 | Dec 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: net: dsa: ocelot: call dsa_tag_8021q_unregister() under rtnl_lock() on driver remove When the tagging protocol in current use is "ocelot-8021q" and we unbind the driver, we see this splat: $ echo '0000:00:00.2 |
- CVE-2025-40343Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: nvmet-fc: avoid scheduling association deletion twice When forcefully shutting down a port via the configfs interface, nvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and then nvmet_disable_por
- CVE-2025-40342Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: nvme-fc: use lock accessing port_state and rport state nvme_fc_unregister_remote removes the remote port on a lport object at any point in time when there is no active association. This races with with the reco
- CVE-2025-40340Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix oops in xe_gem_fault when running core_hotunplug test. I saw an oops in xe_gem_fault when running the xe-fast-feedback testlist against the realtime kernel without debug options enabled. The panic
- CVE-2025-40339Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix nullptr err of vm_handle_moved If a amdgpu_bo_va is fpriv->prt_va, the bo of this one is always NULL. So, such kind of amdgpu_bo_va should be updated separately before amdgpu_vm_handle_moved.
- CVE-2025-40338Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: ASoC: Intel: avs: Do not share the name pointer between components By sharing 'name' directly, tearing down components may lead to use-after-free errors. Duplicate the name to avoid that. At the same time, upd
- CVE-2025-40337Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: net: stmmac: Correctly handle Rx checksum offload errors The stmmac_rx function would previously set skb->ip_summed to CHECKSUM_UNNECESSARY if hardware checksum offload (CoE) was enabled and the packet was of a
- CVE-2025-40332Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix mmap write lock not release If mmap write lock is taken while draining retry fault, mmap write lock is not released because svm_range_restore_pages calls mmap_read_unlock then returns. This caus
- CVE-2025-40331Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: sctp: Prevent TOCTOU out-of-bounds write For the following path not holding the sock lock, sctp_diag_dump() -> sctp_for_each_endpoint() -> sctp_ep_dump() make sure not to exceed bounds in case the address l
- CVE-2025-40330Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Shutdown FW DMA in bnxt_shutdown() The netif_close() call in bnxt_shutdown() only stops packet DMA. There may be FW DMA for trace logging (recently added) that will continue. If we kexec to a new ker
- CVE-2025-40329Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb The Mesa issue referenced below pointed out a possible deadlock: [ 1231.611031] Possible interrupt unsafe locking scenario: [ 1231.611033] CPU0
- CVE-2025-40328Dec 9, 2025affected < 6.4.0-150700.20.27.1fixed 6.4.0-150700.20.27.1
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in smb2_close_cached_fid() find_or_create_cached_dir() could grab a new reference after kref_put() had seen the refcount drop to zero but before cfid_list_lock is acquired in smb2
- CVE-2023-53865Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix warning when putting transaction with qgroups enabled after abort If we have a transaction abort with qgroups enabled we get a warning triggered when doing the final put on the transaction, like this
- CVE-2023-53864Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: drm/mxsfb: Disable overlay plane in mxsfb_plane_overlay_atomic_disable() When disabling overlay plane in mxsfb_plane_overlay_atomic_update(), overlay plane's framebuffer pointer is NULL. So, dereferencing it w
- CVE-2023-53863Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: netlink: do not hard code device address lenth in fdb dumps syzbot reports that some netdev devices do not have a six bytes address [1] Replace ETH_ALEN by dev->addr_len. [1] (Case of a device where dev->addr
- CVE-2023-53861Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: ext4: correct grp validation in ext4_mb_good_group Group corruption check will access memory of grp and will trigger kernel crash if grp is NULL. So do NULL check before corruption check.
- CVE-2023-53860Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: dm: don't attempt to queue IO under RCU protection dm looks up the table for IO based on the request type, with an assumption that if the request is marked REQ_NOWAIT, it's fine to attempt to submit that IO whi
- CVE-2023-53858Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() in case of error If clk_get_rate() fails, the clk that has just been allocated needs to be freed.
- CVE-2023-53857Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: bpf: bpf_sk_storage: Fix invalid wait context lockdep report './test_progs -t test_local_storage' reported a splat: [ 27.137569] ============================= [ 27.138122] [ BUG: Invalid wait context ] [
- CVE-2023-53856Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: of: overlay: Call of_changeset_init() early When of_overlay_fdt_apply() fails, the changeset may be partially applied, and the caller is still expected to call of_overlay_remove() to clean up this partial state
- CVE-2023-53855Dec 9, 2025affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1
In the Linux kernel, the following vulnerability has been resolved: net: dsa: ocelot: call dsa_tag_8021q_unregister() under rtnl_lock() on driver remove When the tagging protocol in current use is "ocelot-8021q" and we unbind the driver, we see this splat: $ echo '0000:00:00.2
Page 20 of 106