Page 4 of 7120 results (0.008 seconds)

CVSS: 9.8EPSS: 0%CPEs: 3EXPL: 0

06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - do not transfer req when tegra init fails The tegra_cmac_init or tegra_sha_init function may return an error when memory is exhausted. It should not transfer the request when they return an error. In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - do not transfer req when tegra init fails The tegra_cmac_init or tegra_sha_init function may return an error when memory is exhausted. It should no... • https://git.kernel.org/stable/c/0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 •

CVSS: 9.8EPSS: 0%CPEs: 2EXPL: 0

06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/i915: Grab intel_display from the encoder to avoid potential oopsies Grab the intel_display from 'encoder' rather than 'state' in the encoder hooks to avoid the massive footgun that is intel_sanitize_encoder(), which passes NULL as the 'state' argument to encoder .disable() and .post_disable(). TODO: figure out how to actually fix intel_sanitize_encoder()... In the Linux kernel, the following vulnerability has been resolved: drm/i915: G... • https://git.kernel.org/stable/c/ab0b0eb5c85c5961913bdb9b8011cc8f5c14978a •

CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0

06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: check dpu_plane_atomic_print_state() for valid sspp Similar to the r_pipe sspp protect, add a check to protect the pipe state prints to avoid NULL ptr dereference for cases when the state is dumped without a corresponding atomic_check() where the pipe->sspp is assigned. Patchwork: https://patchwork.freedesktop.org/patch/628404/ In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: check dpu_plane_atom... • https://git.kernel.org/stable/c/31f7148fd3704e0981b4eb6c6d13cf584da606c4 •

CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0

06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: rtlwifi: remove unused check_buddy_priv Commit 2461c7d60f9f ("rtlwifi: Update header file") introduced a global list of private data structures. Later on, commit 26634c4b1868 ("rtlwifi Modify existing bits to match vendor version 2013.02.07") started adding the private data to that list at probe time and added a hook, check_buddy_priv to find the private data from a similar device. However, that function was never used. Besides, thoug... • https://git.kernel.org/stable/c/26634c4b1868323f49f8cd24c3493b57819867fd •

CVSS: 4.9EPSS: 0%CPEs: 5EXPL: 0

06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: team: prevent adding a device which is already a team device lower Prevent adding a device which is already a team device lower, e.g. adding veth0 if vlan1 was already added and veth0 is a lower of vlan1. This is not useful in practice and can lead to recursive locking: $ ip link add veth0 type veth peer name veth1 $ ip link set veth0 up $ ip link set veth1 up $ ip link add link veth0 name veth0.1 type vlan protocol 802.1Q id 1 $ ip link ad... • https://git.kernel.org/stable/c/3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 •

CVSS: 9.8EPSS: 0%CPEs: 4EXPL: 0

06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: bpf: bpf_local_storage: Always use bpf_mem_alloc in PREEMPT_RT In PREEMPT_RT, kmalloc(GFP_ATOMIC) is still not safe in non preemptible context. bpf_mem_alloc must be used in PREEMPT_RT. This patch is to enforce bpf_mem_alloc in the bpf_local_storage when CONFIG_PREEMPT_RT is enabled. [ 35.118559] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 [ 35.118566] in_atomic(): 1, irqs_disabled(): 0, non_block: ... • https://git.kernel.org/stable/c/08a7ce384e33e53e0732c500a8af67a73f8fceca •

CVSS: 9.8EPSS: 0%CPEs: 5EXPL: 0

06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read The nvmem interface supports variable buffer sizes, while the regmap interface operates with fixed-size storage. If an nvmem client uses a buffer size less than 4 bytes, regmap_read will write out of bounds as it expects the buffer to point at an unsigned int. Fix this by using an intermediary unsigned int to hold the value. In the Linux kernel, the following vulnerability has be... • https://git.kernel.org/stable/c/fadfd092ee9138825d8c2a4f95719d2e2e3202b9 •

CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0

06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: OPP: fix dev_pm_opp_find_bw_*() when bandwidth table not initialized If a driver calls dev_pm_opp_find_bw_ceil/floor() the retrieve bandwidth from the OPP table but the bandwidth table was not created because the interconnect properties were missing in the OPP consumer node, the kernel will crash with: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000004 ... pc : _read_bw+0x8/0x10 lr : _opp_table_find_key+0x9... • https://git.kernel.org/stable/c/add1dc094a7456d3c56782b7478940b6a550c7ed •

CVSS: 7.8EPSS: 0%CPEs: 2EXPL: 0

06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: clk: mmp: pxa1908-mpmu: Fix a NULL vs IS_ERR() check The devm_kzalloc() function returns NULL on error, not error pointers. Update the check to match. In the Linux kernel, the following vulnerability has been resolved: clk: mmp: pxa1908-mpmu: Fix a NULL vs IS_ERR() check The devm_kzalloc() function returns NULL on error, not error pointers. Update the check to match. • https://git.kernel.org/stable/c/ebac87cdd230685fc5245a61bde79c9100ac348a •

CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0

06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: clk: mmp: pxa1908-apbcp: Fix a NULL vs IS_ERR() check The devm_kzalloc() function doesn't return error pointers, it returns NULL on error. Update the check to match. In the Linux kernel, the following vulnerability has been resolved: clk: mmp: pxa1908-apbcp: Fix a NULL vs IS_ERR() check The devm_kzalloc() function doesn't return error pointers, it returns NULL on error. Update the check to match. • https://git.kernel.org/stable/c/a89233dbd4df521094caa0dbcd03338259f8ead6 •