https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 10:26:12 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-89674 <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-2026-89674 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253 certfr-2026-avi-1253 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253 https://cve.radiocsirt.org/vuln/euvd-2026-367687 EUVD-2026-367687 https://cve.radiocsirt.org/vuln/euvd-2026-367687 https://cve.radiocsirt.org/vuln/fkie_cve-2026-89674 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget</p> <p>The XDR buffer size calculation in nfsd4_ff_encode_layoutget() has multiple errors that can result in either an out-of-bounds write or leaking uninitialized kernel memory to the client:</p> <p>- fh_len doesn&#39;t account for XDR padding on the file handle data - uid and gid lengths use &#34;8 + len&#34; but xdr_encode_opaque() actually writes &#34;4 + xdr_align_size(len)&#34; bytes - ds_len omits the flags and stats_collect_hint fields (8 bytes), while len&#39;s header constant overestimates by 8 bytes -- these partially cancel but leave a net mismatch</p> <p>The worst case occurs with short strings (e.g. uid=0, gid=0 with an odd-sized file handle), where the function writes up to 5 bytes past the reserved XDR buffer. Conversely, when string lengths happen to be 4-byte aligned, the reservation is too large and stale buffer content is sent to the client.</p> <p>Fix this by breaking out every encoded field explicitly in the ds_len calculation, using xdr_align_size() for all variable-length opaque fields, and correcting the header constants.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget</p> <p>The XDR buffer size calculation in nfsd4_ff_encode_layoutget() has multiple errors that can result in either an out-of-bounds write or leaking uninitialized kernel memory to the client:</p> <p>- fh_len doesn&#39;t account for XDR padding on the file handle data - uid and gid lengths use &#34;8 + len&#34; but xdr_encode_opaque() actually writes &#34;4 + xdr_align_size(len)&#34; bytes - ds_len omits the flags and stats_collect_hint fields (8 bytes), while len&#39;s header constant overestimates by 8 bytes -- these partially cancel but leave a net mismatch</p> <p>The worst case occurs with short strings (e.g. uid=0, gid=0 with an odd-sized file handle), where the function writes up to 5 bytes past the reserved XDR buffer. Conversely, when string lengths happen to be 4-byte aligned, the reservation is too large and stale buffer content is sent to the client.</p> <p>Fix this by breaking out every encoded field explicitly in the ds_len calculation, using xdr_align_size() for all variable-length opaque fields, and correcting the header constants.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-89674 https://cve.radiocsirt.org/vuln/ghsa-qhmp-vm7x-v422 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget</p> <p>The XDR buffer size calculation in nfsd4_ff_encode_layoutget() has multiple errors that can result in either an out-of-bounds write or leaking uninitialized kernel memory to the client:</p> <p>- fh_len doesn&#39;t account for XDR padding on the file handle data - uid and gid lengths use &#34;8 + len&#34; but xdr_encode_opaque() actually writes &#34;4 + xdr_align_size(len)&#34; bytes - ds_len omits the flags and stats_collect_hint fields (8 bytes), while len&#39;s header constant overestimates by 8 bytes -- these partially cancel but leave a net mismatch</p> <p>The worst case occurs with short strings (e.g. uid=0, gid=0 with an odd-sized file handle), where the function writes up to 5 bytes past the reserved XDR buffer. Conversely, when string lengths happen to be 4-byte aligned, the reservation is too large and stale buffer content is sent to the client.</p> <p>Fix this by breaking out every encoded field explicitly in the ds_len calculation, using xdr_align_size() for all variable-length opaque fields, and correcting the header constants.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget</p> <p>The XDR buffer size calculation in nfsd4_ff_encode_layoutget() has multiple errors that can result in either an out-of-bounds write or leaking uninitialized kernel memory to the client:</p> <p>- fh_len doesn&#39;t account for XDR padding on the file handle data - uid and gid lengths use &#34;8 + len&#34; but xdr_encode_opaque() actually writes &#34;4 + xdr_align_size(len)&#34; bytes - ds_len omits the flags and stats_collect_hint fields (8 bytes), while len&#39;s header constant overestimates by 8 bytes -- these partially cancel but leave a net mismatch</p> <p>The worst case occurs with short strings (e.g. uid=0, gid=0 with an odd-sized file handle), where the function writes up to 5 bytes past the reserved XDR buffer. Conversely, when string lengths happen to be 4-byte aligned, the reservation is too large and stale buffer content is sent to the client.</p> <p>Fix this by breaking out every encoded field explicitly in the ds_len calculation, using xdr_align_size() for all variable-length opaque fields, and correcting the header constants.</p> https://cve.radiocsirt.org/vuln/ghsa-qhmp-vm7x-v422 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11805-1 <p>kernel-devel-7.2.6-1.1 on GA media</p> <p>kernel-devel-7.2.6-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11805-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89674 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, 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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget The XDR buffer size calculation in nfsd4_ff_encode_layoutget() has multiple errors that can result in either an out-of-bounds write or leaking uninitialized kernel memory to the client: - fh_len doesn&#39;t account for XDR padding on the file handle data - uid and gid lengths use &#34;8 + len&#34; but xdr_encode_opaque() actually writes &#34;4 + xdr_align_size(len)&#34; bytes - ds_len omits the flags and stats_collect_hint fields (8 bytes), while len&#39;s header constant overestimates by 8 bytes -- these partially cancel but leave a net mismatch The worst case occurs with short strings (e.g. uid=0, gid=0 with an odd-sized file handle), where the function writes up to 5 bytes past the reserved XDR buffer. Conversely, when string lengths happen to be 4-byte aligned, the reservation is too large and stale buffer content is sent to the client. Fix this by breaking out every encoded field explicitly in the ds_len calculation, using xdr_align_size() for all variable-length opaque fields, and correcting the header constants.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, 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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget The XDR buffer size calculation in nfsd4_ff_encode_layoutget() has multiple errors that can result in either an out-of-bounds write or leaking uninitialized kernel memory to the client: - fh_len doesn&#39;t account for XDR padding on the file handle data - uid and gid lengths use &#34;8 + len&#34; but xdr_encode_opaque() actually writes &#34;4 + xdr_align_size(len)&#34; bytes - ds_len omits the flags and stats_collect_hint fields (8 bytes), while len&#39;s header constant overestimates by 8 bytes -- these partially cancel but leave a net mismatch The worst case occurs with short strings (e.g. uid=0, gid=0 with an odd-sized file handle), where the function writes up to 5 bytes past the reserved XDR buffer. Conversely, when string lengths happen to be 4-byte aligned, the reservation is too large and stale buffer content is sent to the client. Fix this by breaking out every encoded field explicitly in the ds_len calculation, using xdr_align_size() for all variable-length opaque fields, and correcting the header constants.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89674 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321