rpm package
suse/kernel-source-rt&distro=SUSE Linux Enterprise Micro 5.5
pkg:rpm/suse/kernel-source-rt&distro=SUSE%20Linux%20Enterprise%20Micro%205.5
Vulnerabilities (4,559)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2024-46841 | — | < 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: btrfs: don't BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc() We handle errors here properly, ENOMEM isn't fatal, return the error. | ||
| CVE-2024-46840 | — | < 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: btrfs: clean up our handling of refs == 0 in snapshot delete In reada we BUG_ON(refs == 0), which could be unkind since we aren't holding a lock on the extent leaf and thus could get a transient incorrect answe | ||
| CVE-2024-46835 | — | < 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix smatch static checker warning adev->gfx.imu.funcs could be NULL | ||
| CVE-2024-46834 | — | < 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: ethtool: fail closed if we can't get max channel used in indirection tables Commit 0d1b7d6c9274 ("bnxt: fix crashes when reducing ring count with active RSS contexts") proves that allowing indirection table to | ||
| CVE-2024-46828 | — | < 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: sched: sch_cake: fix bulk flow accounting logic for host fairness In sch_cake, we keep track of the count of active bulk flows per host, when running in dst/src host fairness mode, which is used as the round-ro | ||
| CVE-2024-46826 | — | < 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: ELF: fix kernel.randomize_va_space double read ELF loader uses "randomize_va_space" twice. It is sysctl and can change at any moment, so 2 loads could see 2 different values in theory with unpredictable consequ | ||
| CVE-2024-46822 | — | < 5.14.21-150500.13.73.1 | 5.14.21-150500.13.73.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry In a review discussion of the changes to support vCPU hotplug where a check was added on the GICC being enabled if was online, it was noted th | ||
| CVE-2024-46819 | — | < 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: the warning dereferencing obj for nbio_v7_4 if ras_manager obj null, don't print NBIO err data | ||
| CVE-2024-46818 | — | < 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check gpio_id before used as array index [WHY & HOW] GPIO_ID_UNKNOWN (-1) is not a valid value for array index and therefore should be checked in advance. This fixes 5 OVERRUN issues reported | ||
| CVE-2024-46817 | — | < 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 [Why] Coverity reports OVERRUN warning. Should abort amdgpu_dm initialize. [How] Return failure to amdgpu_dm_init. | ||
| CVE-2024-46816 | — | < 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links [Why] Coverity report OVERRUN warning. There are only max_links elements within dc->links. link count could up to AMDGPU_DM_MAX_D | ||
| CVE-2024-46815 | — | < 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] [WHY & HOW] num_valid_sets needs to be checked to avoid a negative index when accessing reader_wm_sets[num_valid_sets - 1]. This fixes an | ||
| CVE-2024-46814 | — | < 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check msg_id before processing transcation [WHY & HOW] HDCP_MESSAGE_ID_INVALID (-1) is not a valid msg_id nor is it a valid array index, and it needs checking before used. This fixes 4 OVERRUN | ||
| CVE-2024-46811 | — | < 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box [Why] Coverity reports OVERRUN warning. soc.num_states could be 40. But array range of bw_params->clk_table.entries is 8. [Ho | ||
| CVE-2024-46810 | — | < 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ Make sure the connector is fully initialized before signalling any HPD events via drm_kms_helper_hotplug_event(), otherwise t | ||
| CVE-2024-46809 | — | < 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check BIOS images before it is used BIOS images may fail to load and null checks are added before they are used. This fixes 6 NULL_RETURNS issues reported by Coverity. | ||
| CVE-2024-46807 | — | < 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/amdgpu: Check tbo resource pointer Validate tbo resource pointer, skip if NULL | ||
| CVE-2024-46805 | — | < 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix the waring dereferencing hive Check the amdgpu_hive_info *hive that maybe is NULL. | ||
| CVE-2024-46804 | — | < 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add array index check for hdcp ddc access [Why] Coverity reports OVERRUN warning. Do not check if array index valid. [How] Check msg_id valid and valid array index. | ||
| CVE-2024-46802 | — | < 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: added NULL check at start of dc_validate_stream [Why] prevent invalid memory access [How] check if dc and stream are NULL |
- CVE-2024-46841Sep 27, 2024affected < 5.14.21-150500.13.76.1fixed 5.14.21-150500.13.76.1
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc() We handle errors here properly, ENOMEM isn't fatal, return the error.
- CVE-2024-46840Sep 27, 2024affected < 5.14.21-150500.13.76.1fixed 5.14.21-150500.13.76.1
In the Linux kernel, the following vulnerability has been resolved: btrfs: clean up our handling of refs == 0 in snapshot delete In reada we BUG_ON(refs == 0), which could be unkind since we aren't holding a lock on the extent leaf and thus could get a transient incorrect answe
- CVE-2024-46835Sep 27, 2024affected < 5.14.21-150500.13.79.1fixed 5.14.21-150500.13.79.1
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix smatch static checker warning adev->gfx.imu.funcs could be NULL
- CVE-2024-46834Sep 27, 2024affected < 5.14.21-150500.13.76.1fixed 5.14.21-150500.13.76.1
In the Linux kernel, the following vulnerability has been resolved: ethtool: fail closed if we can't get max channel used in indirection tables Commit 0d1b7d6c9274 ("bnxt: fix crashes when reducing ring count with active RSS contexts") proves that allowing indirection table to
- CVE-2024-46828Sep 27, 2024affected < 5.14.21-150500.13.76.1fixed 5.14.21-150500.13.76.1
In the Linux kernel, the following vulnerability has been resolved: sched: sch_cake: fix bulk flow accounting logic for host fairness In sch_cake, we keep track of the count of active bulk flows per host, when running in dst/src host fairness mode, which is used as the round-ro
- CVE-2024-46826Sep 27, 2024affected < 5.14.21-150500.13.76.1fixed 5.14.21-150500.13.76.1
In the Linux kernel, the following vulnerability has been resolved: ELF: fix kernel.randomize_va_space double read ELF loader uses "randomize_va_space" twice. It is sysctl and can change at any moment, so 2 loads could see 2 different values in theory with unpredictable consequ
- CVE-2024-46822Sep 27, 2024affected < 5.14.21-150500.13.73.1fixed 5.14.21-150500.13.73.1
In the Linux kernel, the following vulnerability has been resolved: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry In a review discussion of the changes to support vCPU hotplug where a check was added on the GICC being enabled if was online, it was noted th
- CVE-2024-46819Sep 27, 2024affected < 5.14.21-150500.13.79.1fixed 5.14.21-150500.13.79.1
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: the warning dereferencing obj for nbio_v7_4 if ras_manager obj null, don't print NBIO err data
- CVE-2024-46818Sep 27, 2024affected < 5.14.21-150500.13.76.1fixed 5.14.21-150500.13.76.1
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check gpio_id before used as array index [WHY & HOW] GPIO_ID_UNKNOWN (-1) is not a valid value for array index and therefore should be checked in advance. This fixes 5 OVERRUN issues reported
- CVE-2024-46817Sep 27, 2024affected < 5.14.21-150500.13.76.1fixed 5.14.21-150500.13.76.1
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 [Why] Coverity reports OVERRUN warning. Should abort amdgpu_dm initialize. [How] Return failure to amdgpu_dm_init.
- CVE-2024-46816Sep 27, 2024affected < 5.14.21-150500.13.76.1fixed 5.14.21-150500.13.76.1
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links [Why] Coverity report OVERRUN warning. There are only max_links elements within dc->links. link count could up to AMDGPU_DM_MAX_D
- CVE-2024-46815Sep 27, 2024affected < 5.14.21-150500.13.76.1fixed 5.14.21-150500.13.76.1
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] [WHY & HOW] num_valid_sets needs to be checked to avoid a negative index when accessing reader_wm_sets[num_valid_sets - 1]. This fixes an
- CVE-2024-46814Sep 27, 2024affected < 5.14.21-150500.13.76.1fixed 5.14.21-150500.13.76.1
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check msg_id before processing transcation [WHY & HOW] HDCP_MESSAGE_ID_INVALID (-1) is not a valid msg_id nor is it a valid array index, and it needs checking before used. This fixes 4 OVERRUN
- CVE-2024-46811Sep 27, 2024affected < 5.14.21-150500.13.76.1fixed 5.14.21-150500.13.76.1
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box [Why] Coverity reports OVERRUN warning. soc.num_states could be 40. But array range of bw_params->clk_table.entries is 8. [Ho
- CVE-2024-46810Sep 27, 2024affected < 5.14.21-150500.13.79.1fixed 5.14.21-150500.13.79.1
In the Linux kernel, the following vulnerability has been resolved: drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ Make sure the connector is fully initialized before signalling any HPD events via drm_kms_helper_hotplug_event(), otherwise t
- CVE-2024-46809Sep 27, 2024affected < 5.14.21-150500.13.76.1fixed 5.14.21-150500.13.76.1
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check BIOS images before it is used BIOS images may fail to load and null checks are added before they are used. This fixes 6 NULL_RETURNS issues reported by Coverity.
- CVE-2024-46807Sep 27, 2024affected < 5.14.21-150500.13.79.1fixed 5.14.21-150500.13.79.1
In the Linux kernel, the following vulnerability has been resolved: drm/amd/amdgpu: Check tbo resource pointer Validate tbo resource pointer, skip if NULL
- CVE-2024-46805Sep 27, 2024affected < 5.14.21-150500.13.79.1fixed 5.14.21-150500.13.79.1
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix the waring dereferencing hive Check the amdgpu_hive_info *hive that maybe is NULL.
- CVE-2024-46804Sep 27, 2024affected < 5.14.21-150500.13.79.1fixed 5.14.21-150500.13.79.1
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add array index check for hdcp ddc access [Why] Coverity reports OVERRUN warning. Do not check if array index valid. [How] Check msg_id valid and valid array index.
- CVE-2024-46802Sep 27, 2024affected < 5.14.21-150500.13.79.1fixed 5.14.21-150500.13.79.1
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: added NULL check at start of dc_validate_stream [Why] prevent invalid memory access [How] check if dc and stream are NULL
Page 130 of 228