Security Vulnerabilities fixed in Firefox ESR 115.28 — Mozilla

CVE-2025-10533: Integer overflow in the SVG component Reporter Andrew Creskey Impact moderate References Bug 1980788...

Mozilla -- integer overflow

[email protected] reports: Integer overflow in the SVG component...

SUSE CVE-2022-50252

In the Linux kernel, the following vulnerability has been resolved: igb: Do not free qvector unless new one was allocated Avoid potential use-after-free condition under memory pressure. If the kzalloc fails, qvector will be freed but left in the original adapter-qvectorvidx array position...

DEBIAN-CVE-2023-53184

In the Linux kernel, the following vulnerability has been resolved: arm64/sme: Set new vector length before reallocating As part of fixing the allocation of the buffer for SVE state when changing SME vector length we introduced an immediate reallocation of the SVE state, this is also done when...

CVE-2023-53184

In the Linux kernel, the following vulnerability has been resolved: arm64/sme: Set new vector length before reallocating As part of fixing the allocation of the buffer for SVE state when changing SME vector length we introduced an immediate reallocation of the SVE state, this is also done when...

CVE-2022-50252

In the Linux kernel, the following vulnerability has been resolved: igb: Do not free qvector unless new one was allocated Avoid potential use-after-free condition under memory pressure. If the kzalloc fails, qvector will be freed but left in the original adapter-qvectorvidx array position...

UBUNTU-CVE-2023-53184

In the Linux kernel, the following vulnerability has been resolved: arm64/sme: Set new vector length before reallocating As part of fixing the allocation of the buffer for SVE state when changing SME vector length we introduced an immediate reallocation of the SVE state, this is also done when...

UBUNTU-CVE-2022-50252

In the Linux kernel, the following vulnerability has been resolved: igb: Do not free qvector unless new one was allocated Avoid potential use-after-free condition under memory pressure. If the kzalloc fails, qvector will be freed but left in the original adapter-qvectorvidx array position...

CVE-2023-53184 arm64/sme: Set new vector length before reallocating

In the Linux kernel, the following vulnerability has been resolved: arm64/sme: Set new vector length before reallocating As part of fixing the allocation of the buffer for SVE state when changing SME vector length we introduced an immediate reallocation of the SVE state, this is also done when...

CVE-2023-53184

The CVE-2023-53184 entry concerns a Linux kernel vulnerability in arm64 SME (SVE state handling). The root cause is that the vector length is updated after allocating the SVE state, causing allocation with the old length and potential memory corruption from an undersized buffer. The fix moves the...

CVE-2023-53184 arm64/sme: Set new vector length before reallocating

In the Linux kernel, the following vulnerability has been resolved: arm64/sme: Set new vector length before reallocating As part of fixing the allocation of the buffer for SVE state when changing SME vector length we introduced an immediate reallocation of the SVE state, this is also done when...

CVE-2022-50252

CVE-2022-50252 affects the Linux kernel igb driver. The issue arises when memory pressure triggers kzalloc() failure: q_vector is freed but not cleared from adapter->q_vector[v_idx], risking a use-after-free. The available connected advisories confirm the fix was implemented to ensure that q_v...

CVE-2022-50252 igb: Do not free q_vector unless new one was allocated

In the Linux kernel, the following vulnerability has been resolved: igb: Do not free qvector unless new one was allocated Avoid potential use-after-free condition under memory pressure. If the kzalloc fails, qvector will be freed but left in the original adapter-qvectorvidx array position...

CVE-2022-50252 igb: Do not free q_vector unless new one was allocated

In the Linux kernel, the following vulnerability has been resolved: igb: Do not free qvector unless new one was allocated Avoid potential use-after-free condition under memory pressure. If the kzalloc fails, qvector will be freed but left in the original adapter-qvectorvidx array position...

UBUNTU-CVE-2025-39802

In the Linux kernel, the following vulnerability has been resolved: lib/crypto: arm/poly1305: Fix register corruption in no-SIMD contexts Restore the SIMD usability check that was removed by commit 773426f4771b "crypto: arm/poly1305 - Add block-only interface". This safety check is cheap and is...

UBUNTU-CVE-2025-39804

In the Linux kernel, the following vulnerability has been resolved: lib/crypto: arm64/poly1305: Fix register corruption in no-SIMD contexts Restore the SIMD usability check that was removed by commit a59e5468a921 "crypto: arm64/poly1305 - Add block-only interface". This safety check is cheap and ...

CVE-2025-39804

In the Linux kernel, the following vulnerability has been resolved: lib/crypto: arm64/poly1305: Fix register corruption in no-SIMD contexts Restore the SIMD usability check that was removed by commit a59e5468a921 "crypto: arm64/poly1305 - Add block-only interface". This safety check is cheap and ...

CVE-2025-39804 lib/crypto: arm64/poly1305: Fix register corruption in no-SIMD contexts

In the Linux kernel, the following vulnerability has been resolved: lib/crypto: arm64/poly1305: Fix register corruption in no-SIMD contexts Restore the SIMD usability check that was removed by commit a59e5468a921 "crypto: arm64/poly1305 - Add block-only interface". This safety check is cheap and ...

CVE-2025-39802 lib/crypto: arm/poly1305: Fix register corruption in no-SIMD contexts

In the Linux kernel, the following vulnerability has been resolved: lib/crypto: arm/poly1305: Fix register corruption in no-SIMD contexts Restore the SIMD usability check that was removed by commit 773426f4771b "crypto: arm/poly1305 - Add block-only interface". This safety check is cheap and is...

CVE-2025-39802

CVE-2025-39802 affects the Linux kernel’s poly1305 implementation (lib/crypto: arm/poly1305). The root cause is register corruption when SIMD is unusable; the patch restores a cheap SIMD usability check (may_use_simd) that was removed by a prior commit and ensures poly1305 code behaves safely rat...