<?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</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:0152-1</ID>
    </Identification>
    <Status>Final</Status>
    <Version>1</Version>
    <RevisionHistory>
      <Revision>
        <Number>1</Number>
        <Date>2025-01-17T09:13:58Z</Date>
        <Description>current</Description>
      </Revision>
    </RevisionHistory>
    <InitialReleaseDate>2025-01-17T09:13:58Z</InitialReleaseDate>
    <CurrentReleaseDate>2025-01-17T09:13:58Z</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</Note>
    <Note Title="Details" Type="General" Ordinal="2" xml:lang="en">
The SUSE Linux Enterprise 11 SP4 kernel was updated to receive various security bugfixes.


The following security bugs were fixed:

- CVE-2017-14051: scsi/qla2xxx: Fix an integer overflow in sysfs code. (bsc#1056588)
- CVE-2024-53146: NFSD: Prevent a potential integer overflow (bsc#1234853).
- CVE-2024-53156: wifi: ath9k: add range check for conn_rsp_epid in htc_connect_service() (bsc#1234846).
- CVE-2024-53173: NFSv4.0: Fix a use-after-free problem in the asynchronous open() (bsc#1234891).
- CVE-2024-53239: ALSA: 6fire: Release resources at card release (bsc#1235054).
- CVE-2024-56539: wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_config_scan() (bsc#1234963).
- CVE-2024-56548: hfsplus: do not query the device logical block size multiple times (bsc#1235073).
- CVE-2024-56598: jfs: array-index-out-of-bounds fix in dtReadFirst (bsc#1235220).
- CVE-2024-56604: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() (bsc#1235056).
- CVE-2024-56605: Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create() (bsc#1235061).
- CVE-2024-56619: nilfs2: fix potential out-of-bounds memory access in nilfs_find_entry() (bsc#1235224).

The following non-security bugs were fixed:

- Enable CONFIG_FIRMWARE_SIG ()
- r8169: check ALDPS bit and disable it if enabled for the 8168g (bnc#845352).
- rpm/kernel-binary.spec.in: Remove obsolete ext4-writeable. Needs to be handled differently. (bnc#830822)
</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-152,SUSE-SLE-SERVER-11-SP4-LTSS-EXTREME-CORE-2025-152</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-20250152-1/</URL>
      <Description>Link for SUSE-SU-2025:0152-1</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://lists.suse.com/pipermail/sle-security-updates/2025-January/020152.html</URL>
      <Description>E-Mail link for SUSE-SU-2025:0152-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/1027565</URL>
      <Description>SUSE Bug 1027565</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1056588</URL>
      <Description>SUSE Bug 1056588</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1059525</URL>
      <Description>SUSE Bug 1059525</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1202346</URL>
      <Description>SUSE Bug 1202346</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1227985</URL>
      <Description>SUSE Bug 1227985</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1234846</URL>
      <Description>SUSE Bug 1234846</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1234853</URL>
      <Description>SUSE Bug 1234853</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1234891</URL>
      <Description>SUSE Bug 1234891</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1234963</URL>
      <Description>SUSE Bug 1234963</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1235054</URL>
      <Description>SUSE Bug 1235054</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1235056</URL>
      <Description>SUSE Bug 1235056</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1235061</URL>
      <Description>SUSE Bug 1235061</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1235073</URL>
      <Description>SUSE Bug 1235073</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1235220</URL>
      <Description>SUSE Bug 1235220</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1235224</URL>
      <Description>SUSE Bug 1235224</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2017-1000253/</URL>
      <Description>SUSE CVE CVE-2017-1000253 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2017-14051/</URL>
      <Description>SUSE CVE CVE-2017-14051 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2017-2636/</URL>
      <Description>SUSE CVE CVE-2017-2636 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2022-20368/</URL>
      <Description>SUSE CVE CVE-2022-20368 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2022-48839/</URL>
      <Description>SUSE CVE CVE-2022-48839 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-53146/</URL>
      <Description>SUSE CVE CVE-2024-53146 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-53156/</URL>
      <Description>SUSE CVE CVE-2024-53156 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-53173/</URL>
      <Description>SUSE CVE CVE-2024-53173 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-53239/</URL>
      <Description>SUSE CVE CVE-2024-53239 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-56539/</URL>
      <Description>SUSE CVE CVE-2024-56539 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-56548/</URL>
      <Description>SUSE CVE CVE-2024-56548 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-56598/</URL>
      <Description>SUSE CVE CVE-2024-56598 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-56604/</URL>
      <Description>SUSE CVE CVE-2024-56604 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-56605/</URL>
      <Description>SUSE CVE CVE-2024-56605 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-56619/</URL>
      <Description>SUSE CVE CVE-2024-56619 page</Description>
    </Reference>
  </DocumentReferences>
  <ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
    <Branch Type="Product Family" Name="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <Branch Type="Product Name" Name="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
        <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE" CPE="cpe:/o:suse:suse_sles_ltss-extreme-core:11:sp4">SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Version" Name="kernel-debug-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-debug-3.0.101-108.174.1">kernel-debug-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-debug-base-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-debug-base-3.0.101-108.174.1">kernel-debug-base-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-debug-devel-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-debug-devel-3.0.101-108.174.1">kernel-debug-devel-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-debug-extra-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-debug-extra-3.0.101-108.174.1">kernel-debug-extra-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-debug-hmac-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-debug-hmac-3.0.101-108.174.1">kernel-debug-hmac-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-default-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-default-3.0.101-108.174.1">kernel-default-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-default-base-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-default-base-3.0.101-108.174.1">kernel-default-base-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-default-devel-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-default-devel-3.0.101-108.174.1">kernel-default-devel-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-default-extra-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-default-extra-3.0.101-108.174.1">kernel-default-extra-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-default-hmac-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-default-hmac-3.0.101-108.174.1">kernel-default-hmac-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-docs-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-docs-3.0.101-108.174.1">kernel-docs-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-ec2-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-ec2-3.0.101-108.174.1">kernel-ec2-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-ec2-base-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-ec2-base-3.0.101-108.174.1">kernel-ec2-base-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-ec2-devel-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-ec2-devel-3.0.101-108.174.1">kernel-ec2-devel-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-ec2-extra-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-ec2-extra-3.0.101-108.174.1">kernel-ec2-extra-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-ec2-hmac-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-ec2-hmac-3.0.101-108.174.1">kernel-ec2-hmac-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-pae-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-pae-3.0.101-108.174.1">kernel-pae-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-pae-base-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-pae-base-3.0.101-108.174.1">kernel-pae-base-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-pae-devel-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-pae-devel-3.0.101-108.174.1">kernel-pae-devel-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-pae-extra-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-pae-extra-3.0.101-108.174.1">kernel-pae-extra-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-pae-hmac-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-pae-hmac-3.0.101-108.174.1">kernel-pae-hmac-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-source-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-source-3.0.101-108.174.1">kernel-source-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-source-vanilla-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-source-vanilla-3.0.101-108.174.1">kernel-source-vanilla-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-syms-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-syms-3.0.101-108.174.1">kernel-syms-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-trace-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-trace-3.0.101-108.174.1">kernel-trace-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-trace-base-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-trace-base-3.0.101-108.174.1">kernel-trace-base-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-trace-devel-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-trace-devel-3.0.101-108.174.1">kernel-trace-devel-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-trace-extra-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-trace-extra-3.0.101-108.174.1">kernel-trace-extra-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-trace-hmac-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-trace-hmac-3.0.101-108.174.1">kernel-trace-hmac-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-vanilla-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-vanilla-3.0.101-108.174.1">kernel-vanilla-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-vanilla-base-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-vanilla-base-3.0.101-108.174.1">kernel-vanilla-base-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-vanilla-devel-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-vanilla-devel-3.0.101-108.174.1">kernel-vanilla-devel-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-vanilla-hmac-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-vanilla-hmac-3.0.101-108.174.1">kernel-vanilla-hmac-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-xen-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-xen-3.0.101-108.174.1">kernel-xen-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-xen-base-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-xen-base-3.0.101-108.174.1">kernel-xen-base-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-xen-devel-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-xen-devel-3.0.101-108.174.1">kernel-xen-devel-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-xen-extra-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-xen-extra-3.0.101-108.174.1">kernel-xen-extra-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-xen-hmac-3.0.101-108.174.1">
      <FullProductName ProductID="kernel-xen-hmac-3.0.101-108.174.1">kernel-xen-hmac-3.0.101-108.174.1</FullProductName>
    </Branch>
    <Relationship ProductReference="kernel-default-3.0.101-108.174.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1">kernel-default-3.0.101-108.174.1 as a component of SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-default-base-3.0.101-108.174.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1">kernel-default-base-3.0.101-108.174.1 as a component of SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-default-devel-3.0.101-108.174.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1">kernel-default-devel-3.0.101-108.174.1 as a component of SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-ec2-3.0.101-108.174.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1">kernel-ec2-3.0.101-108.174.1 as a component of SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-ec2-base-3.0.101-108.174.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1">kernel-ec2-base-3.0.101-108.174.1 as a component of SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-ec2-devel-3.0.101-108.174.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1">kernel-ec2-devel-3.0.101-108.174.1 as a component of SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-source-3.0.101-108.174.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1">kernel-source-3.0.101-108.174.1 as a component of SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-syms-3.0.101-108.174.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1">kernel-syms-3.0.101-108.174.1 as a component of SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-trace-3.0.101-108.174.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1">kernel-trace-3.0.101-108.174.1 as a component of SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-trace-base-3.0.101-108.174.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1">kernel-trace-base-3.0.101-108.174.1 as a component of SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-trace-devel-3.0.101-108.174.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1">kernel-trace-devel-3.0.101-108.174.1 as a component of SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-xen-3.0.101-108.174.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1">kernel-xen-3.0.101-108.174.1 as a component of SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-xen-base-3.0.101-108.174.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1">kernel-xen-base-3.0.101-108.174.1 as a component of SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-xen-devel-3.0.101-108.174.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.1">kernel-xen-devel-3.0.101-108.174.1 as a component of SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE</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">Linux distributions that have not patched their long-term kernels with https://git.kernel.org/linus/a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (committed on April 14, 2015). This kernel vulnerability was fixed in April 2015 by commit a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (backported to Linux 3.10.77 in May 2015), but it was not recognized as a security threat. With CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE enabled, and a normal top-down address allocation strategy, load_elf_binary() will attempt to map a PIE binary into an address range immediately below mm-&gt;mmap_base. Unfortunately, load_elf_ binary() does not take account of the need to allocate sufficient space for the entire binary which means that, while the first PT_LOAD segment is mapped below mm-&gt;mmap_base, the subsequent PT_LOAD segment(s) end up being mapped above mm-&gt;mmap_base into the are that is supposed to be the "gap" between the stack and the binary.</Note>
    </Notes>
    <CVE>CVE-2017-1000253</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>important</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>7.2</BaseScore>
        <Vector>AV:L/AC:L/Au:N/C:C/I:C/A:C</Vector>
      </ScoreSet>
      <ScoreSet>
        <BaseScore>7.2</BaseScore>
        <Vector>AV:L/AC:L/Au:N/C:C/I:C/A:C</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2017-1000253.html</URL>
        <Description>CVE-2017-1000253</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1059525</URL>
        <Description>SUSE Bug 1059525</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1061680</URL>
        <Description>SUSE Bug 1061680</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1063607</URL>
        <Description>SUSE Bug 1063607</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1071943</URL>
        <Description>SUSE Bug 1071943</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1072204</URL>
        <Description>SUSE Bug 1072204</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1075506</URL>
        <Description>SUSE Bug 1075506</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1115893</URL>
        <Description>SUSE Bug 1115893</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1149729</URL>
        <Description>SUSE Bug 1149729</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">An integer overflow in the qla2x00_sysfs_write_optrom_ctl function in drivers/scsi/qla2xxx/qla_attr.c in the Linux kernel through 4.12.10 allows local users to cause a denial of service (memory corruption and system crash) by leveraging root access.</Note>
    </Notes>
    <CVE>CVE-2017-14051</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>6</BaseScore>
        <Vector>AV:L/AC:H/Au:S/C:C/I:C/A:C</Vector>
      </ScoreSet>
      <ScoreSet>
        <BaseScore>4.9</BaseScore>
        <Vector>AV:L/AC:L/Au:N/C:N/I:N/A:C</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2017-14051.html</URL>
        <Description>CVE-2017-14051</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1056588</URL>
        <Description>SUSE Bug 1056588</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">Race condition in drivers/tty/n_hdlc.c in the Linux kernel through 4.10.1 allows local users to gain privileges or cause a denial of service (double free) by setting the HDLC line discipline.</Note>
    </Notes>
    <CVE>CVE-2017-2636</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>6</BaseScore>
        <Vector>AV:L/AC:H/Au:S/C:C/I:C/A:C</Vector>
      </ScoreSet>
      <ScoreSet>
        <BaseScore>6.9</BaseScore>
        <Vector>AV:L/AC:M/Au:N/C:C/I:C/A:C</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2017-2636.html</URL>
        <Description>CVE-2017-2636</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1027565</URL>
        <Description>SUSE Bug 1027565</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1027575</URL>
        <Description>SUSE Bug 1027575</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1028372</URL>
        <Description>SUSE Bug 1028372</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1115893</URL>
        <Description>SUSE Bug 1115893</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">Product: AndroidVersions: Android kernelAndroid ID: A-224546354References: Upstream kernel</Note>
    </Notes>
    <CVE>CVE-2022-20368</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2022-20368.html</URL>
        <Description>CVE-2022-20368</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1202346</URL>
        <Description>SUSE Bug 1202346</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1212311</URL>
        <Description>SUSE Bug 1212311</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="5">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:

net/packet: fix slab-out-of-bounds access in packet_recvmsg()

syzbot found that when an AF_PACKET socket is using PACKET_COPY_THRESH
and mmap operations, tpacket_rcv() is queueing skbs with
garbage in skb-&gt;cb[], triggering a too big copy [1]

Presumably, users of af_packet using mmap() already gets correct
metadata from the mapped buffer, we can simply make sure
to clear 12 bytes that might be copied to user space later.

BUG: KASAN: stack-out-of-bounds in memcpy include/linux/fortify-string.h:225 [inline]
BUG: KASAN: stack-out-of-bounds in packet_recvmsg+0x56c/0x1150 net/packet/af_packet.c:3489
Write of size 165 at addr ffffc9000385fb78 by task syz-executor233/3631

CPU: 0 PID: 3631 Comm: syz-executor233 Not tainted 5.17.0-rc7-syzkaller-02396-g0b3660695e80 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 &lt;TASK&gt;
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 print_address_description.constprop.0.cold+0xf/0x336 mm/kasan/report.c:255
 __kasan_report mm/kasan/report.c:442 [inline]
 kasan_report.cold+0x83/0xdf mm/kasan/report.c:459
 check_region_inline mm/kasan/generic.c:183 [inline]
 kasan_check_range+0x13d/0x180 mm/kasan/generic.c:189
 memcpy+0x39/0x60 mm/kasan/shadow.c:66
 memcpy include/linux/fortify-string.h:225 [inline]
 packet_recvmsg+0x56c/0x1150 net/packet/af_packet.c:3489
 sock_recvmsg_nosec net/socket.c:948 [inline]
 sock_recvmsg net/socket.c:966 [inline]
 sock_recvmsg net/socket.c:962 [inline]
 ____sys_recvmsg+0x2c4/0x600 net/socket.c:2632
 ___sys_recvmsg+0x127/0x200 net/socket.c:2674
 __sys_recvmsg+0xe2/0x1a0 net/socket.c:2704
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7fdfd5954c29
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 41 15 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 &lt;48&gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcf8e71e48 EFLAGS: 00000246 ORIG_RAX: 000000000000002f
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fdfd5954c29
RDX: 0000000000000000 RSI: 0000000020000500 RDI: 0000000000000005
RBP: 0000000000000000 R08: 000000000000000d R09: 000000000000000d
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffcf8e71e60
R13: 00000000000f4240 R14: 000000000000c1ff R15: 00007ffcf8e71e54
 &lt;/TASK&gt;

addr ffffc9000385fb78 is located in stack of task syz-executor233/3631 at offset 32 in frame:
 ____sys_recvmsg+0x0/0x600 include/linux/uio.h:246

this frame has 1 object:
 [32, 160) 'addr'

Memory state around the buggy address:
 ffffc9000385fa80: 00 04 f3 f3 f3 f3 f3 00 00 00 00 00 00 00 00 00
 ffffc9000385fb00: 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00
&gt;ffffc9000385fb80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f3
                                                                ^
 ffffc9000385fc00: f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 f1
 ffffc9000385fc80: f1 f1 f1 00 f2 f2 f2 00 f2 f2 f2 00 00 00 00 00
==================================================================</Note>
    </Notes>
    <CVE>CVE-2022-48839</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2022-48839.html</URL>
        <Description>CVE-2022-48839</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1227985</URL>
        <Description>SUSE Bug 1227985</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="6">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:

NFSD: Prevent a potential integer overflow

If the tag length is &gt;= U32_MAX - 3 then the "length + 4" addition
can result in an integer overflow. Address this by splitting the
decoding into several steps so that decode_cb_compound4res() does
not have to perform arithmetic on the unsafe length value.</Note>
    </Notes>
    <CVE>CVE-2024-53146</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-53146.html</URL>
        <Description>CVE-2024-53146</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234853</URL>
        <Description>SUSE Bug 1234853</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234854</URL>
        <Description>SUSE Bug 1234854</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="7">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:

wifi: ath9k: add range check for conn_rsp_epid in htc_connect_service()

I found the following bug in my fuzzer:

  UBSAN: array-index-out-of-bounds in drivers/net/wireless/ath/ath9k/htc_hst.c:26:51
  index 255 is out of range for type 'htc_endpoint [22]'
  CPU: 0 UID: 0 PID: 8 Comm: kworker/0:0 Not tainted 6.11.0-rc6-dirty #14
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
  Workqueue: events request_firmware_work_func
  Call Trace:
   &lt;TASK&gt;
   dump_stack_lvl+0x180/0x1b0
   __ubsan_handle_out_of_bounds+0xd4/0x130
   htc_issue_send.constprop.0+0x20c/0x230
   ? _raw_spin_unlock_irqrestore+0x3c/0x70
   ath9k_wmi_cmd+0x41d/0x610
   ? mark_held_locks+0x9f/0xe0
   ...

Since this bug has been confirmed to be caused by insufficient verification
of conn_rsp_epid, I think it would be appropriate to add a range check for
conn_rsp_epid to htc_connect_service() to prevent the bug from occurring.</Note>
    </Notes>
    <CVE>CVE-2024-53156</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-53156.html</URL>
        <Description>CVE-2024-53156</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234846</URL>
        <Description>SUSE Bug 1234846</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234847</URL>
        <Description>SUSE Bug 1234847</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234853</URL>
        <Description>SUSE Bug 1234853</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="8">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:

NFSv4.0: Fix a use-after-free problem in the asynchronous open()

Yang Erkun reports that when two threads are opening files at the same
time, and are forced to abort before a reply is seen, then the call to
nfs_release_seqid() in nfs4_opendata_free() can result in a
use-after-free of the pointer to the defunct rpc task of the other
thread.
The fix is to ensure that if the RPC call is aborted before the call to
nfs_wait_on_sequence() is complete, then we must call nfs_release_seqid()
in nfs4_open_release() before the rpc_task is freed.</Note>
    </Notes>
    <CVE>CVE-2024-53173</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-53173.html</URL>
        <Description>CVE-2024-53173</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234853</URL>
        <Description>SUSE Bug 1234853</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234891</URL>
        <Description>SUSE Bug 1234891</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234892</URL>
        <Description>SUSE Bug 1234892</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="9">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:

ALSA: 6fire: Release resources at card release

The current 6fire code tries to release the resources right after the
call of usb6fire_chip_abort().  But at this moment, the card object
might be still in use (as we're calling snd_card_free_when_closed()).

For avoid potential UAFs, move the release of resources to the card's
private_free instead of the manual call of usb6fire_chip_destroy() at
the USB disconnect callback.</Note>
    </Notes>
    <CVE>CVE-2024-53239</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-53239.html</URL>
        <Description>CVE-2024-53239</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234853</URL>
        <Description>SUSE Bug 1234853</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1235054</URL>
        <Description>SUSE Bug 1235054</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1235055</URL>
        <Description>SUSE Bug 1235055</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="10">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:

wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_config_scan()

Replace one-element array with a flexible-array member in `struct
mwifiex_ie_types_wildcard_ssid_params` to fix the following warning
on a MT8173 Chromebook (mt8173-elm-hana):

[  356.775250] ------------[ cut here ]------------
[  356.784543] memcpy: detected field-spanning write (size 6) of single field "wildcard_ssid_tlv-&gt;ssid" at drivers/net/wireless/marvell/mwifiex/scan.c:904 (size 1)
[  356.813403] WARNING: CPU: 3 PID: 742 at drivers/net/wireless/marvell/mwifiex/scan.c:904 mwifiex_scan_networks+0x4fc/0xf28 [mwifiex]

The "(size 6)" above is exactly the length of the SSID of the network
this device was connected to. The source of the warning looks like:

    ssid_len = user_scan_in-&gt;ssid_list[i].ssid_len;
    [...]
    memcpy(wildcard_ssid_tlv-&gt;ssid,
           user_scan_in-&gt;ssid_list[i].ssid, ssid_len);

There is a #define WILDCARD_SSID_TLV_MAX_SIZE that uses sizeof() on this
struct, but it already didn't account for the size of the one-element
array, so it doesn't need to be changed.</Note>
    </Notes>
    <CVE>CVE-2024-56539</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-56539.html</URL>
        <Description>CVE-2024-56539</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234853</URL>
        <Description>SUSE Bug 1234853</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234963</URL>
        <Description>SUSE Bug 1234963</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234964</URL>
        <Description>SUSE Bug 1234964</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="11">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:

hfsplus: don't query the device logical block size multiple times

Devices block sizes may change. One of these cases is a loop device by
using ioctl LOOP_SET_BLOCK_SIZE.

While this may cause other issues like IO being rejected, in the case of
hfsplus, it will allocate a block by using that size and potentially write
out-of-bounds when hfsplus_read_wrapper calls hfsplus_submit_bio and the
latter function reads a different io_size.

Using a new min_io_size initally set to sb_min_blocksize works for the
purposes of the original fix, since it will be set to the max between
HFSPLUS_SECTOR_SIZE and the first seen logical block size. We still use the
max between HFSPLUS_SECTOR_SIZE and min_io_size in case the latter is not
initialized.

Tested by mounting an hfsplus filesystem with loop block sizes 512, 1024
and 4096.

The produced KASAN report before the fix looks like this:

[  419.944641] ==================================================================
[  419.945655] BUG: KASAN: slab-use-after-free in hfsplus_read_wrapper+0x659/0xa0a
[  419.946703] Read of size 2 at addr ffff88800721fc00 by task repro/10678
[  419.947612]
[  419.947846] CPU: 0 UID: 0 PID: 10678 Comm: repro Not tainted 6.12.0-rc5-00008-gdf56e0f2f3ca #84
[  419.949007] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
[  419.950035] Call Trace:
[  419.950384]  &lt;TASK&gt;
[  419.950676]  dump_stack_lvl+0x57/0x78
[  419.951212]  ? hfsplus_read_wrapper+0x659/0xa0a
[  419.951830]  print_report+0x14c/0x49e
[  419.952361]  ? __virt_addr_valid+0x267/0x278
[  419.952979]  ? kmem_cache_debug_flags+0xc/0x1d
[  419.953561]  ? hfsplus_read_wrapper+0x659/0xa0a
[  419.954231]  kasan_report+0x89/0xb0
[  419.954748]  ? hfsplus_read_wrapper+0x659/0xa0a
[  419.955367]  hfsplus_read_wrapper+0x659/0xa0a
[  419.955948]  ? __pfx_hfsplus_read_wrapper+0x10/0x10
[  419.956618]  ? do_raw_spin_unlock+0x59/0x1a9
[  419.957214]  ? _raw_spin_unlock+0x1a/0x2e
[  419.957772]  hfsplus_fill_super+0x348/0x1590
[  419.958355]  ? hlock_class+0x4c/0x109
[  419.958867]  ? __pfx_hfsplus_fill_super+0x10/0x10
[  419.959499]  ? __pfx_string+0x10/0x10
[  419.960006]  ? lock_acquire+0x3e2/0x454
[  419.960532]  ? bdev_name.constprop.0+0xce/0x243
[  419.961129]  ? __pfx_bdev_name.constprop.0+0x10/0x10
[  419.961799]  ? pointer+0x3f0/0x62f
[  419.962277]  ? __pfx_pointer+0x10/0x10
[  419.962761]  ? vsnprintf+0x6c4/0xfba
[  419.963178]  ? __pfx_vsnprintf+0x10/0x10
[  419.963621]  ? setup_bdev_super+0x376/0x3b3
[  419.964029]  ? snprintf+0x9d/0xd2
[  419.964344]  ? __pfx_snprintf+0x10/0x10
[  419.964675]  ? lock_acquired+0x45c/0x5e9
[  419.965016]  ? set_blocksize+0x139/0x1c1
[  419.965381]  ? sb_set_blocksize+0x6d/0xae
[  419.965742]  ? __pfx_hfsplus_fill_super+0x10/0x10
[  419.966179]  mount_bdev+0x12f/0x1bf
[  419.966512]  ? __pfx_mount_bdev+0x10/0x10
[  419.966886]  ? vfs_parse_fs_string+0xce/0x111
[  419.967293]  ? __pfx_vfs_parse_fs_string+0x10/0x10
[  419.967702]  ? __pfx_hfsplus_mount+0x10/0x10
[  419.968073]  legacy_get_tree+0x104/0x178
[  419.968414]  vfs_get_tree+0x86/0x296
[  419.968751]  path_mount+0xba3/0xd0b
[  419.969157]  ? __pfx_path_mount+0x10/0x10
[  419.969594]  ? kmem_cache_free+0x1e2/0x260
[  419.970311]  do_mount+0x99/0xe0
[  419.970630]  ? __pfx_do_mount+0x10/0x10
[  419.971008]  __do_sys_mount+0x199/0x1c9
[  419.971397]  do_syscall_64+0xd0/0x135
[  419.971761]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[  419.972233] RIP: 0033:0x7c3cb812972e
[  419.972564] Code: 48 8b 0d f5 46 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 &lt;48&gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d c2 46 0d 00 f7 d8 64 89 01 48
[  419.974371] RSP: 002b:00007ffe30632548 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
[  419.975048] RAX: ffffffffffffffda RBX: 00007ffe306328d8 RCX: 00007c3cb812972e
[  419.975701] RDX: 0000000020000000 RSI: 0000000020000c80 RDI:
---truncated---</Note>
    </Notes>
    <CVE>CVE-2024-56548</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-56548.html</URL>
        <Description>CVE-2024-56548</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234853</URL>
        <Description>SUSE Bug 1234853</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1235073</URL>
        <Description>SUSE Bug 1235073</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1235074</URL>
        <Description>SUSE Bug 1235074</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="12">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:

jfs: array-index-out-of-bounds fix in dtReadFirst

The value of stbl can be sometimes out of bounds due
to a bad filesystem. Added a check with appopriate return
of error code in that case.</Note>
    </Notes>
    <CVE>CVE-2024-56598</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-56598.html</URL>
        <Description>CVE-2024-56598</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1235220</URL>
        <Description>SUSE Bug 1235220</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1235221</URL>
        <Description>SUSE Bug 1235221</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="13">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc()

bt_sock_alloc() attaches allocated sk object to the provided sock object.
If rfcomm_dlc_alloc() fails, we release the sk object, but leave the
dangling pointer in the sock object, which may cause use-after-free.

Fix this by swapping calls to bt_sock_alloc() and rfcomm_dlc_alloc().</Note>
    </Notes>
    <CVE>CVE-2024-56604</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-56604.html</URL>
        <Description>CVE-2024-56604</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1235056</URL>
        <Description>SUSE Bug 1235056</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1235058</URL>
        <Description>SUSE Bug 1235058</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="14">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create()

bt_sock_alloc() allocates the sk object and attaches it to the provided
sock object. On error l2cap_sock_alloc() frees the sk object, but the
dangling pointer is still attached to the sock object, which may create
use-after-free in other code.</Note>
    </Notes>
    <CVE>CVE-2024-56605</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-56605.html</URL>
        <Description>CVE-2024-56605</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234853</URL>
        <Description>SUSE Bug 1234853</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1235061</URL>
        <Description>SUSE Bug 1235061</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1235062</URL>
        <Description>SUSE Bug 1235062</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="15">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:

nilfs2: fix potential out-of-bounds memory access in nilfs_find_entry()

Syzbot reported that when searching for records in a directory where the
inode's i_size is corrupted and has a large value, memory access outside
the folio/page range may occur, or a use-after-free bug may be detected if
KASAN is enabled.

This is because nilfs_last_byte(), which is called by nilfs_find_entry()
and others to calculate the number of valid bytes of directory data in a
page from i_size and the page index, loses the upper 32 bits of the 64-bit
size information due to an inappropriate type of local variable to which
the i_size value is assigned.

This caused a large byte offset value due to underflow in the end address
calculation in the calling nilfs_find_entry(), resulting in memory access
that exceeds the folio/page size.

Fix this issue by changing the type of the local variable causing the bit
loss from "unsigned int" to "u64".  The return value of nilfs_last_byte()
is also of type "unsigned int", but it is truncated so as not to exceed
PAGE_SIZE and no bit loss occurs, so no change is required.</Note>
    </Notes>
    <CVE>CVE-2024-56619</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-default-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-ec2-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-source-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-syms-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-trace-devel-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-base-3.0.101-108.174.1</ProductID>
        <ProductID>SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE:kernel-xen-devel-3.0.101-108.174.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-20250152-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-56619.html</URL>
        <Description>CVE-2024-56619</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1235224</URL>
        <Description>SUSE Bug 1235224</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1235225</URL>
        <Description>SUSE Bug 1235225</Description>
      </Reference>
    </References>
  </Vulnerability>
</cvrfdoc>
