Paul Menzel

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to the `lis3lv02d i2c` component in the Linux kernel, where the `lis3lv02d i2c suspend()` function calls `lis3lv02d poweroff()` even if the device has already been turned off by the runtime-suspend handler. This can cause unbalanced disables for the regulator, leading to a warning in the regulator core. The `lis3lv02d i2c resume()` function has similar issues, where it always powers on the device if it is runtime suspended, causing the enabled count for the regulator to increase by 1 every suspend/resume. These unbalanced regulator enable calls can cause the regulator to never be turned off and trigger a warning on driver unbind. **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** Thunderbird versions 68 through 102.9.1 Thunderbird versions prior to 102.10 **Description** The issue is related to the implementation of the S/MIME protocol in the Thunderbird email client, specifically with errors in resource release. When sending S/MIME encrypted email, the OCSP revocation status of recipient certificates was not checked, and revoked certificates would be accepted. This could allow a remote attacker to bypass existing security restrictions and gain unauthorized access to protected information. **Recommendations** For Thunderbird versions 68 through 102.9.1, update to version 102.10 or later to resolve the issue. For Thunderbird versions prior to 102.10, update to version 102.10 or later to resolve the issue. As a temporary workaround, consider disabling S/MIME encryption until a patch is available. Restrict access to sensitive information to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Thunderbird versions 68 through 102.7.0 **Description** The issue is related to errors in checking the S/Mime signature's OCSP certificate revocation status. This could allow a remote attacker to implement a spoofing attack. Mail signed with a revoked certificate would be displayed as having a valid signature. **Recommendations** For Thunderbird versions 68 through 102.7.0, update to version 102.7.1 or later to resolve the issue. As a temporary workaround, consider disabling S/Mime signature verification until a patch is available.