0.0

CVE-2025-29649 -

DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage.

πŸ“… Published: April 16, 2025, midnight πŸ”„ Last Modified: June 16, 2025, 10:15 p.m.

0.0

CVE-2025-29651 -

DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage.

πŸ“… Published: April 16, 2025, midnight πŸ”„ Last Modified: June 16, 2025, 10:16 p.m.

5.5

CVSS3.1

CVE-2025-22106 - vmxnet3: unregister xdp rxq info in the reset path

In the Linux kernel, the following vulnerability has been resolved: vmxnet3: unregister xdp rxq info in the reset path vmxnet3 does not unregister xdp rxq info in the vmxnet3_reset_work() code path as vmxnet3_rq_destroy() is not invoked in this code path. So, we get below message with a backtrace…

πŸ“… Published: April 16, 2025, midnight πŸ”„ Last Modified: Nov. 3, 2025, 6:42 p.m.

0.0

CVE-2025-29650 -

DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage.

πŸ“… Published: April 16, 2025, midnight πŸ”„ Last Modified: June 16, 2025, 10:16 p.m.

0.0

CVE-2025-29652 -

DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage.

πŸ“… Published: April 16, 2025, midnight πŸ”„ Last Modified: June 16, 2025, 10:16 p.m.

0.0

CVE-2025-29648 -

DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage.

πŸ“… Published: April 16, 2025, midnight πŸ”„ Last Modified: June 16, 2025, 10:15 p.m.

5.5

CVSS3.1

CVE-2025-22047 - x86/microcode/AMD: Fix __apply_microcode_amd()'s return value

In the Linux kernel, the following vulnerability has been resolved: x86/microcode/AMD: Fix __apply_microcode_amd()'s return value When verify_sha256_digest() fails, __apply_microcode_amd() should propagate the failure by returning false (and not -1 which is promoted to true).

πŸ“… Published: April 16, 2025, midnight πŸ”„ Last Modified: Oct. 31, 2025, 8:20 p.m.

5.5

CVSS3.1

CVE-2024-58095 - jfs: add check read-only before txBeginAnon() call

In the Linux kernel, the following vulnerability has been resolved: jfs: add check read-only before txBeginAnon() call Added a read-only check before calling `txBeginAnon` in `extAlloc` and `extRecord`. This prevents modification attempts on a read-only mounted filesystem, avoiding potential erro…

πŸ“… Published: April 16, 2025, midnight πŸ”„ Last Modified: Oct. 28, 2025, 6:55 p.m.

5.5

CVSS3.1

CVE-2025-23136 - thermal: int340x: Add NULL check for adev

In the Linux kernel, the following vulnerability has been resolved: thermal: int340x: Add NULL check for adev Not all devices have an ACPI companion fwnode, so adev might be NULL. This is similar to the commit cd2fd6eab480 ("platform/x86: int3472: Check for adev == NULL"). Add a check for adev n…

πŸ“… Published: April 16, 2025, midnight πŸ”„ Last Modified: Nov. 3, 2025, 8:17 p.m.

5.5

CVSS3.1

CVE-2025-23134 - ALSA: timer: Don't take register_mutex with copy_from/to_user()

In the Linux kernel, the following vulnerability has been resolved: ALSA: timer: Don't take register_mutex with copy_from/to_user() The infamous mmap_lock taken in copy_from/to_user() can be often problematic when it's called inside another mutex, as they might lead to deadlocks. In the case of …

πŸ“… Published: April 16, 2025, midnight πŸ”„ Last Modified: Oct. 1, 2025, 5:15 p.m.
Total resulsts: 343980
Page 5272 of 34,398
Β« previous page Β» next page
Filters