Tony Battersby

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to the bonding driver in the Linux kernel, specifically with the `bonding init()` and `bonding exit()` functions, which are associated with errors in resource management. The vulnerability can be exploited to cause a denial of service. The problem arises when "rmmod bonding" is executed, leading to an oops due to a removed check for `bonding debug root == NULL` in the `debugfs remove()` function. This can happen during module removal or if there is an error during module initialization. The vulnerability is caused by a race condition that can occur when multiple CPUs are involved in the process. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to an incorrect number of pages being released for buffers that do not start at the beginning of a page in the Linux kernel. This is fixed by correcting page refcounts for unaligned buffers in the ` bio release pages()` function. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** OpenSSL versions 3.0 and 3.1 **Description** A bug has been identified in the processing of key and initialisation vector (IV) lengths, potentially leading to truncation or overruns during the initialisation of some symmetric ciphers. This issue can result in non-uniqueness, leading to loss of confidentiality for some cipher modes. The affected ciphers and modes include RC2, RC4, RC5, CCM, GCM, and OCB. Truncation of the IV in CCM, GCM, and OCB modes can lead to loss of confidentiality. For example, when following NIST's SP 800-38D guidance for constructing a deterministic IV for AES in GCM mode, truncation of the counter portion could lead to IV reuse. The `EVP EncryptInit ex2()`, `EVP DecryptInit ex2()`, and `EVP CipherInit ex2()` functions are impacted, and alterations to the key length via the `keylen` parameter or the IV length via the `ivlen` parameter within the `OSSL PARAM` array may not take effect as intended. **Recommendations** For OpenSSL versions 3.0 and 3.1, update to a fixed version to resolve the issue. As a temporary workaround, consider restricting the use of the vulnerable `EVP EncryptInit ex2()`, `EVP DecryptInit ex2()`, and `EVP CipherInit ex2()` functions until a patch is available. Avoid using the `keylen` and `ivlen` parameters within the `OSSL PARAM` array to minimize the risk of exploitation.