rpm package
suse/kernel-syms-rt&distro=SUSE Real Time Module 15 SP6
pkg:rpm/suse/kernel-syms-rt&distro=SUSE%20Real%20Time%20Module%2015%20SP6
Vulnerabilities (3,796)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2024-58017 | Med | 5.5 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: printk: Fix signed integer overflow when defining LOG_BUF_LEN_MAX Shifting 1 << 31 on a 32-bit int causes signed integer overflow, which leads to undefined behavior. To prevent this, cast 1 to u32 before perfor | |
| CVE-2024-58014 | Hig | 7.1 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() In 'wlc_phy_iqcal_gainparams_nphy()', add gain range check to WARN() instead of possible out-of-bounds 'tbl_iqcal_gainparams_nphy' access. | |
| CVE-2024-58013 | Hig | 7.8 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync This fixes the following crash: ================================================================== BUG: KASAN: slab-use-after-free | |
| CVE-2024-58012 | Med | 5.5 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params Each cpu DAI should associate with a widget. However, the topology might not create the right number of DAI widgets for aggregated amps. And i | |
| CVE-2024-58011 | Med | 5.5 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: platform/x86: int3472: Check for adev == NULL Not all devices have an ACPI companion fwnode, so adev might be NULL. This can e.g. (theoretically) happen when a user manually binds one of the int3472 drivers to | |
| CVE-2024-58009 | Med | 5.5 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc A NULL sock pointer is passed into l2cap_sock_alloc() when it is called from l2cap_sock_new_connection_cb() and the error handling paths should als | |
| CVE-2024-58007 | Hig | 7.1 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: soc: qcom: socinfo: Avoid out of bounds read of serial number On MSM8916 devices, the serial number exposed in sysfs is constant and does not change across individual devices. It's always: db410c:/sys/device | |
| CVE-2024-58006 | Cri | 9.6 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar() In commit 4284c88fff0e ("PCI: designware-ep: Allow pci_epc_set_bar() update inbound map address") set_bar() was modified to support dynamically | |
| CVE-2024-58005 | Med | 5.5 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: tpm: Change to kvalloc() in eventlog/acpi.c The following failure was reported on HPE ProLiant D320: [ 10.693310][ T1] tpm_tis STM0925:00: 2.0 TPM (device-id 0x3, rev-id 0) [ 10.848132][ T1] -------- | |
| CVE-2024-58002 | Hig | 7.8 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Remove dangling pointers When an async control is written, we copy a pointer to the file handle that started the operation. That pointer will be used when the device is done. Which could be any | |
| CVE-2024-58001 | Med | 5.5 | < 6.4.0-150600.10.39.1 | 6.4.0-150600.10.39.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: ocfs2: handle a symlink read error correctly Patch series "Convert ocfs2 to use folios". Mark did a conversion of ocfs2 to use folios and sent it to me as a giant patch for review ;-) So I've redone it as ind | |
| CVE-2024-57834 | Med | 5.5 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: media: vidtv: Fix a null-ptr-deref in vidtv_mux_stop_thread syzbot report a null-ptr-deref in vidtv_mux_stop_thread. [1] If dvb->mux is not initialized successfully by vidtv_mux_init() in the vidtv_start_strea | |
| CVE-2024-54458 | Hig | 7.8 | < 6.4.0-150600.10.39.1 | 6.4.0-150600.10.39.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: bsg: Set bsg_queue to NULL after removal Currently, this does not cause any issues, but I believe it is necessary to set bsg_queue to NULL after removing it to prevent potential use-after-free (UAF) | |
| CVE-2024-52559 | Hig | 7.8 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/msm/gem: prevent integer overflow in msm_ioctl_gem_submit() The "submit->cmd[i].size" and "submit->cmd[i].offset" variables are u32 values that come from the user via the submit_lookup_cmds() function. This | |
| CVE-2025-21731 | Hig | 7.8 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: nbd: don't allow reconnect after disconnect Following process can cause nbd_config UAF: 1) grab nbd_config temporarily; 2) nbd_genl_disconnect() flush all recv_work() and release the initial reference: nbd | |
| CVE-2025-21729 | Hig | 7.8 | < 6.4.0-150600.10.39.1 | 6.4.0-150600.10.39.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion The rtwdev->scanning flag isn't protected by mutex originally, so cancel_hw_scan can pass the condition, but suddenly hw_scan completion unset | |
| CVE-2025-21728 | Med | 5.5 | < 6.4.0-150600.10.29.1 | 6.4.0-150600.10.29.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: bpf: Send signals asynchronously if !preemptible BPF programs can execute in all kinds of contexts and when a program running in a non-preemptible context uses the bpf_send_signal() kfunc, it will cause issues | |
| CVE-2025-21727 | Hig | 7.8 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: padata: fix UAF in padata_reorder A bug was found when run ltp test: BUG: KASAN: slab-use-after-free in padata_find_next+0x29/0x1a0 Read of size 4 at addr ffff88bbfe003524 by task kworker/u113:2/3039206 CPU: | |
| CVE-2025-21726 | Hig | 7.8 | < 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: padata: avoid UAF for reorder_work Although the previous patch can avoid ps and ps UAF for _do_serial, it can not avoid potential UAF issue for reorder_work. This issue can happen just as below: crypto_request | |
| CVE-2025-21725 | Hig | 7.5 | < 6.4.0-150600.10.29.1 | 6.4.0-150600.10.29.1 | Feb 27, 2025 | In the Linux kernel, the following vulnerability has been resolved: smb: client: fix oops due to unset link speed It isn't guaranteed that NETWORK_INTERFACE_INFO::LinkSpeed will always be set by the server, so the client must handle any values and then prevent oopses like below |
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: printk: Fix signed integer overflow when defining LOG_BUF_LEN_MAX Shifting 1 << 31 on a 32-bit int causes signed integer overflow, which leads to undefined behavior. To prevent this, cast 1 to u32 before perfor
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() In 'wlc_phy_iqcal_gainparams_nphy()', add gain range check to WARN() instead of possible out-of-bounds 'tbl_iqcal_gainparams_nphy' access.
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync This fixes the following crash: ================================================================== BUG: KASAN: slab-use-after-free
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params Each cpu DAI should associate with a widget. However, the topology might not create the right number of DAI widgets for aggregated amps. And i
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: platform/x86: int3472: Check for adev == NULL Not all devices have an ACPI companion fwnode, so adev might be NULL. This can e.g. (theoretically) happen when a user manually binds one of the int3472 drivers to
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc A NULL sock pointer is passed into l2cap_sock_alloc() when it is called from l2cap_sock_new_connection_cb() and the error handling paths should als
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: soc: qcom: socinfo: Avoid out of bounds read of serial number On MSM8916 devices, the serial number exposed in sysfs is constant and does not change across individual devices. It's always: db410c:/sys/device
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar() In commit 4284c88fff0e ("PCI: designware-ep: Allow pci_epc_set_bar() update inbound map address") set_bar() was modified to support dynamically
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: tpm: Change to kvalloc() in eventlog/acpi.c The following failure was reported on HPE ProLiant D320: [ 10.693310][ T1] tpm_tis STM0925:00: 2.0 TPM (device-id 0x3, rev-id 0) [ 10.848132][ T1] --------
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Remove dangling pointers When an async control is written, we copy a pointer to the file handle that started the operation. That pointer will be used when the device is done. Which could be any
- affected < 6.4.0-150600.10.39.1fixed 6.4.0-150600.10.39.1
In the Linux kernel, the following vulnerability has been resolved: ocfs2: handle a symlink read error correctly Patch series "Convert ocfs2 to use folios". Mark did a conversion of ocfs2 to use folios and sent it to me as a giant patch for review ;-) So I've redone it as ind
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: media: vidtv: Fix a null-ptr-deref in vidtv_mux_stop_thread syzbot report a null-ptr-deref in vidtv_mux_stop_thread. [1] If dvb->mux is not initialized successfully by vidtv_mux_init() in the vidtv_start_strea
- affected < 6.4.0-150600.10.39.1fixed 6.4.0-150600.10.39.1
In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: bsg: Set bsg_queue to NULL after removal Currently, this does not cause any issues, but I believe it is necessary to set bsg_queue to NULL after removing it to prevent potential use-after-free (UAF)
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: drm/msm/gem: prevent integer overflow in msm_ioctl_gem_submit() The "submit->cmd[i].size" and "submit->cmd[i].offset" variables are u32 values that come from the user via the submit_lookup_cmds() function. This
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: nbd: don't allow reconnect after disconnect Following process can cause nbd_config UAF: 1) grab nbd_config temporarily; 2) nbd_genl_disconnect() flush all recv_work() and release the initial reference: nbd
- affected < 6.4.0-150600.10.39.1fixed 6.4.0-150600.10.39.1
In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion The rtwdev->scanning flag isn't protected by mutex originally, so cancel_hw_scan can pass the condition, but suddenly hw_scan completion unset
- affected < 6.4.0-150600.10.29.1fixed 6.4.0-150600.10.29.1
In the Linux kernel, the following vulnerability has been resolved: bpf: Send signals asynchronously if !preemptible BPF programs can execute in all kinds of contexts and when a program running in a non-preemptible context uses the bpf_send_signal() kfunc, it will cause issues
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: padata: fix UAF in padata_reorder A bug was found when run ltp test: BUG: KASAN: slab-use-after-free in padata_find_next+0x29/0x1a0 Read of size 4 at addr ffff88bbfe003524 by task kworker/u113:2/3039206 CPU:
- affected < 6.4.0-150600.10.34.1fixed 6.4.0-150600.10.34.1
In the Linux kernel, the following vulnerability has been resolved: padata: avoid UAF for reorder_work Although the previous patch can avoid ps and ps UAF for _do_serial, it can not avoid potential UAF issue for reorder_work. This issue can happen just as below: crypto_request
- affected < 6.4.0-150600.10.29.1fixed 6.4.0-150600.10.29.1
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix oops due to unset link speed It isn't guaranteed that NETWORK_INTERFACE_INFO::LinkSpeed will always be set by the server, so the client must handle any values and then prevent oopses like below
Page 72 of 190