<?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 the Linux Kernel RT (Live Patch 11 for SUSE Linux Enterprise Micro 6.0)</DocumentTitle>
  <DocumentType>SUSE Patch</DocumentType>
  <DocumentPublisher Type="Vendor">
    <ContactDetails>security@suse.de</ContactDetails>
    <IssuingAuthority>SUSE Security Team</IssuingAuthority>
  </DocumentPublisher>
  <DocumentTracking>
    <Identification>
      <ID>SUSE-SU-2026:20254-1</ID>
    </Identification>
    <Status>Final</Status>
    <Version>1</Version>
    <RevisionHistory>
      <Revision>
        <Number>1</Number>
        <Date>2026-01-19T15:31:57Z</Date>
        <Description>current</Description>
      </Revision>
    </RevisionHistory>
    <InitialReleaseDate>2026-01-19T15:31:57Z</InitialReleaseDate>
    <CurrentReleaseDate>2026-01-19T15:31:57Z</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 the Linux Kernel RT (Live Patch 11 for SUSE Linux Enterprise Micro 6.0)</Note>
    <Note Title="Details" Type="General" Ordinal="2" xml:lang="en">
This update for the SUSE Linux Enterprise kernel 6.4.0-32.1 fixes various security issues

The following security issues were fixed:

- CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251787).
- CVE-2025-38608: bpf, ktls: Fix data corruption when using bpf_msg_pop_data() in ktls (bsc#1248670).
- CVE-2025-39682: tls: fix handling of zero-length records on the rx_list (bsc#1250192).
- CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253437).
</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-SLE-Micro-6.0-kernel-239</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/2026/suse-su-202620254-1/</URL>
      <Description>Link for SUSE-SU-2026:20254-1</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://lists.suse.com/pipermail/sle-security-updates/2026-February/024229.html</URL>
      <Description>E-Mail link for SUSE-SU-2026:20254-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/1248670</URL>
      <Description>SUSE Bug 1248670</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1250192</URL>
      <Description>SUSE Bug 1250192</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1251787</URL>
      <Description>SUSE Bug 1251787</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1253437</URL>
      <Description>SUSE Bug 1253437</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2023-53676/</URL>
      <Description>SUSE CVE CVE-2023-53676 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-38608/</URL>
      <Description>SUSE CVE CVE-2025-38608 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-39682/</URL>
      <Description>SUSE CVE CVE-2025-39682 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-40204/</URL>
      <Description>SUSE CVE CVE-2025-40204 page</Description>
    </Reference>
  </DocumentReferences>
  <ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
    <Branch Type="Product Family" Name="SUSE Linux Micro 6.0">
      <Branch Type="Product Name" Name="SUSE Linux Micro 6.0">
        <FullProductName ProductID="SUSE Linux Micro 6.0" CPE="cpe:/o:suse:sl-micro:6.0">SUSE Linux Micro 6.0</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Version" Name="kernel-livepatch-6_4_0-35-rt-5-1.1">
      <FullProductName ProductID="kernel-livepatch-6_4_0-35-rt-5-1.1">kernel-livepatch-6_4_0-35-rt-5-1.1</FullProductName>
    </Branch>
    <Relationship ProductReference="kernel-livepatch-6_4_0-35-rt-5-1.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Micro 6.0">
      <FullProductName ProductID="SUSE Linux Micro 6.0:kernel-livepatch-6_4_0-35-rt-5-1.1">kernel-livepatch-6_4_0-35-rt-5-1.1 as a component of SUSE Linux Micro 6.0</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">In the Linux kernel, the following vulnerability has been resolved:

scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show()

The function lio_target_nacl_info_show() uses sprintf() in a loop to print
details for every iSCSI connection in a session without checking for the
buffer length. With enough iSCSI connections it's possible to overflow the
buffer provided by configfs and corrupt the memory.

This patch replaces sprintf() with sysfs_emit_at() that checks for buffer
boundries.</Note>
    </Notes>
    <CVE>CVE-2023-53676</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Micro 6.0:kernel-livepatch-6_4_0-35-rt-5-1.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/2026/suse-su-202620254-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2023-53676.html</URL>
        <Description>CVE-2023-53676</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1251786</URL>
        <Description>SUSE Bug 1251786</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1251787</URL>
        <Description>SUSE Bug 1251787</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">In the Linux kernel, the following vulnerability has been resolved:

bpf, ktls: Fix data corruption when using bpf_msg_pop_data() in ktls

When sending plaintext data, we initially calculated the corresponding
ciphertext length. However, if we later reduced the plaintext data length
via socket policy, we failed to recalculate the ciphertext length.

This results in transmitting buffers containing uninitialized data during
ciphertext transmission.

This causes uninitialized bytes to be appended after a complete
"Application Data" packet, leading to errors on the receiving end when
parsing TLS record.</Note>
    </Notes>
    <CVE>CVE-2025-38608</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Micro 6.0:kernel-livepatch-6_4_0-35-rt-5-1.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/2026/suse-su-202620254-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-38608.html</URL>
        <Description>CVE-2025-38608</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1248338</URL>
        <Description>SUSE Bug 1248338</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1248670</URL>
        <Description>SUSE Bug 1248670</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="3">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:

tls: fix handling of zero-length records on the rx_list

Each recvmsg() call must process either
 - only contiguous DATA records (any number of them)
 - one non-DATA record

If the next record has different type than what has already been
processed we break out of the main processing loop. If the record
has already been decrypted (which may be the case for TLS 1.3 where
we don't know type until decryption) we queue the pending record
to the rx_list. Next recvmsg() will pick it up from there.

Queuing the skb to rx_list after zero-copy decrypt is not possible,
since in that case we decrypted directly to the user space buffer,
and we don't have an skb to queue (darg.skb points to the ciphertext
skb for access to metadata like length).

Only data records are allowed zero-copy, and we break the processing
loop after each non-data record. So we should never zero-copy and
then find out that the record type has changed. The corner case
we missed is when the initial record comes from rx_list, and it's
zero length.</Note>
    </Notes>
    <CVE>CVE-2025-39682</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Micro 6.0:kernel-livepatch-6_4_0-35-rt-5-1.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/2026/suse-su-202620254-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-39682.html</URL>
        <Description>CVE-2025-39682</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1249284</URL>
        <Description>SUSE Bug 1249284</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1250192</URL>
        <Description>SUSE Bug 1250192</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="4">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:

sctp: Fix MAC comparison to be constant-time

To prevent timing attacks, MACs need to be compared in constant time.
Use the appropriate helper function for this.</Note>
    </Notes>
    <CVE>CVE-2025-40204</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Micro 6.0:kernel-livepatch-6_4_0-35-rt-5-1.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/2026/suse-su-202620254-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-40204.html</URL>
        <Description>CVE-2025-40204</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1253436</URL>
        <Description>SUSE Bug 1253436</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1253437</URL>
        <Description>SUSE Bug 1253437</Description>
      </Reference>
    </References>
  </Vulnerability>
</cvrfdoc>
