<?xml version="1.0" encoding="UTF-8"?>
<cvrfdoc xmlns="http://www.icasi.org/CVRF/schema/cvrf/1.1" xmlns:cvrf="http://www.icasi.org/CVRF/schema/cvrf/1.1">
  <DocumentTitle xml:lang="en">Security update for openssl-1_1-livepatches</DocumentTitle>
  <DocumentType>SUSE Patch</DocumentType>
  <DocumentPublisher Type="Vendor">
    <ContactDetails>security@suse.de</ContactDetails>
    <IssuingAuthority>SUSE Security Team</IssuingAuthority>
  </DocumentPublisher>
  <DocumentTracking>
    <Identification>
      <ID>SUSE-SU-2025:03632-1</ID>
    </Identification>
    <Status>Final</Status>
    <Version>1</Version>
    <RevisionHistory>
      <Revision>
        <Number>1</Number>
        <Date>2025-10-17T14:06:17Z</Date>
        <Description>current</Description>
      </Revision>
    </RevisionHistory>
    <InitialReleaseDate>2025-10-17T14:06:17Z</InitialReleaseDate>
    <CurrentReleaseDate>2025-10-17T14:06:17Z</CurrentReleaseDate>
    <Generator>
      <Engine>cve-database/bin/generate-cvrf.pl</Engine>
      <Date>2017-02-24T01:00:00Z</Date>
    </Generator>
  </DocumentTracking>
  <DocumentNotes>
    <Note Title="Topic" Type="Summary" Ordinal="1" xml:lang="en">Security update for openssl-1_1-livepatches</Note>
    <Note Title="Details" Type="General" Ordinal="2" xml:lang="en">This update for openssl-1_1-livepatches fixes the following issues:

- Add livepatch for CVE-2025-9230 (bsc#1250410).

- Use strong externalization for ssl3_setup_read_buffer and
  ssl3_release_read_buffer
- Use strong externalization for ossl_statem_fatal.

- Add livepatch for CVE-2024-4741 (bsc#1225552).

- Drop trigger rules for very old libpulp-tools package.

- Fix building process to include functions of older livepatches
  correctly (bsc#1224458)'.
</Note>
    <Note Title="Terms of Use" Type="Legal Disclaimer" Ordinal="3" xml:lang="en">The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).</Note>
    <Note Title="Patchnames" Type="Details" Ordinal="4" xml:lang="en">SUSE-2025-3632,SUSE-SLE-Module-Live-Patching-15-SP6-2025-3632</Note>
  </DocumentNotes>
  <DocumentDistribution xml:lang="en">Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0)</DocumentDistribution>
  <DocumentReferences>
    <Reference Type="Self">
      <URL>https://www.suse.com/support/update/announcement/2025/suse-su-202503632-1/</URL>
      <Description>Link for SUSE-SU-2025:03632-1</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://lists.suse.com/pipermail/sle-security-updates/2025-October/022927.html</URL>
      <Description>E-Mail link for SUSE-SU-2025:03632-1</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/support/security/rating/</URL>
      <Description>SUSE Security Ratings</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1224458</URL>
      <Description>SUSE Bug 1224458</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1225552</URL>
      <Description>SUSE Bug 1225552</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1250410</URL>
      <Description>SUSE Bug 1250410</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-4741/</URL>
      <Description>SUSE CVE CVE-2024-4741 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-9230/</URL>
      <Description>SUSE CVE CVE-2025-9230 page</Description>
    </Reference>
  </DocumentReferences>
  <ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
    <Branch Type="Product Family" Name="SUSE Linux Enterprise Live Patching 15 SP6">
      <Branch Type="Product Name" Name="SUSE Linux Enterprise Live Patching 15 SP6">
        <FullProductName ProductID="SUSE Linux Enterprise Live Patching 15 SP6" CPE="cpe:/o:suse:sle-module-live-patching:15:sp6">SUSE Linux Enterprise Live Patching 15 SP6</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Version" Name="openssl-1_1-livepatches-0.5-150600.11.3.1">
      <FullProductName ProductID="openssl-1_1-livepatches-0.5-150600.11.3.1">openssl-1_1-livepatches-0.5-150600.11.3.1</FullProductName>
    </Branch>
    <Relationship ProductReference="openssl-1_1-livepatches-0.5-150600.11.3.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Live Patching 15 SP6">
      <FullProductName ProductID="SUSE Linux Enterprise Live Patching 15 SP6:openssl-1_1-livepatches-0.5-150600.11.3.1">openssl-1_1-livepatches-0.5-150600.11.3.1 as a component of SUSE Linux Enterprise Live Patching 15 SP6</FullProductName>
    </Relationship>
  </ProductTree>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="1">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause
memory to be accessed that was previously freed in some situations

Impact summary: A use after free can have a range of potential consequences such
as the corruption of valid data, crashes or execution of arbitrary code.
However, only applications that directly call the SSL_free_buffers function are
affected by this issue. Applications that do not call this function are not
vulnerable. Our investigations indicate that this function is rarely used by
applications.

The SSL_free_buffers function is used to free the internal OpenSSL buffer used
when processing an incoming record from the network. The call is only expected
to succeed if the buffer is not currently in use. However, two scenarios have
been identified where the buffer is freed even when still in use.

The first scenario occurs where a record header has been received from the
network and processed by OpenSSL, but the full record body has not yet arrived.
In this case calling SSL_free_buffers will succeed even though a record has only
been partially processed and the buffer is still in use.

The second scenario occurs where a full record containing application data has
been received and processed by OpenSSL but the application has only read part of
this data. Again a call to SSL_free_buffers will succeed even though the buffer
is still in use.

While these scenarios could occur accidentally during normal operation a
malicious attacker could attempt to engineer a stituation where this occurs.
We are not aware of this issue being actively exploited.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.</Note>
    </Notes>
    <CVE>CVE-2024-4741</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Live Patching 15 SP6:openssl-1_1-livepatches-0.5-150600.11.3.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>important</Description>
      </Threat>
    </Threats>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL>https://www.suse.com/support/update/announcement/2025/suse-su-202503632-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-4741.html</URL>
        <Description>CVE-2024-4741</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1225551</URL>
        <Description>SUSE Bug 1225551</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1225552</URL>
        <Description>SUSE Bug 1225552</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="2">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">Issue summary: An application trying to decrypt CMS messages encrypted using
password based encryption can trigger an out-of-bounds read and write.

Impact summary: This out-of-bounds read may trigger a crash which leads to
Denial of Service for an application. The out-of-bounds write can cause
a memory corruption which can have various consequences including
a Denial of Service or Execution of attacker-supplied code.

Although the consequences of a successful exploit of this vulnerability
could be severe, the probability that the attacker would be able to
perform it is low. Besides, password based (PWRI) encryption support in CMS
messages is very rarely used. For that reason the issue was assessed as
Moderate severity according to our Security Policy.

The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this
issue, as the CMS implementation is outside the OpenSSL FIPS module
boundary.</Note>
    </Notes>
    <CVE>CVE-2025-9230</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Live Patching 15 SP6:openssl-1_1-livepatches-0.5-150600.11.3.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>important</Description>
      </Threat>
    </Threats>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL>https://www.suse.com/support/update/announcement/2025/suse-su-202503632-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-9230.html</URL>
        <Description>CVE-2025-9230</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1250232</URL>
        <Description>SUSE Bug 1250232</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1250410</URL>
        <Description>SUSE Bug 1250410</Description>
      </Reference>
    </References>
  </Vulnerability>
</cvrfdoc>
