https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 16:26:29 +0000 https://cve.radiocsirt.org/vuln/alsa-2025:12447 <p><strong>Affected:</strong> AlmaLinux:9: libxml2, AlmaLinux:9: libxml2-devel, AlmaLinux:9: python3-libxml2</p> <p>The libxml2 library is a development toolbox providing the implementation of various XML standards.</p> <p>Security Fix(es):</p> <p>* libxslt: Heap Use-After-Free in libxslt caused by atype corruption in xmlAttrPtr (CVE-2025-7425)</p> <p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p> <p><strong>Affected:</strong> AlmaLinux:9: libxml2, AlmaLinux:9: libxml2-devel, AlmaLinux:9: python3-libxml2</p> <p>The libxml2 library is a development toolbox providing the implementation of various XML standards.</p> <p>Security Fix(es):</p> <p>* libxslt: Heap Use-After-Free in libxslt caused by atype corruption in xmlAttrPtr (CVE-2025-7425)</p> <p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p> https://cve.radiocsirt.org/vuln/alsa-2025:12447 https://cve.radiocsirt.org/vuln/bdu:2026-04327 bdu:2026-04327 https://cve.radiocsirt.org/vuln/bdu:2026-04327 https://cve.radiocsirt.org/vuln/bell-cve-2025-7425 <p><strong>Affected:</strong> Alpaquita:23: libxslt, Alpaquita:stream: libxslt, BellSoft Hardened Containers:23: libxslt, BellSoft Hardened Containers:stream: libxslt</p> <p><strong>Affected:</strong> Alpaquita:23: libxslt, Alpaquita:stream: libxslt, BellSoft Hardened Containers:23: libxslt, BellSoft Hardened Containers:stream: libxslt</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-7425 https://cve.radiocsirt.org/vuln/bit-java-2025-7425 <p><strong>Affected:</strong> Bitnami: java</p> <p>A flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.</p> <p><strong>Affected:</strong> Bitnami: java</p> <p>A flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.</p> https://cve.radiocsirt.org/vuln/bit-java-2025-7425 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0640 certfr-2025-avi-0640 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0640 https://cve.radiocsirt.org/vuln/euvd-2026-372986 EUVD-2026-372986 https://cve.radiocsirt.org/vuln/euvd-2026-372986 https://cve.radiocsirt.org/vuln/fkie_cve-2025-7425 <p>A flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.</p> <p>A flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-7425 https://cve.radiocsirt.org/vuln/ghsa-8c4w-j52q-j4jq <p>A flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.</p> <p>A flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.</p> https://cve.radiocsirt.org/vuln/ghsa-8c4w-j52q-j4jq 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-2025-7425 msrc_CVE-2025-7425 https://cve.radiocsirt.org/vuln/msrc_cve-2025-7425 https://cve.radiocsirt.org/vuln/ncsc-2026-0030 NCSC-2026-0030 https://cve.radiocsirt.org/vuln/ncsc-2026-0030 https://cve.radiocsirt.org/vuln/opensuse-su-2025:15363-1 <p>libxml2-2-2.13.8-3.1 on GA media</p> <p>libxml2-2-2.13.8-3.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15363-1 https://cve.radiocsirt.org/vuln/rhba-2025:12345 <p>libxslt: Type confusion in xmlNode.psvi between stylesheet and source nodes libxslt: libxml2: Heap Use-After-Free in libxslt caused by atype corruption in xmlAttrPtr</p> <p>libxslt: Type confusion in xmlNode.psvi between stylesheet and source nodes libxslt: libxml2: Heap Use-After-Free in libxslt caused by atype corruption in xmlAttrPtr</p> https://cve.radiocsirt.org/vuln/rhba-2025:12345 https://cve.radiocsirt.org/vuln/ssa-032379 <p>In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check link_res-&gt;hpo_dp_link_enc before using it [WHAT &amp; HOW] Functions dp_enable_link_phy and dp_disable_link_phy can pass link_res without initializing hpo_dp_link_enc and it is necessary to check for null before dereferencing. This fixes 2 FORWARD_NULL issues reported by Coverity. In the Linux kernel, the following vulnerability has been resolved:</p> <p>fs: relax assertions on failure to encode file handles</p> <p>Encoding file handles is usually performed by a filesystem &gt;encode_fh() method that may fail for various reasons.</p> <p>The legacy users of exportfs_encode_fh(), namely, nfsd and name_to_handle_at(2) syscall are ready to cope with the possibility of failure to encode a file handle.</p> <p>There are a few other users of exportfs_encode_{fh,fid}() that currently have a WARN_ON() assertion when -&gt;encode_fh() fails. Relax those assertions because they are wrong.</p> <p>The second linked bug report states commit 16aac5ad1fa9 (&#34;ovl: support encoding non-decodable file handles&#34;) in v6.6 as the regressing commit, but this is not accurate.</p> <p>The aforementioned commit only increases the chances of the assertion and allows triggering the assertion with the reproducer using overlayfs, inotify and drop_caches.</p> <p>Triggering this assertion was always possible with other filesystems and other reasons of -&gt;encode_fh() failures and more particularly, it was also possible with the exact same reproducer using overlay…</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check link_res-&gt;hpo_dp_link_enc before using it [WHAT &amp; HOW] Functions dp_enable_link_phy and dp_disable_link_phy can pass link_res without initializing hpo_dp_link_enc and it is necessary to check for null before dereferencing. This fixes 2 FORWARD_NULL issues reported by Coverity. In the Linux kernel, the following vulnerability has been resolved:</p> <p>fs: relax assertions on failure to encode file handles</p> <p>Encoding file handles is usually performed by a filesystem &gt;encode_fh() method that may fail for various reasons.</p> <p>The legacy users of exportfs_encode_fh(), namely, nfsd and name_to_handle_at(2) syscall are ready to cope with the possibility of failure to encode a file handle.</p> <p>There are a few other users of exportfs_encode_{fh,fid}() that currently have a WARN_ON() assertion when -&gt;encode_fh() fails. Relax those assertions because they are wrong.</p> <p>The second linked bug report states commit 16aac5ad1fa9 (&#34;ovl: support encoding non-decodable file handles&#34;) in v6.6 as the regressing commit, but this is not accurate.</p> <p>The aforementioned commit only increases the chances of the assertion and allows triggering the assertion with the reproducer using overlayfs, inotify and drop_caches.</p> <p>Triggering this assertion was always possible with other filesystems and other reasons of -&gt;encode_fh() failures and more particularly, it was also possible with the exact same reproducer using overlay…</p> https://cve.radiocsirt.org/vuln/ssa-032379 https://cve.radiocsirt.org/vuln/suse-su-2025:02547-1 <p>Security update for libxml2</p> <p>Security update for libxml2</p> https://cve.radiocsirt.org/vuln/suse-su-2025:02547-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-7425 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: libxml2, Ubuntu:Pro:16.04:LTS: libxml2, Ubuntu:Pro:18.04:LTS: libxml2, Ubuntu:Pro:20.04:LTS: libxml2, Ubuntu:22.04:LTS: libxml2, Ubuntu:24.04:LTS: libxml2, Ubuntu:24.04:LTS: libxslt, Ubuntu:25.10: libxslt, Ubuntu:26.04:LTS: libxslt</p> <p>A flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: libxml2, Ubuntu:Pro:16.04:LTS: libxml2, Ubuntu:Pro:18.04:LTS: libxml2, Ubuntu:Pro:20.04:LTS: libxml2, Ubuntu:22.04:LTS: libxml2, Ubuntu:24.04:LTS: libxml2, Ubuntu:24.04:LTS: libxslt, Ubuntu:25.10: libxslt, Ubuntu:26.04:LTS: libxslt</p> <p>A flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-7425 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1668 <p>Ein Angreifer kann mehrere Schwachstellen in Apple iOS und Apple iPadOS ausnutzen, um Informationen offenzulegen, um einen Denial of Service Angriff durchzuführen, um Sicherheitsvorkehrungen zu umgehen und um weitere, nicht spezifizierte Auswirkungen zu verursachen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Apple iOS und Apple iPadOS ausnutzen, um Informationen offenzulegen, um einen Denial of Service Angriff durchzuführen, um Sicherheitsvorkehrungen zu umgehen und um weitere, nicht spezifizierte Auswirkungen zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1668