CVSS: 7.8EPSS: 0%CPEs: 8EXPL: 0CVE-2025-21689 – USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb()
https://notcve.org/view.php?id=CVE-2025-21689
10 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb() This patch addresses a null-ptr-deref in qt2_process_read_urb() due to an incorrect bounds check in the following: if (newport > serial->num_ports) { dev_err(&port->dev, "%s - port change to invalid port: %i\n", __func__, newport); break; } The condition doesn't account for the valid range of the serial->port buffer, which is from 0 to serial->num_ports - 1. When newport is... • https://git.kernel.org/stable/c/f7a33e608d9ae022b7f49307921627e34e9484ed •
CVSS: 7.8EPSS: 0%CPEs: 8EXPL: 0CVE-2025-21687 – vfio/platform: check the bounds of read/write syscalls
https://notcve.org/view.php?id=CVE-2025-21687
10 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: vfio/platform: check the bounds of read/write syscalls count and offset are passed from user space and not checked, only offset is capped to 40 bits, which can be used to read/write out of bounds of the device. In the Linux kernel, the following vulnerability has been resolved: vfio/platform: check the bounds of read/write syscalls count and offset are passed from user space and not checked, only offset is capped to 40 bits, which can be us... • https://git.kernel.org/stable/c/6e3f264560099869f68830cb14b3b3e71e5ac76a •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2024-57950 – drm/amd/display: Initialize denominator defaults to 1
https://notcve.org/view.php?id=CVE-2024-57950
10 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Initialize denominator defaults to 1 [WHAT & HOW] Variables, used as denominators and maybe not assigned to other values, should be initialized to non-zero to avoid DIVIDE_BY_ZERO, as reported by Coverity. (cherry picked from commit e2c4c6c10542ccfe4a0830bb6c9fd5b177b7bbb7) In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Initialize denominator defaults to 1 [WHAT & HOW] Variables, used a... • https://git.kernel.org/stable/c/c9d6afb4f9c338049662d27d169fba7dd60e337d •
CVSS: 7.2EPSS: 0%CPEs: 3EXPL: 0CVE-2025-21684 – gpio: xilinx: Convert gpio_lock to raw spinlock
https://notcve.org/view.php?id=CVE-2025-21684
09 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: gpio: xilinx: Convert gpio_lock to raw spinlock irq_chip functions may be called in raw spinlock context. Therefore, we must also use a raw spinlock for our own internal locking. This fixes the following lockdep splat: [ 5.349336] ============================= [ 5.353349] [ BUG: Invalid wait context ] [ 5.357361] 6.13.0-rc5+ #69 Tainted: G W [ 5.363031] ----------------------------- [ 5.367045] kworker/u17:1/44 is trying to lock: [ 5.371587... • https://git.kernel.org/stable/c/a32c7caea292c4d1e417eae6e5a348d187546acf •
CVSS: 8.5EPSS: 0%CPEs: 3EXPL: 0CVE-2023-52925 – netfilter: nf_tables: don't fail inserts if duplicate has expired
https://notcve.org/view.php?id=CVE-2023-52925
05 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: don't fail inserts if duplicate has expired nftables selftests fail: run-tests.sh testcases/sets/0044interval_overlap_0 Expected: 0-2 . 0-3, got: W: [FAILED] ./testcases/sets/0044interval_overlap_0: got 1 Insertion must ignore duplicate but expired entries. Moreover, there is a strange asymmetry in nft_pipapo_activate: It refetches the current element, whereas the other ->activate callbacks (bitmap, hash, rhash, rbtree... • https://git.kernel.org/stable/c/bd156ce9553dcaf2d6ee2c825d1a5a1718e86524 •
CVSS: 7.1EPSS: 0%CPEs: 7EXPL: 0CVE-2023-52924 – netfilter: nf_tables: don't skip expired elements during walk
https://notcve.org/view.php?id=CVE-2023-52924
05 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: don't skip expired elements during walk There is an asymmetry between commit/abort and preparation phase if the following conditions are met: 1. set is a verdict map ("1.2.3.4 : jump foo") 2. timeouts are enabled In this case, following sequence is problematic: 1. element E in set S refers to chain C 2. userspace requests removal of set S 3. kernel does a set walk to decrement chain->use count for all elements from pre... • https://git.kernel.org/stable/c/9d0982927e79049675cb6c6c04a0ebb3dad5a434 •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2025-21683 – bpf: Fix bpf_sk_select_reuseport() memory leak
https://notcve.org/view.php?id=CVE-2025-21683
31 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: bpf: Fix bpf_sk_select_reuseport() memory leak As pointed out in the original comment, lookup in sockmap can return a TCP ESTABLISHED socket. Such TCP socket may have had SO_ATTACH_REUSEPORT_EBPF set before it was ESTABLISHED. In other words, a non-NULL sk_reuseport_cb does not imply a non-refcounted socket. Drop sk's reference in both error paths. unreferenced object 0xffff888101911800 (size 2048): comm "test_progs", pid 44109, jiffies 429... • https://git.kernel.org/stable/c/64d85290d79c0677edb5a8ee2295b36c022fa5df •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2025-21682 – eth: bnxt: always recalculate features after XDP clearing, fix null-deref
https://notcve.org/view.php?id=CVE-2025-21682
31 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: eth: bnxt: always recalculate features after XDP clearing, fix null-deref Recalculate features when XDP is detached. Before: # ip li set dev eth0 xdp obj xdp_dummy.bpf.o sec xdp # ip li set dev eth0 xdp off # ethtool -k eth0 | grep gro rx-gro-hw: off [requested on] After: # ip li set dev eth0 xdp obj xdp_dummy.bpf.o sec xdp # ip li set dev eth0 xdp off # ethtool -k eth0 | grep gro rx-gro-hw: on The fact that HW-GRO doesn't get re-enabled au... • https://git.kernel.org/stable/c/1054aee82321483dceabbb9b9e5d6512e8fe684b •
CVSS: 7.8EPSS: 0%CPEs: 5EXPL: 0CVE-2025-21680 – pktgen: Avoid out-of-bounds access in get_imix_entries
https://notcve.org/view.php?id=CVE-2025-21680
31 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: pktgen: Avoid out-of-bounds access in get_imix_entries Passing a sufficient amount of imix entries leads to invalid access to the pkt_dev->imix_entries array because of the incorrect boundary check. UBSAN: array-index-out-of-bounds in net/core/pktgen.c:874:24 index 20 is out of range for type 'imix_pkt [20]' CPU: 2 PID: 1210 Comm: bash Not tainted 6.10.0-rc1 #121 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Call Trace:
CVSS: 7.8EPSS: 0%CPEs: 7EXPL: 0CVE-2025-21678 – gtp: Destroy device along with udp socket's netns dismantle.
https://notcve.org/view.php?id=CVE-2025-21678
31 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: gtp: Destroy device along with udp socket's netns dismantle. gtp_newlink() links the device to a list in dev_net(dev) instead of src_net, where a udp tunnel socket is created. Even when src_net is removed, the device stays alive on dev_net(dev). Then, removing src_net triggers the splat below. [0] In this example, gtp0 is created in ns2, and the udp socket is created in ns1. ip netns add ns1 ip netns add ns2 ip -n ns1 link add netns ns2 nam... • https://git.kernel.org/stable/c/459aa660eb1d8ce67080da1983bb81d716aa5a69 •