Vendor advisories

Microsoft Security Response Center

Browse 15,972 advisories from this official source. Search by product, CVE, severity, or advisory ID.

Current Checked 5 hours ago Checked every 6 hours

15,972 advisories

Each date says whether the vendor published or updated the bulletin. A vendor bulletin describes products that may be affected. It does not prove that the vulnerable product or version is installed in your environment.

RSS for these results
Microsoft Security Response CenterCVE-2025-69649
MediumCVSS 5.5

GNU Binutils thru 2.46 readelf contains a null pointer dereference vulnerability when processing a crafted ELF binary with malformed header fields. During relocation processing, an invalid or null section pointer may be passed into display_relocations(), resulting in a segmentation fault (SIGSEGV) and abrupt termination. No evidence of memory corruption beyond the null pointer dereference, nor any possibility of code execution, was observed.

Mariner

Affected productscbl2 binutils 2.37-20 on CBL-Mariner 2.0, azl3 binutils 2.41-10 on Azure Linux 3.0, cbl2 binutils 2.37-20 on CBL Mariner 2.0, azl3 binutils 2.41-11 on Azure Linux 3.0
Fixed versions2.41-11
Vendor guidance

Release Notes CBL-Mariner Releases

Microsoft Security Response CenterCVE-2025-69645
MediumCVSS 5.5

Binutils objdump contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF debug information. A logic error in the handling of DWARF compilation units can result in an invalid offset_size value being used inside byte_get_little_endian, leading to an abort (SIGABRT). The issue was observed in binutils 2.44. A local attacker can trigger the crash by supplying a malicious input file.

Mariner

Affected productsazl3 binutils 2.41-11 on Azure Linux 3.0, cbl2 binutils 2.37-20, azl3 binutils 2.41-10 on Azure Linux 3.0, cbl2 binutils 2.37-20 on CBL Mariner 2.0
Fixed versions2.41-11
Vendor guidance

CBL-Mariner Releases Release Notes

Microsoft Security Response CenterCVE-2025-69652
MediumCVSS 6.2

GNU Binutils thru 2.46 readelf contains a vulnerability that leads to an abort (SIGABRT) when processing a crafted ELF binary with malformed DWARF abbrev or debug information. Due to incomplete state cleanup in process_debug_info(), an invalid debug_info_p state may propagate into DWARF attribute parsing routines. When certain malformed attributes result in an unexpected data length of zero, byte_get_little_endian() triggers a fatal abort. No evidence of memory corruption or code execution was observed; the impact is limited to denial of service.

Mariner

Affected productscbl2 binutils 2.37-20 on CBL-Mariner 2.0, azl3 binutils 2.41-10 on Azure Linux 3.0, cbl2 binutils 2.37-20 on CBL Mariner 2.0, azl3 binutils 2.41-11 on Azure Linux 3.0
Fixed versions2.41-11
Vendor guidance

Release Notes CBL-Mariner Releases

Microsoft Security Response CenterCVE-2025-69646
MediumCVSS 5.5

Binutils objdump contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF debug_rnglists data. A logic error in the handling of the debug_rnglists header can cause objdump to repeatedly print the same warning message and fail to terminate, resulting in an unbounded logging loop until the process is interrupted. The issue was observed in binutils 2.44. A local attacker can exploit this vulnerability by supplying a malicious input file, leading to excessive CPU and I/O usage and preventing completion of the objdump analysis.

Mariner

Affected productsazl3 binutils 2.41-10 on Azure Linux 3.0, cbl2 binutils 2.37-20 on CBL Mariner 2.0, azl3 binutils 2.41-11 on Azure Linux 3.0, cbl2 binutils 2.37-20
Fixed versions2.41-11
Vendor guidance

CBL-Mariner Releases Release Notes

Before you act

Start with the vendor's bulletin.

We normalize the fields that vendors publish so you can search and compare advisories in one place. We do not replace the original bulletin or turn a product-name match into proof that a system is vulnerable.

Confirm the installed product and version, read the linked vendor guidance, and test the recommended update or mitigation through your normal change process.

How we check our sources