Back to vendor advisories
Microsoft Security Response CenterCVE-2025-38264

nvme-tcp: sanitize request list handling

MediumVendor CVSS 7.1 / 10 1 CVE Published Sep 3, 2025 at 11:24 PM UTC

Summary

Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?

One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information.

If impact to additional products is identified, we will update the CVE to reflect this.

Products covered

  • azl3 kernel 6.6.112.1-2 on Azure Linux 3.0

  • azl3 kernel 6.6.117.1-1 on Azure Linux 3.0

  • azl3 kernel 6.6.119.3-3 on Azure Linux 3.0

  • azl3 kernel 6.6.121.1-1 on Azure Linux 3.0

  • cbl2 kernel 5.15.200.1-1 on CBL Mariner 2.0

  • cbl2 kernel 5.15.202.1-1 on CBL Mariner 2.0

  • azl3 kernel 6.6.134.1-2 on Azure Linux 3.0

  • cbl2 kernel 5.15.202.1-1

Show 15 more products
  • cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0

  • cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0

  • azl3 kernel 6.6.119.3-1 on Azure Linux 3.0

  • azl3 kernel 6.6.126.1-1 on Azure Linux 3.0

  • azl3 kernel 6.6.130.1-3 on Azure Linux 3.0

  • azl3 kernel 6.6.137.1-2 on Azure Linux 3.0

  • azl3 kernel 6.6.138.1-1 on Azure Linux 3.0

  • azl3 kernel 6.6.139.1-1 on Azure Linux 3.0

  • azl3 kernel 6.6.141.1-1 on Azure Linux 3.0

  • azl3 kernel 6.6.143.1-1 on Azure Linux 3.0

  • azl3 kernel 6.6.144.1-1 on Azure Linux 3.0

  • azl3 kernel 6.6.145.2-1 on Azure Linux 3.0

  • azl3 kernel 6.6.150.1-1 on Azure Linux 3.0

  • azl3 kernel 6.6.152.1-1 on Azure Linux 3.0

  • azl3 kernel 6.6.157.1-1 on Azure Linux 3.0

Remediation

Release Notes

CVEs in this advisory 1

Update history

What changed in later vendor updates

SecurityAlert records field-level changes from the point we begin following a bulletin. Earlier vendor changes may not have a field-by-field record.

    • The vendor changed the advisory's last-updated date.

Updates

  1. Published by Microsoft Security Response Center

    The publication date reported by the vendor.

  2. Added to SecurityAlert

    We collected the advisory from the official source.

  3. Updated by Microsoft Security Response Center

    The vendor changed the advisory after it was first published.

  4. Confirmed at the source

    Our collector saw this advisory during a later source check.