Page 47 of 6517 results (0.006 seconds)

CVSS: -EPSS: 0%CPEs: 6EXPL: 0

24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix GID entry ref leak when create_ah fails If AH create request fails, release sgid_attr to avoid GID entry referrence leak reported while releasing GID table The SUSE Linux Enterprise 15 SP5 RT kernel was updated to fix various security issues. • https://git.kernel.org/stable/c/1a1f460ff151710289c2f8d4badd8b603b87d610 •

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

24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: staging: r8712: Fix memory leak in _r8712_init_xmit_priv() In the above mentioned routine, memory is allocated in several places. If the first succeeds and a later one fails, the routine will leak memory. This patch fixes commit 2865d42c78a9 ("staging: r8712u: Add the new driver to the mainline kernel"). A potential memory leak in r8712_xmit_resource_alloc() is also addressed. The SUSE Linux Enterprise 15 SP5 RT kernel was updated to fix va... • https://git.kernel.org/stable/c/2865d42c78a9121caad52cb02d1fbb7f5cdbc4ef •

CVSS: -EPSS: 0%CPEs: 8EXPL: 0

24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: hwrng: virtio - Fix race on data_avail and actual data The virtio rng device kicks off a new entropy request whenever the data available reaches zero. When a new request occurs at the end of a read operation, that is, when the result of that request is only needed by the next reader, then there is a race between the writing of the new data and the next reader. This is because there is no synchronisation whatsoever between the writer and the... • https://git.kernel.org/stable/c/f7f510ec195781c857ab76366a3e1c59e1caae42 •

CVSS: -EPSS: 0%CPEs: 6EXPL: 0

24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: net: ipv4: fix one memleak in __inet_del_ifa() I got the below warning when do fuzzing test: unregister_netdevice: waiting for bond0 to become free. Usage count = 2 It can be repoduced via: ip link add bond0 type bond sysctl -w net.ipv4.conf.bond0.promote_secondaries=1 ip addr add 4.117.174.103/0 scope 0x40 dev bond0 ip addr add 192.168.100.111/255.255.255.254 scope 0 dev bond0 ip addr add 0.0.0.4/0 scope 0x40 secondary dev bond0 ip addr de... • https://git.kernel.org/stable/c/0ff60a45678e67b2547256a636fd00c1667ce4fa •

CVSS: -EPSS: 0%CPEs: 6EXPL: 0

24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: ionic: remove WARN_ON to prevent panic_on_warn Remove unnecessary early code development check and the WARN_ON that it uses. The irq alloc and free paths have long been cleaned up and this check shouldn't have stuck around so long. The SUSE Linux Enterprise 15 SP6 kernel was updated to fix various security issues. • https://git.kernel.org/stable/c/77ceb68e29ccd25d923b6af59e74ecaf736cc4b7 •

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

24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: ocb: don't leave if not joined If there's no OCB state, don't ask the driver/mac80211 to leave, since that's just confusing. Since set/clear the chandef state, that's a simple check. The SUSE Linux Enterprise 15 SP6 kernel was updated to fix various security issues. • https://git.kernel.org/stable/c/6e0bd6c35b021dc73a81ebd1ef79761233c48b50 •

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

24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: Disallow unallocated resources to be returned In the event that the topology requests resources that have not been created by the system (because they are typically not represented in dpu_mdss_cfg ^1), the resource(s) in global_state (in this case DSC blocks, until their allocation/assignment is being sanity-checked in "drm/msm/dpu: Reject topologies for which no DSC blocks are available") remain NULL but will still be returned... • https://git.kernel.org/stable/c/bb00a452d6f77391441ef7df48f7115dd459cd2f •

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

24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: arm64: mm: fix VA-range sanity check Both create_mapping_noalloc() and update_mapping_prot() sanity-check their 'virt' parameter, but the check itself doesn't make much sense. The condition used today appears to be a historical accident. The sanity-check condition: if ((virt >= PAGE_END) && (virt < VMALLOC_START)) { [ ... warning here ... ] return; } ... can only be true for the KASAN shadow region or the module region, and there's no reaso... • https://git.kernel.org/stable/c/14c127c957c1c6070647c171e72f06e0db275ebf •

CVSS: -EPSS: 0%CPEs: 6EXPL: 0

24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: mips: bmips: BCM6358: disable RAC flush for TP1 RAC flush causes kernel panics on BCM6358 with EHCI/OHCI when booting from TP1: [ 3.881739] usb 1-1: new high-speed USB device number 2 using ehci-platform [ 3.895011] Reserved instruction in kernel code[#1]: [ 3.900113] CPU: 0 PID: 1 Comm: init Not tainted 5.10.16 #0 [ 3.905829] $ 0 : 00000000 10008700 00000000 77d94060 [ 3.911238] $ 4 : 7fd1f088 00000000 81431cac 81431ca0 [ 3.916641] $ 8 : 0... • https://git.kernel.org/stable/c/d59098a0e9cb3c7767090e935c909b37a30629ab •

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

24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: ceph: fix potential use-after-free bug when trimming caps When trimming the caps and just after the 'session->s_cap_lock' is released in ceph_iterate_session_caps() the cap maybe removed by another thread, and when using the stale cap memory in the callbacks it will trigger use-after-free crash. We need to check the existence of the cap just after the 'ci->i_ceph_lock' being acquired. And do nothing if it's already removed. • https://git.kernel.org/stable/c/2f2dc053404febedc9c273452d9d518fb31fde72 •