https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 20:52:14 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-03039 bdu:2025-03039 https://cve.radiocsirt.org/vuln/bdu:2025-03039 https://cve.radiocsirt.org/vuln/bell-cve-2024-47718 <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-47718 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0999 certfr-2024-avi-0999 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0999 https://cve.radiocsirt.org/vuln/euvd-2026-317064 EUVD-2026-317064 https://cve.radiocsirt.org/vuln/euvd-2026-317064 https://cve.radiocsirt.org/vuln/fkie_cve-2024-47718 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>wifi: rtw88: always wait for both firmware loading attempts</p> <p>In &#39;rtw_wait_firmware_completion()&#39;, always wait for both (regular and wowlan) firmware loading attempts. Otherwise if &#39;rtw_usb_intf_init()&#39; has failed in &#39;rtw_usb_probe()&#39;, &#39;rtw_usb_disconnect()&#39; may issue &#39;ieee80211_free_hw()&#39; when one of &#39;rtw_load_firmware_cb()&#39; (usually the wowlan one) is still in progress, causing UAF detected by KASAN.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>wifi: rtw88: always wait for both firmware loading attempts</p> <p>In &#39;rtw_wait_firmware_completion()&#39;, always wait for both (regular and wowlan) firmware loading attempts. Otherwise if &#39;rtw_usb_intf_init()&#39; has failed in &#39;rtw_usb_probe()&#39;, &#39;rtw_usb_disconnect()&#39; may issue &#39;ieee80211_free_hw()&#39; when one of &#39;rtw_load_firmware_cb()&#39; (usually the wowlan one) is still in progress, causing UAF detected by KASAN.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-47718 https://cve.radiocsirt.org/vuln/ghsa-992g-jf7j-f3wc <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>wifi: rtw88: always wait for both firmware loading attempts</p> <p>In &#39;rtw_wait_firmware_completion()&#39;, always wait for both (regular and wowlan) firmware loading attempts. Otherwise if &#39;rtw_usb_intf_init()&#39; has failed in &#39;rtw_usb_probe()&#39;, &#39;rtw_usb_disconnect()&#39; may issue &#39;ieee80211_free_hw()&#39; when one of &#39;rtw_load_firmware_cb()&#39; (usually the wowlan one) is still in progress, causing UAF detected by KASAN.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>wifi: rtw88: always wait for both firmware loading attempts</p> <p>In &#39;rtw_wait_firmware_completion()&#39;, always wait for both (regular and wowlan) firmware loading attempts. Otherwise if &#39;rtw_usb_intf_init()&#39; has failed in &#39;rtw_usb_probe()&#39;, &#39;rtw_usb_disconnect()&#39; may issue &#39;ieee80211_free_hw()&#39; when one of &#39;rtw_load_firmware_cb()&#39; (usually the wowlan one) is still in progress, causing UAF detected by KASAN.</p> https://cve.radiocsirt.org/vuln/ghsa-992g-jf7j-f3wc 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-47718 msrc_CVE-2024-47718 https://cve.radiocsirt.org/vuln/msrc_cve-2024-47718 https://cve.radiocsirt.org/vuln/oesa-2024-2518 <p><strong>Affected:</strong> openEuler:22.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: serial: sc16is7xx: fix invalid FIFO access with special register set When enabling access to the special register set, Receiver time-out and RHR interrupts can happen. In this case, the IRQ handler will try to read from the FIFO thru the RHR register at address 0x00, but address 0x00 is mapped to DLL register, resulting in erroneous FIFO reading. Call graph example: sc16is7xx_startup(): entry sc16is7xx_ms_proc(): entry sc16is7xx_set_termios(): entry sc16is7xx_set_baud(): DLH/DLL = $009C --&amp;gt; access special register set sc16is7xx_port_irq() entry --&amp;gt; IIR is 0x0C sc16is7xx_handle_rx() entry sc16is7xx_fifo_read(): --&amp;gt; unable to access FIFO (RHR) because it is mapped to DLL (LCR=LCR_CONF_MODE_A) sc16is7xx_set_baud(): exit --&amp;gt; Restore access to general register set Fix the problem by claiming the efr_lock mutex when accessing the Special register set.(CVE-2024-44950) In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check link_index before accessing dc-&amp;gt;links[] [WHY &amp;amp; HOW] dc-&amp;gt;links[] has max size of MAX_LINKS and NULL is return when trying to access with out-of-bound index. This fixes 3 OVERRUN and 1 RESOURCE_LEAK issues reported by Coverity.(CVE-2024-46813) In the Linux kernel, the…</p> <p><strong>Affected:</strong> openEuler:22.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: serial: sc16is7xx: fix invalid FIFO access with special register set When enabling access to the special register set, Receiver time-out and RHR interrupts can happen. In this case, the IRQ handler will try to read from the FIFO thru the RHR register at address 0x00, but address 0x00 is mapped to DLL register, resulting in erroneous FIFO reading. Call graph example: sc16is7xx_startup(): entry sc16is7xx_ms_proc(): entry sc16is7xx_set_termios(): entry sc16is7xx_set_baud(): DLH/DLL = $009C --&amp;gt; access special register set sc16is7xx_port_irq() entry --&amp;gt; IIR is 0x0C sc16is7xx_handle_rx() entry sc16is7xx_fifo_read(): --&amp;gt; unable to access FIFO (RHR) because it is mapped to DLL (LCR=LCR_CONF_MODE_A) sc16is7xx_set_baud(): exit --&amp;gt; Restore access to general register set Fix the problem by claiming the efr_lock mutex when accessing the Special register set.(CVE-2024-44950) In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check link_index before accessing dc-&amp;gt;links[] [WHY &amp;amp; HOW] dc-&amp;gt;links[] has max size of MAX_LINKS and NULL is return when trying to access with out-of-bound index. This fixes 3 OVERRUN and 1 RESOURCE_LEAK issues reported by Coverity.(CVE-2024-46813) In the Linux kernel, the…</p> https://cve.radiocsirt.org/vuln/oesa-2024-2518 https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1 <p>kernel-devel-6.11.8-1.1 on GA media</p> <p>kernel-devel-6.11.8-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1 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:3984-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:3984-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47718 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 164 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: wifi: rtw88: always wait for both firmware loading attempts In &#39;rtw_wait_firmware_completion()&#39;, always wait for both (regular and wowlan) firmware loading attempts. Otherwise if &#39;rtw_usb_intf_init()&#39; has failed in &#39;rtw_usb_probe()&#39;, &#39;rtw_usb_disconnect()&#39; may issue &#39;ieee80211_free_hw()&#39; when one of &#39;rtw_load_firmware_cb()&#39; (usually the wowlan one) is still in progress, causing UAF detected by KASAN.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 164 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: wifi: rtw88: always wait for both firmware loading attempts In &#39;rtw_wait_firmware_completion()&#39;, always wait for both (regular and wowlan) firmware loading attempts. Otherwise if &#39;rtw_usb_intf_init()&#39; has failed in &#39;rtw_usb_probe()&#39;, &#39;rtw_usb_disconnect()&#39; may issue &#39;ieee80211_free_hw()&#39; when one of &#39;rtw_load_firmware_cb()&#39; (usually the wowlan one) is still in progress, causing UAF detected by KASAN.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47718 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251