https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 12:09:30 +0000 https://cve.radiocsirt.org/vuln/alsa-2024:3618 <p><strong>Affected:</strong> AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 more</p> <p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p> <p>Security Fix(es):</p> <p>* kernel: Marvin vulnerability side-channel leakage in the RSA decryption operation (CVE-2023-6240) * kernel: Information disclosure in vhost/vhost.c:vhost_new_msg() (CVE-2024-0340) * kernel: untrusted VMM can trigger int80 syscall handling (CVE-2024-25744) * kernel: i2c: i801: Fix block process call transactions (CVE-2024-26593) * kernel: pvrusb2: fix use after free on context disconnection (CVE-2023-52445) * kernel: x86/fpu: Stop relying on userspace for info to fault in xsave buffer that cause loop forever (CVE-2024-26603) * kernel: use after free in i2c (CVE-2019-25162) * kernel: i2c: validate user data in compat ioctl (CVE-2021-46934) * kernel: media: dvbdev: Fix memory leak in dvb_media_device_free() (CVE-2020-36777) * kernel: usb: hub: Guard against accesses to uninitialized BOS descriptors (CVE-2023-52477) * kernel: mtd: require write permissions for locking and badblock ioctls (CVE-2021-47055) * kernel: net/smc: fix illegal rmb_desc access in SMC-D connection dump (CVE-2024-26615) * kernel: vt: fix memory overlapping when deleting chars in the buffer (CVE-2022-48627) * kernel: Integer Overflow in raid5_cache_count (CVE-2024-23307) * kernel: media: uvcvideo: out-of-bounds read in uvc_query_v4l2_menu() (CVE-2023-52565) * kernel: net: bridge: data races indata-races in br_handle_frame_finish() (CVE-2023-52578) * kernel: net: usb: smsc75xx: Fix uninit-value access i…</p> <p><strong>Affected:</strong> AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 more</p> <p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p> <p>Security Fix(es):</p> <p>* kernel: Marvin vulnerability side-channel leakage in the RSA decryption operation (CVE-2023-6240) * kernel: Information disclosure in vhost/vhost.c:vhost_new_msg() (CVE-2024-0340) * kernel: untrusted VMM can trigger int80 syscall handling (CVE-2024-25744) * kernel: i2c: i801: Fix block process call transactions (CVE-2024-26593) * kernel: pvrusb2: fix use after free on context disconnection (CVE-2023-52445) * kernel: x86/fpu: Stop relying on userspace for info to fault in xsave buffer that cause loop forever (CVE-2024-26603) * kernel: use after free in i2c (CVE-2019-25162) * kernel: i2c: validate user data in compat ioctl (CVE-2021-46934) * kernel: media: dvbdev: Fix memory leak in dvb_media_device_free() (CVE-2020-36777) * kernel: usb: hub: Guard against accesses to uninitialized BOS descriptors (CVE-2023-52477) * kernel: mtd: require write permissions for locking and badblock ioctls (CVE-2021-47055) * kernel: net/smc: fix illegal rmb_desc access in SMC-D connection dump (CVE-2024-26615) * kernel: vt: fix memory overlapping when deleting chars in the buffer (CVE-2022-48627) * kernel: Integer Overflow in raid5_cache_count (CVE-2024-23307) * kernel: media: uvcvideo: out-of-bounds read in uvc_query_v4l2_menu() (CVE-2023-52565) * kernel: net: bridge: data races indata-races in br_handle_frame_finish() (CVE-2023-52578) * kernel: net: usb: smsc75xx: Fix uninit-value access i…</p> https://cve.radiocsirt.org/vuln/alsa-2024:3618 https://cve.radiocsirt.org/vuln/bdu:2024-04581 bdu:2024-04581 https://cve.radiocsirt.org/vuln/bdu:2024-04581 https://cve.radiocsirt.org/vuln/bell-cve-2024-26934 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2024-26934 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0381 certfr-2024-avi-0381 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0381 https://cve.radiocsirt.org/vuln/euvd-2026-316944 EUVD-2026-316944 https://cve.radiocsirt.org/vuln/euvd-2026-316944 https://cve.radiocsirt.org/vuln/fkie_cve-2024-26934 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>USB: core: Fix deadlock in usb_deauthorize_interface()</p> <p>Among the attribute file callback routines in drivers/usb/core/sysfs.c, the interface_authorized_store() function is the only one which acquires a device lock on an ancestor device: It calls usb_deauthorize_interface(), which locks the interface&#39;s parent USB device.</p> <p>The will lead to deadlock if another process already owns that lock and tries to remove the interface, whether through a configuration change or because the device has been disconnected. As part of the removal procedure, device_del() waits for all ongoing sysfs attribute callbacks to complete. But usb_deauthorize_interface() can&#39;t complete until the device lock has been released, and the lock won&#39;t be released until the removal has finished.</p> <p>The mechanism provided by sysfs to prevent this kind of deadlock is to use the sysfs_break_active_protection() function, which tells sysfs not to wait for the attribute callback.</p> <p>Reported-and-tested by: Yue Sun &lt;samsun1006219@gmail.com&gt; Reported by: xingwei lee &lt;xrivendell7@gmail.com&gt;</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>USB: core: Fix deadlock in usb_deauthorize_interface()</p> <p>Among the attribute file callback routines in drivers/usb/core/sysfs.c, the interface_authorized_store() function is the only one which acquires a device lock on an ancestor device: It calls usb_deauthorize_interface(), which locks the interface&#39;s parent USB device.</p> <p>The will lead to deadlock if another process already owns that lock and tries to remove the interface, whether through a configuration change or because the device has been disconnected. As part of the removal procedure, device_del() waits for all ongoing sysfs attribute callbacks to complete. But usb_deauthorize_interface() can&#39;t complete until the device lock has been released, and the lock won&#39;t be released until the removal has finished.</p> <p>The mechanism provided by sysfs to prevent this kind of deadlock is to use the sysfs_break_active_protection() function, which tells sysfs not to wait for the attribute callback.</p> <p>Reported-and-tested by: Yue Sun &lt;samsun1006219@gmail.com&gt; Reported by: xingwei lee &lt;xrivendell7@gmail.com&gt;</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-26934 https://cve.radiocsirt.org/vuln/ghsa-6wq5-2j9j-6rvr <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>USB: core: Fix deadlock in usb_deauthorize_interface()</p> <p>Among the attribute file callback routines in drivers/usb/core/sysfs.c, the interface_authorized_store() function is the only one which acquires a device lock on an ancestor device: It calls usb_deauthorize_interface(), which locks the interface&#39;s parent USB device.</p> <p>The will lead to deadlock if another process already owns that lock and tries to remove the interface, whether through a configuration change or because the device has been disconnected. As part of the removal procedure, device_del() waits for all ongoing sysfs attribute callbacks to complete. But usb_deauthorize_interface() can&#39;t complete until the device lock has been released, and the lock won&#39;t be released until the removal has finished.</p> <p>The mechanism provided by sysfs to prevent this kind of deadlock is to use the sysfs_break_active_protection() function, which tells sysfs not to wait for the attribute callback.</p> <p>Reported-and-tested by: Yue Sun &lt;samsun1006219@gmail.com&gt; Reported by: xingwei lee &lt;xrivendell7@gmail.com&gt;</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>USB: core: Fix deadlock in usb_deauthorize_interface()</p> <p>Among the attribute file callback routines in drivers/usb/core/sysfs.c, the interface_authorized_store() function is the only one which acquires a device lock on an ancestor device: It calls usb_deauthorize_interface(), which locks the interface&#39;s parent USB device.</p> <p>The will lead to deadlock if another process already owns that lock and tries to remove the interface, whether through a configuration change or because the device has been disconnected. As part of the removal procedure, device_del() waits for all ongoing sysfs attribute callbacks to complete. But usb_deauthorize_interface() can&#39;t complete until the device lock has been released, and the lock won&#39;t be released until the removal has finished.</p> <p>The mechanism provided by sysfs to prevent this kind of deadlock is to use the sysfs_break_active_protection() function, which tells sysfs not to wait for the attribute callback.</p> <p>Reported-and-tested by: Yue Sun &lt;samsun1006219@gmail.com&gt; Reported by: xingwei lee &lt;xrivendell7@gmail.com&gt;</p> https://cve.radiocsirt.org/vuln/ghsa-6wq5-2j9j-6rvr https://cve.radiocsirt.org/vuln/gsd-2024-26934 gsd-2024-26934 https://cve.radiocsirt.org/vuln/gsd-2024-26934 https://cve.radiocsirt.org/vuln/icsa-24-102-01 <p>An out-of-bounds (OOB) memory write flaw was found in the NFSD in the Linux kernel. Missing sanity may lead to a write beyond bmval[bmlen-1] in nfsd4_decode_bitmap4 in fs/nfsd/nfs4xdr.c. In this flaw, a local attacker with user privilege may gain access to out-of-bounds memory, leading to a system integrity and confidentiality threat. fs/nfsd/trace.h in the Linux kernel before 5.13.4 might allow remote attackers to cause a denial of service (out-of-bounds read in strlen) by sending NFS traffic when the trace event framework is being used for nfsd. SUNRPC: null pointer dereference in svc_rqst_free(). When alloc_pages_node() returns null in svc_rqst_alloc(), the null rq_scratch_page pointer will be dereferenced when calling put_page() in svc_rqst_free(). NFSD: READDIR buffer overflow. If a client sends a READDIR count argument that is too small (say, zero), then the buffer size calculation in the new init_dirlist helper functions results in an underflow, allowing the XDR stream functions to write beyond the actual buffer. This calculation has always been suspect. NFSD has never sanity- checked the READDIR count argument, but the old entry encoders managed the problem correctly. With the commits below, entry encoding changed, exposing the underflow to the pointer arithmetic in xdr_reserve_space(). Modern NFS clients attempt to retrieve as much data as possible for each READDIR request. nfsd: NULL dereference in nfs3svc_encode_getaclres. A NULL pointer dereference vulnerability…</p> <p>An out-of-bounds (OOB) memory write flaw was found in the NFSD in the Linux kernel. Missing sanity may lead to a write beyond bmval[bmlen-1] in nfsd4_decode_bitmap4 in fs/nfsd/nfs4xdr.c. In this flaw, a local attacker with user privilege may gain access to out-of-bounds memory, leading to a system integrity and confidentiality threat. fs/nfsd/trace.h in the Linux kernel before 5.13.4 might allow remote attackers to cause a denial of service (out-of-bounds read in strlen) by sending NFS traffic when the trace event framework is being used for nfsd. SUNRPC: null pointer dereference in svc_rqst_free(). When alloc_pages_node() returns null in svc_rqst_alloc(), the null rq_scratch_page pointer will be dereferenced when calling put_page() in svc_rqst_free(). NFSD: READDIR buffer overflow. If a client sends a READDIR count argument that is too small (say, zero), then the buffer size calculation in the new init_dirlist helper functions results in an underflow, allowing the XDR stream functions to write beyond the actual buffer. This calculation has always been suspect. NFSD has never sanity- checked the READDIR count argument, but the old entry encoders managed the problem correctly. With the commits below, entry encoding changed, exposing the underflow to the pointer arithmetic in xdr_reserve_space(). Modern NFS clients attempt to retrieve as much data as possible for each READDIR request. nfsd: NULL dereference in nfs3svc_encode_getaclres. A NULL pointer dereference vulnerability…</p> https://cve.radiocsirt.org/vuln/icsa-24-102-01 https://cve.radiocsirt.org/vuln/msrc_cve-2024-26934 msrc_CVE-2024-26934 https://cve.radiocsirt.org/vuln/msrc_cve-2024-26934 https://cve.radiocsirt.org/vuln/oesa-2024-1692 <p><strong>Affected:</strong> openEuler:20.03-LTS-SP4: kernel</p> <p>The Linux Kernel, the operating system core itself. Security Fix(es): In the Linux kernel, the following vulnerability has been resolved: net: usb: fix possible use-after-free in smsc75xx_bind The commit 46a8b29c6306 (&amp;quot;net: usb: fix memory leak in smsc75xx_bind&amp;quot;) fails to clean up the work scheduled in smsc75xx_reset-&amp;gt; smsc75xx_set_multicast, which leads to use-after-free if the work is scheduled to start after the deallocation. In addition, this patch also removes a dangling pointer - dev-&amp;gt;data[0]. This patch calls cancel_work_sync to cancel the scheduled work and set the dangling pointer to NULL.(CVE-2021-47239) In the Linux kernel, the following vulnerability has been resolved: RDMA: Verify port when creating flow rule Validate port value provided by the user and with that remove no longer needed validation by the driver. The missing check in the mlx5_ib driver could cause to the below oops. Call trace: _create_flow_rule+0x2d4/0xf28 [mlx5_ib] mlx5_ib_create_flow+0x2d0/0x5b0 [mlx5_ib] ib_uverbs_ex_create_flow+0x4cc/0x624 [ib_uverbs] ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0xd4/0x150 [ib_uverbs] ib_uverbs_cmd_verbs.isra.7+0xb28/0xc50 [ib_uverbs] ib_uverbs_ioctl+0x158/0x1d0 [ib_uverbs] do_vfs_ioctl+0xd0/0xaf0 ksys_ioctl+0x84/0xb4 __arm64_sys_ioctl+0x28/0xc4 el0_svc_common.constprop.3+0xa4/0x254 el0_svc_handler+0x84/0xa0 el0_svc+0x10/0x26c Code: b9401260 f9615681 51000400 8b001c20 (f9403c1a)(CVE-2021-47…</p> <p><strong>Affected:</strong> openEuler:20.03-LTS-SP4: kernel</p> <p>The Linux Kernel, the operating system core itself. Security Fix(es): In the Linux kernel, the following vulnerability has been resolved: net: usb: fix possible use-after-free in smsc75xx_bind The commit 46a8b29c6306 (&amp;quot;net: usb: fix memory leak in smsc75xx_bind&amp;quot;) fails to clean up the work scheduled in smsc75xx_reset-&amp;gt; smsc75xx_set_multicast, which leads to use-after-free if the work is scheduled to start after the deallocation. In addition, this patch also removes a dangling pointer - dev-&amp;gt;data[0]. This patch calls cancel_work_sync to cancel the scheduled work and set the dangling pointer to NULL.(CVE-2021-47239) In the Linux kernel, the following vulnerability has been resolved: RDMA: Verify port when creating flow rule Validate port value provided by the user and with that remove no longer needed validation by the driver. The missing check in the mlx5_ib driver could cause to the below oops. Call trace: _create_flow_rule+0x2d4/0xf28 [mlx5_ib] mlx5_ib_create_flow+0x2d0/0x5b0 [mlx5_ib] ib_uverbs_ex_create_flow+0x4cc/0x624 [ib_uverbs] ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0xd4/0x150 [ib_uverbs] ib_uverbs_cmd_verbs.isra.7+0xb28/0xc50 [ib_uverbs] ib_uverbs_ioctl+0x158/0x1d0 [ib_uverbs] do_vfs_ioctl+0xd0/0xaf0 ksys_ioctl+0x84/0xb4 __arm64_sys_ioctl+0x28/0xc4 el0_svc_common.constprop.3+0xa4/0x254 el0_svc_handler+0x84/0xa0 el0_svc+0x10/0x26c Code: b9401260 f9615681 51000400 8b001c20 (f9403c1a)(CVE-2021-47…</p> https://cve.radiocsirt.org/vuln/oesa-2024-1692 https://cve.radiocsirt.org/vuln/rhsa-2024:3618 <p>kernel: use after free in i2c kernel: media: dvbdev: Fix memory leak in dvb_media_device_free() kernel: i2c: validate user data in compat ioctl kernel: net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send kernel: mtd: require write permissions for locking and badblock ioctls kernel: pid: take a reference when initializing `cad_pid` kernel: i2c: i801: Don&amp;#39;t generate an interrupt on bus reset kernel: net: usb: fix memory leak in smsc75xx_bind kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: vt: fix memory overlapping when deleting chars in the buffer kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: Marvin vulnerability side-channel leakage in the RSA decryption operation kernel: uio: Fix use-after-free in uio_open kernel: pvrusb2: fix use after free on context disconnection kernel: usb: hub: Guard against accesses to uninitialized BOS descriptors kernel: RDMA/siw: Fix connection failure handling kernel: platform/x86: think-lmi: Fix reference leak kernel: net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg kernel: media: uvcvideo: out-of-bounds read in uvc_query_v4l2_menu() kernel: net: bridge: data races indata-races in br_handle_frame_finish() kernel: wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus() kernel: wifi: rt2x00: restart beacon queue when hardware reset kernel: s390/ptrace: handle setting of fpc register correctly kernel: powerpc/lib: Validate size for ve…</p> <p>kernel: use after free in i2c kernel: media: dvbdev: Fix memory leak in dvb_media_device_free() kernel: i2c: validate user data in compat ioctl kernel: net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send kernel: mtd: require write permissions for locking and badblock ioctls kernel: pid: take a reference when initializing `cad_pid` kernel: i2c: i801: Don&amp;#39;t generate an interrupt on bus reset kernel: net: usb: fix memory leak in smsc75xx_bind kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: vt: fix memory overlapping when deleting chars in the buffer kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: Marvin vulnerability side-channel leakage in the RSA decryption operation kernel: uio: Fix use-after-free in uio_open kernel: pvrusb2: fix use after free on context disconnection kernel: usb: hub: Guard against accesses to uninitialized BOS descriptors kernel: RDMA/siw: Fix connection failure handling kernel: platform/x86: think-lmi: Fix reference leak kernel: net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg kernel: media: uvcvideo: out-of-bounds read in uvc_query_v4l2_menu() kernel: net: bridge: data races indata-races in br_handle_frame_finish() kernel: wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus() kernel: wifi: rt2x00: restart beacon queue when hardware reset kernel: s390/ptrace: handle setting of fpc register correctly kernel: powerpc/lib: Validate size for ve…</p> https://cve.radiocsirt.org/vuln/rhsa-2024:3618 https://cve.radiocsirt.org/vuln/rhsa-2024:3627 <p>kernel: use after free in i2c kernel: media: dvbdev: Fix memory leak in dvb_media_device_free() kernel: i2c: validate user data in compat ioctl kernel: net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send kernel: mtd: require write permissions for locking and badblock ioctls kernel: pid: take a reference when initializing `cad_pid` kernel: i2c: i801: Don&amp;#39;t generate an interrupt on bus reset kernel: net: usb: fix memory leak in smsc75xx_bind kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: vt: fix memory overlapping when deleting chars in the buffer kernel: Marvin vulnerability side-channel leakage in the RSA decryption operation kernel: uio: Fix use-after-free in uio_open kernel: pvrusb2: fix use after free on context disconnection kernel: usb: hub: Guard against accesses to uninitialized BOS descriptors kernel: RDMA/siw: Fix connection failure handling kernel: platform/x86: think-lmi: Fix reference leak kernel: net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg kernel: media: uvcvideo: out-of-bounds read in uvc_query_v4l2_menu() kernel: net: bridge: data races indata-races in br_handle_frame_finish() kernel: wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus() kernel: wifi: rt2x00: restart beacon queue when hardware reset kernel: net/sched: act_ct: fix skb leak and crash on ooo frags kernel: Information disclosure in vhost/vhost.c:vhost_new_msg() kernel: Integer Overflow in raid5_cache_co…</p> <p>kernel: use after free in i2c kernel: media: dvbdev: Fix memory leak in dvb_media_device_free() kernel: i2c: validate user data in compat ioctl kernel: net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send kernel: mtd: require write permissions for locking and badblock ioctls kernel: pid: take a reference when initializing `cad_pid` kernel: i2c: i801: Don&amp;#39;t generate an interrupt on bus reset kernel: net: usb: fix memory leak in smsc75xx_bind kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: vt: fix memory overlapping when deleting chars in the buffer kernel: Marvin vulnerability side-channel leakage in the RSA decryption operation kernel: uio: Fix use-after-free in uio_open kernel: pvrusb2: fix use after free on context disconnection kernel: usb: hub: Guard against accesses to uninitialized BOS descriptors kernel: RDMA/siw: Fix connection failure handling kernel: platform/x86: think-lmi: Fix reference leak kernel: net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg kernel: media: uvcvideo: out-of-bounds read in uvc_query_v4l2_menu() kernel: net: bridge: data races indata-races in br_handle_frame_finish() kernel: wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus() kernel: wifi: rt2x00: restart beacon queue when hardware reset kernel: net/sched: act_ct: fix skb leak and crash on ooo frags kernel: Information disclosure in vhost/vhost.c:vhost_new_msg() kernel: Integer Overflow in raid5_cache_co…</p> https://cve.radiocsirt.org/vuln/rhsa-2024:3627 https://cve.radiocsirt.org/vuln/ssa-265688 <p>An out-of-bounds (OOB) memory write flaw was found in the NFSD in the Linux kernel. Missing sanity may lead to a write beyond bmval[bmlen-1] in nfsd4_decode_bitmap4 in fs/nfsd/nfs4xdr.c. In this flaw, a local attacker with user privilege may gain access to out-of-bounds memory, leading to a system integrity and confidentiality threat. fs/nfsd/trace.h in the Linux kernel before 5.13.4 might allow remote attackers to cause a denial of service (out-of-bounds read in strlen) by sending NFS traffic when the trace event framework is being used for nfsd. SUNRPC: null pointer dereference in svc_rqst_free(). When alloc_pages_node() returns null in svc_rqst_alloc(), the null rq_scratch_page pointer will be dereferenced when calling put_page() in svc_rqst_free(). NFSD: READDIR buffer overflow. If a client sends a READDIR count argument that is too small (say, zero), then the buffer size calculation in the new init_dirlist helper functions results in an underflow, allowing the XDR stream functions to write beyond the actual buffer. This calculation has always been suspect. NFSD has never sanity- checked the READDIR count argument, but the old entry encoders managed the problem correctly. With the commits below, entry encoding changed, exposing the underflow to the pointer arithmetic in xdr_reserve_space(). Modern NFS clients attempt to retrieve as much data as possible for each READDIR request. nfsd: NULL dereference in nfs3svc_encode_getaclres. A NULL pointer dereference vulnerability…</p> <p>An out-of-bounds (OOB) memory write flaw was found in the NFSD in the Linux kernel. Missing sanity may lead to a write beyond bmval[bmlen-1] in nfsd4_decode_bitmap4 in fs/nfsd/nfs4xdr.c. In this flaw, a local attacker with user privilege may gain access to out-of-bounds memory, leading to a system integrity and confidentiality threat. fs/nfsd/trace.h in the Linux kernel before 5.13.4 might allow remote attackers to cause a denial of service (out-of-bounds read in strlen) by sending NFS traffic when the trace event framework is being used for nfsd. SUNRPC: null pointer dereference in svc_rqst_free(). When alloc_pages_node() returns null in svc_rqst_alloc(), the null rq_scratch_page pointer will be dereferenced when calling put_page() in svc_rqst_free(). NFSD: READDIR buffer overflow. If a client sends a READDIR count argument that is too small (say, zero), then the buffer size calculation in the new init_dirlist helper functions results in an underflow, allowing the XDR stream functions to write beyond the actual buffer. This calculation has always been suspect. NFSD has never sanity- checked the READDIR count argument, but the old entry encoders managed the problem correctly. With the commits below, entry encoding changed, exposing the underflow to the pointer arithmetic in xdr_reserve_space(). Modern NFS clients attempt to retrieve as much data as possible for each READDIR request. nfsd: NULL dereference in nfs3svc_encode_getaclres. A NULL pointer dereference vulnerability…</p> https://cve.radiocsirt.org/vuln/ssa-265688 https://cve.radiocsirt.org/vuln/suse-su-2024:1979-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2024:1979-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26934 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-kvm and 170 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix deadlock in usb_deauthorize_interface() Among the attribute file callback routines in drivers/usb/core/sysfs.c, the interface_authorized_store() function is the only one which acquires a device lock on an ancestor device: It calls usb_deauthorize_interface(), which locks the interface&#39;s parent USB device. The will lead to deadlock if another process already owns that lock and tries to remove the interface, whether through a configuration change or because the device has been disconnected. As part of the removal procedure, device_del() waits for all ongoing sysfs attribute callbacks to complete. But usb_deauthorize_interface() can&#39;t complete until the device lock has been released, and the lock won&#39;t be released until the removal has finished. The mechanism provided by sysfs to prevent this kind of deadlock is to use the sysfs_break_active_protection() function, which tells sysfs not to wait for the attribute callback. Reported-and-tested by: Yue Sun &lt;samsun1006219@gmail.com&gt; Reported by: xingwei lee &lt;xrivendell7@gmail.com&gt;</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-kvm and 170 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix deadlock in usb_deauthorize_interface() Among the attribute file callback routines in drivers/usb/core/sysfs.c, the interface_authorized_store() function is the only one which acquires a device lock on an ancestor device: It calls usb_deauthorize_interface(), which locks the interface&#39;s parent USB device. The will lead to deadlock if another process already owns that lock and tries to remove the interface, whether through a configuration change or because the device has been disconnected. As part of the removal procedure, device_del() waits for all ongoing sysfs attribute callbacks to complete. But usb_deauthorize_interface() can&#39;t complete until the device lock has been released, and the lock won&#39;t be released until the removal has finished. The mechanism provided by sysfs to prevent this kind of deadlock is to use the sysfs_break_active_protection() function, which tells sysfs not to wait for the attribute callback. Reported-and-tested by: Yue Sun &lt;samsun1006219@gmail.com&gt; Reported by: xingwei lee &lt;xrivendell7@gmail.com&gt;</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26934 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1008 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder sonstige Auswirkungen zu verursachen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder sonstige Auswirkungen zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1008