https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 17:10:09 +0000 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1032 certfr-2025-avi-1032 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1032 https://cve.radiocsirt.org/vuln/fkie_cve-2022-50487 <p>Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.</p> <p>Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-50487 https://cve.radiocsirt.org/vuln/ghsa-w4m7-g79f-rv8p <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>NFSD: Protect against send buffer overflow in NFSv3 READDIR</p> <p>Since before the git era, NFSD has conserved the number of pages held by each nfsd thread by combining the RPC receive and send buffers into a single array of pages. This works because there are no cases where an operation needs a large RPC Call message and a large RPC Reply message at the same time.</p> <p>Once an RPC Call has been received, svc_process() updates svc_rqst::rq_res to describe the part of rq_pages that can be used for constructing the Reply. This means that the send buffer (rq_res) shrinks when the received RPC record containing the RPC Call is large.</p> <p>A client can force this shrinkage on TCP by sending a correctly- formed RPC Call header contained in an RPC record that is excessively large. The full maximum payload size cannot be constructed in that case.</p> <p>Thanks to Aleksi Illikainen and Kari Hulkko for uncovering this issue.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>NFSD: Protect against send buffer overflow in NFSv3 READDIR</p> <p>Since before the git era, NFSD has conserved the number of pages held by each nfsd thread by combining the RPC receive and send buffers into a single array of pages. This works because there are no cases where an operation needs a large RPC Call message and a large RPC Reply message at the same time.</p> <p>Once an RPC Call has been received, svc_process() updates svc_rqst::rq_res to describe the part of rq_pages that can be used for constructing the Reply. This means that the send buffer (rq_res) shrinks when the received RPC record containing the RPC Call is large.</p> <p>A client can force this shrinkage on TCP by sending a correctly- formed RPC Call header contained in an RPC record that is excessively large. The full maximum payload size cannot be constructed in that case.</p> <p>Thanks to Aleksi Illikainen and Kari Hulkko for uncovering this issue.</p> https://cve.radiocsirt.org/vuln/ghsa-w4m7-g79f-rv8p https://cve.radiocsirt.org/vuln/rhsa-2023:0832 <p>kernel: an out-of-bounds vulnerability in i2c-ismt driver kernel: mm/mremap.c use-after-free vulnerability kernel: nfsd buffer overflow by RPC message over TCP with garbage data kernel: NFSD: Protect against send buffer overflow in NFSv2 READDIR kernel: NFSD: Protect against send buffer overflow in NFSv2 READ kernel: iommu/vt-d: Clean up si_domain in the init_dmars() error path kernel: NFSD: Protect against send buffer overflow in NFSv3 READDIR</p> <p>kernel: an out-of-bounds vulnerability in i2c-ismt driver kernel: mm/mremap.c use-after-free vulnerability kernel: nfsd buffer overflow by RPC message over TCP with garbage data kernel: NFSD: Protect against send buffer overflow in NFSv2 READDIR kernel: NFSD: Protect against send buffer overflow in NFSv2 READ kernel: iommu/vt-d: Clean up si_domain in the init_dmars() error path kernel: NFSD: Protect against send buffer overflow in NFSv3 READDIR</p> https://cve.radiocsirt.org/vuln/rhsa-2023:0832 https://cve.radiocsirt.org/vuln/suse-su-2025:4135-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:4135-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50487 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, 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 and 137 more</p> <p>Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, 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 and 137 more</p> <p>Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50487 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2194 <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2194