https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 00:52:08 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-04221 bdu:2026-04221 https://cve.radiocsirt.org/vuln/bdu:2026-04221 https://cve.radiocsirt.org/vuln/bell-cve-2025-68726 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-68726 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0331 certfr-2026-avi-0331 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0331 https://cve.radiocsirt.org/vuln/euvd-2026-347501 EUVD-2026-347501 https://cve.radiocsirt.org/vuln/euvd-2026-347501 https://cve.radiocsirt.org/vuln/fkie_cve-2025-68726 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>crypto: aead - Fix reqsize handling</p> <p>Commit afddce13ce81d (&#34;crypto: api - Add reqsize to crypto_alg&#34;) introduced cra_reqsize field in crypto_alg struct to replace type specific reqsize fields. It looks like this was introduced specifically for ahash and acomp from the commit description as subsequent commits add necessary changes in these alg frameworks.</p> <p>However, this is being recommended for use in all crypto algs instead of setting reqsize using crypto_*_set_reqsize(). Using cra_reqsize in aead algorithms, hence, causes memory corruptions and crashes as the underlying functions in the algorithm framework have not been updated to set the reqsize properly from cra_reqsize. [1]</p> <p>Add proper set_reqsize calls in the aead init function to properly initialize reqsize for these algorithms in the framework.</p> <p>[1]: https://gist.github.com/Pratham-T/24247446f1faf4b7843e4014d5089f6b</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>crypto: aead - Fix reqsize handling</p> <p>Commit afddce13ce81d (&#34;crypto: api - Add reqsize to crypto_alg&#34;) introduced cra_reqsize field in crypto_alg struct to replace type specific reqsize fields. It looks like this was introduced specifically for ahash and acomp from the commit description as subsequent commits add necessary changes in these alg frameworks.</p> <p>However, this is being recommended for use in all crypto algs instead of setting reqsize using crypto_*_set_reqsize(). Using cra_reqsize in aead algorithms, hence, causes memory corruptions and crashes as the underlying functions in the algorithm framework have not been updated to set the reqsize properly from cra_reqsize. [1]</p> <p>Add proper set_reqsize calls in the aead init function to properly initialize reqsize for these algorithms in the framework.</p> <p>[1]: https://gist.github.com/Pratham-T/24247446f1faf4b7843e4014d5089f6b</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-68726 https://cve.radiocsirt.org/vuln/ghsa-hgjv-cpc3-r8f4 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>crypto: aead - Fix reqsize handling</p> <p>Commit afddce13ce81d (&#34;crypto: api - Add reqsize to crypto_alg&#34;) introduced cra_reqsize field in crypto_alg struct to replace type specific reqsize fields. It looks like this was introduced specifically for ahash and acomp from the commit description as subsequent commits add necessary changes in these alg frameworks.</p> <p>However, this is being recommended for use in all crypto algs instead of setting reqsize using crypto_*_set_reqsize(). Using cra_reqsize in aead algorithms, hence, causes memory corruptions and crashes as the underlying functions in the algorithm framework have not been updated to set the reqsize properly from cra_reqsize. [1]</p> <p>Add proper set_reqsize calls in the aead init function to properly initialize reqsize for these algorithms in the framework.</p> <p>[1]: https://gist.github.com/Pratham-T/24247446f1faf4b7843e4014d5089f6b</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>crypto: aead - Fix reqsize handling</p> <p>Commit afddce13ce81d (&#34;crypto: api - Add reqsize to crypto_alg&#34;) introduced cra_reqsize field in crypto_alg struct to replace type specific reqsize fields. It looks like this was introduced specifically for ahash and acomp from the commit description as subsequent commits add necessary changes in these alg frameworks.</p> <p>However, this is being recommended for use in all crypto algs instead of setting reqsize using crypto_*_set_reqsize(). Using cra_reqsize in aead algorithms, hence, causes memory corruptions and crashes as the underlying functions in the algorithm framework have not been updated to set the reqsize properly from cra_reqsize. [1]</p> <p>Add proper set_reqsize calls in the aead init function to properly initialize reqsize for these algorithms in the framework.</p> <p>[1]: https://gist.github.com/Pratham-T/24247446f1faf4b7843e4014d5089f6b</p> https://cve.radiocsirt.org/vuln/ghsa-hgjv-cpc3-r8f4 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10039-1 <p>kernel-devel-6.18.5-1.1 on GA media</p> <p>kernel-devel-6.18.5-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10039-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68726 <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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 97 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: crypto: aead - Fix reqsize handling Commit afddce13ce81d (&#34;crypto: api - Add reqsize to crypto_alg&#34;) introduced cra_reqsize field in crypto_alg struct to replace type specific reqsize fields. It looks like this was introduced specifically for ahash and acomp from the commit description as subsequent commits add necessary changes in these alg frameworks. However, this is being recommended for use in all crypto algs instead of setting reqsize using crypto_*_set_reqsize(). Using cra_reqsize in aead algorithms, hence, causes memory corruptions and crashes as the underlying functions in the algorithm framework have not been updated to set the reqsize properly from cra_reqsize. [1] Add proper set_reqsize calls in the aead init function to properly initialize reqsize for these algorithms in the framework. [1]: https://gist.github.com/Pratham-T/24247446f1faf4b7843e4014d5089f6b</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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 97 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: crypto: aead - Fix reqsize handling Commit afddce13ce81d (&#34;crypto: api - Add reqsize to crypto_alg&#34;) introduced cra_reqsize field in crypto_alg struct to replace type specific reqsize fields. It looks like this was introduced specifically for ahash and acomp from the commit description as subsequent commits add necessary changes in these alg frameworks. However, this is being recommended for use in all crypto algs instead of setting reqsize using crypto_*_set_reqsize(). Using cra_reqsize in aead algorithms, hence, causes memory corruptions and crashes as the underlying functions in the algorithm framework have not been updated to set the reqsize properly from cra_reqsize. [1] Add proper set_reqsize calls in the aead init function to properly initialize reqsize for these algorithms in the framework. [1]: https://gist.github.com/Pratham-T/24247446f1faf4b7843e4014d5089f6b</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68726 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2920 <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2920