<?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:1573-1</ID>
    </Identification>
    <Status>Final</Status>
    <Version>1</Version>
    <RevisionHistory>
      <Revision>
        <Number>1</Number>
        <Date>2025-05-16T16:32:08Z</Date>
        <Description>current</Description>
      </Revision>
    </RevisionHistory>
    <InitialReleaseDate>2025-05-16T16:32:08Z</InitialReleaseDate>
    <CurrentReleaseDate>2025-05-16T16:32:08Z</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 15 SP4 RT kernel was updated to receive various security bugfixes.


The following security bugs were fixed:

- CVE-2025-21726: padata: avoid UAF for reorder_work (bsc#1238865).
- CVE-2025-21785: arm64: cacheinfo: Avoid out-of-bounds write to cacheinfo array (bsc#1238747).
- CVE-2025-21791: vrf: use RCU protection in l3mdev_l3_out() (bsc#1238512).
- CVE-2025-21812: ax25: rcu protect dev-&gt;ax25_ptr (bsc#1238471).
- CVE-2025-22004: net: atm: fix use after free in lec_send() (bsc#1240835).
- CVE-2025-22020: memstick: rtsx_usb_ms: Fix slab-use-after-free in rtsx_usb_ms_drv_remove (bsc#1241280).
- CVE-2025-22029: exec: fix the racy usage of fs_struct-&gt;in_exec (bsc#1241378).
- CVE-2025-22045: x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs (bsc#1241433).
- CVE-2025-22055: net: fix geneve_opt length integer overflow (bsc#1241371).
- CVE-2025-22097: drm/vkms: Fix use after free and double free on init error (bsc#1241541).

The following non-security bugs were fixed:

- scsi: smartpqi: Add ctrl ready timeout module parameter (jsc#PED-1557, bsc#1201855, bsc#1240553).
</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-1573,SUSE-SLE-Micro-5.3-2025-1573,SUSE-SLE-Micro-5.4-2025-1573</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-20251573-1/</URL>
      <Description>Link for SUSE-SU-2025:1573-1</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://lists.suse.com/pipermail/sle-security-updates/2025-May/020836.html</URL>
      <Description>E-Mail link for SUSE-SU-2025:1573-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/1201855</URL>
      <Description>SUSE Bug 1201855</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1230771</URL>
      <Description>SUSE Bug 1230771</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1238471</URL>
      <Description>SUSE Bug 1238471</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1238512</URL>
      <Description>SUSE Bug 1238512</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1238747</URL>
      <Description>SUSE Bug 1238747</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1238865</URL>
      <Description>SUSE Bug 1238865</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1239968</URL>
      <Description>SUSE Bug 1239968</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1240188</URL>
      <Description>SUSE Bug 1240188</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1240195</URL>
      <Description>SUSE Bug 1240195</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1240553</URL>
      <Description>SUSE Bug 1240553</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1240747</URL>
      <Description>SUSE Bug 1240747</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1240835</URL>
      <Description>SUSE Bug 1240835</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1241280</URL>
      <Description>SUSE Bug 1241280</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1241371</URL>
      <Description>SUSE Bug 1241371</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1241378</URL>
      <Description>SUSE Bug 1241378</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1241421</URL>
      <Description>SUSE Bug 1241421</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1241433</URL>
      <Description>SUSE Bug 1241433</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1241541</URL>
      <Description>SUSE Bug 1241541</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2021-47671/</URL>
      <Description>SUSE CVE CVE-2021-47671 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2022-49741/</URL>
      <Description>SUSE CVE CVE-2022-49741 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-46784/</URL>
      <Description>SUSE CVE CVE-2024-46784 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-21726/</URL>
      <Description>SUSE CVE CVE-2025-21726 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-21785/</URL>
      <Description>SUSE CVE CVE-2025-21785 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-21791/</URL>
      <Description>SUSE CVE CVE-2025-21791 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-21812/</URL>
      <Description>SUSE CVE CVE-2025-21812 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-21886/</URL>
      <Description>SUSE CVE CVE-2025-21886 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-22004/</URL>
      <Description>SUSE CVE CVE-2025-22004 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-22020/</URL>
      <Description>SUSE CVE CVE-2025-22020 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-22029/</URL>
      <Description>SUSE CVE CVE-2025-22029 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-22045/</URL>
      <Description>SUSE CVE CVE-2025-22045 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-22055/</URL>
      <Description>SUSE CVE CVE-2025-22055 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-22097/</URL>
      <Description>SUSE CVE CVE-2025-22097 page</Description>
    </Reference>
  </DocumentReferences>
  <ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
    <Branch Type="Product Family" Name="SUSE Linux Enterprise Micro 5.3">
      <Branch Type="Product Name" Name="SUSE Linux Enterprise Micro 5.3">
        <FullProductName ProductID="SUSE Linux Enterprise Micro 5.3" CPE="cpe:/o:suse:sle-micro:5.3">SUSE Linux Enterprise Micro 5.3</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Family" Name="SUSE Linux Enterprise Micro 5.4">
      <Branch Type="Product Name" Name="SUSE Linux Enterprise Micro 5.4">
        <FullProductName ProductID="SUSE Linux Enterprise Micro 5.4" CPE="cpe:/o:suse:sle-micro:5.4">SUSE Linux Enterprise Micro 5.4</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Version" Name="cluster-md-kmp-rt-5.14.21-150400.15.118.1">
      <FullProductName ProductID="cluster-md-kmp-rt-5.14.21-150400.15.118.1">cluster-md-kmp-rt-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="dlm-kmp-rt-5.14.21-150400.15.118.1">
      <FullProductName ProductID="dlm-kmp-rt-5.14.21-150400.15.118.1">dlm-kmp-rt-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="gfs2-kmp-rt-5.14.21-150400.15.118.1">
      <FullProductName ProductID="gfs2-kmp-rt-5.14.21-150400.15.118.1">gfs2-kmp-rt-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-devel-rt-5.14.21-150400.15.118.1">
      <FullProductName ProductID="kernel-devel-rt-5.14.21-150400.15.118.1">kernel-devel-rt-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-rt-5.14.21-150400.15.118.1">
      <FullProductName ProductID="kernel-rt-5.14.21-150400.15.118.1">kernel-rt-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-rt-devel-5.14.21-150400.15.118.1">
      <FullProductName ProductID="kernel-rt-devel-5.14.21-150400.15.118.1">kernel-rt-devel-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-rt-extra-5.14.21-150400.15.118.1">
      <FullProductName ProductID="kernel-rt-extra-5.14.21-150400.15.118.1">kernel-rt-extra-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-rt-livepatch-5.14.21-150400.15.118.1">
      <FullProductName ProductID="kernel-rt-livepatch-5.14.21-150400.15.118.1">kernel-rt-livepatch-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-rt-livepatch-devel-5.14.21-150400.15.118.1">
      <FullProductName ProductID="kernel-rt-livepatch-devel-5.14.21-150400.15.118.1">kernel-rt-livepatch-devel-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-rt-optional-5.14.21-150400.15.118.1">
      <FullProductName ProductID="kernel-rt-optional-5.14.21-150400.15.118.1">kernel-rt-optional-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-rt_debug-5.14.21-150400.15.118.1">
      <FullProductName ProductID="kernel-rt_debug-5.14.21-150400.15.118.1">kernel-rt_debug-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-rt_debug-devel-5.14.21-150400.15.118.1">
      <FullProductName ProductID="kernel-rt_debug-devel-5.14.21-150400.15.118.1">kernel-rt_debug-devel-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-source-rt-5.14.21-150400.15.118.1">
      <FullProductName ProductID="kernel-source-rt-5.14.21-150400.15.118.1">kernel-source-rt-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-syms-rt-5.14.21-150400.15.118.1">
      <FullProductName ProductID="kernel-syms-rt-5.14.21-150400.15.118.1">kernel-syms-rt-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kselftests-kmp-rt-5.14.21-150400.15.118.1">
      <FullProductName ProductID="kselftests-kmp-rt-5.14.21-150400.15.118.1">kselftests-kmp-rt-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="ocfs2-kmp-rt-5.14.21-150400.15.118.1">
      <FullProductName ProductID="ocfs2-kmp-rt-5.14.21-150400.15.118.1">ocfs2-kmp-rt-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="reiserfs-kmp-rt-5.14.21-150400.15.118.1">
      <FullProductName ProductID="reiserfs-kmp-rt-5.14.21-150400.15.118.1">reiserfs-kmp-rt-5.14.21-150400.15.118.1</FullProductName>
    </Branch>
    <Relationship ProductReference="kernel-rt-5.14.21-150400.15.118.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Micro 5.3">
      <FullProductName ProductID="SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1">kernel-rt-5.14.21-150400.15.118.1 as a component of SUSE Linux Enterprise Micro 5.3</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-source-rt-5.14.21-150400.15.118.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Micro 5.3">
      <FullProductName ProductID="SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1">kernel-source-rt-5.14.21-150400.15.118.1 as a component of SUSE Linux Enterprise Micro 5.3</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-rt-5.14.21-150400.15.118.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Micro 5.4">
      <FullProductName ProductID="SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1">kernel-rt-5.14.21-150400.15.118.1 as a component of SUSE Linux Enterprise Micro 5.4</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-source-rt-5.14.21-150400.15.118.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Micro 5.4">
      <FullProductName ProductID="SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.1">kernel-source-rt-5.14.21-150400.15.118.1 as a component of SUSE Linux Enterprise Micro 5.4</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:

can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path

In es58x_rx_err_msg(), if can-&gt;do_set_mode() fails, the function
directly returns without calling netif_rx(skb). This means that the
skb previously allocated by alloc_can_err_skb() is not freed. In other
terms, this is a memory leak.

This patch simply removes the return statement in the error branch and
let the function continue.

Issue was found with GCC -fanalyzer, please follow the link below for
details.</Note>
    </Notes>
    <CVE>CVE-2021-47671</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.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-20251573-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2021-47671.html</URL>
        <Description>CVE-2021-47671</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1241421</URL>
        <Description>SUSE Bug 1241421</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:

fbdev: smscufx: fix error handling code in ufx_usb_probe

The current error handling code in ufx_usb_probe have many unmatching
issues, e.g., missing ufx_free_usb_list, destroy_modedb label should
only include framebuffer_release, fb_dealloc_cmap only matches
fb_alloc_cmap.

My local syzkaller reports a memory leak bug:

memory leak in ufx_usb_probe

BUG: memory leak
unreferenced object 0xffff88802f879580 (size 128):
  comm "kworker/0:7", pid 17416, jiffies 4295067474 (age 46.710s)
  hex dump (first 32 bytes):
    80 21 7c 2e 80 88 ff ff 18 d0 d0 0c 80 88 ff ff  .!|.............
    00 d0 d0 0c 80 88 ff ff e0 ff ff ff 0f 00 00 00  ................
  backtrace:
    [&lt;ffffffff814c99a0&gt;] kmalloc_trace+0x20/0x90 mm/slab_common.c:1045
    [&lt;ffffffff824d219c&gt;] kmalloc include/linux/slab.h:553 [inline]
    [&lt;ffffffff824d219c&gt;] kzalloc include/linux/slab.h:689 [inline]
    [&lt;ffffffff824d219c&gt;] ufx_alloc_urb_list drivers/video/fbdev/smscufx.c:1873 [inline]
    [&lt;ffffffff824d219c&gt;] ufx_usb_probe+0x11c/0x15a0 drivers/video/fbdev/smscufx.c:1655
    [&lt;ffffffff82d17927&gt;] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
    [&lt;ffffffff82712f0d&gt;] call_driver_probe drivers/base/dd.c:560 [inline]
    [&lt;ffffffff82712f0d&gt;] really_probe+0x12d/0x390 drivers/base/dd.c:639
    [&lt;ffffffff8271322f&gt;] __driver_probe_device+0xbf/0x140 drivers/base/dd.c:778
    [&lt;ffffffff827132da&gt;] driver_probe_device+0x2a/0x120 drivers/base/dd.c:808
    [&lt;ffffffff82713c27&gt;] __device_attach_driver+0xf7/0x150 drivers/base/dd.c:936
    [&lt;ffffffff82710137&gt;] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:427
    [&lt;ffffffff827136b5&gt;] __device_attach+0x105/0x2d0 drivers/base/dd.c:1008
    [&lt;ffffffff82711d36&gt;] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:487
    [&lt;ffffffff8270e242&gt;] device_add+0x642/0xdc0 drivers/base/core.c:3517
    [&lt;ffffffff82d14d5f&gt;] usb_set_configuration+0x8ef/0xb80 drivers/usb/core/message.c:2170
    [&lt;ffffffff82d2576c&gt;] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238
    [&lt;ffffffff82d16ffc&gt;] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293
    [&lt;ffffffff82712f0d&gt;] call_driver_probe drivers/base/dd.c:560 [inline]
    [&lt;ffffffff82712f0d&gt;] really_probe+0x12d/0x390 drivers/base/dd.c:639
    [&lt;ffffffff8271322f&gt;] __driver_probe_device+0xbf/0x140 drivers/base/dd.c:778

Fix this bug by rewriting the error handling code in ufx_usb_probe.</Note>
    </Notes>
    <CVE>CVE-2022-49741</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.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-20251573-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2022-49741.html</URL>
        <Description>CVE-2022-49741</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1240747</URL>
        <Description>SUSE Bug 1240747</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:

net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup

Currently napi_disable() gets called during rxq and txq cleanup,
even before napi is enabled and hrtimer is initialized. It causes
kernel panic.

? page_fault_oops+0x136/0x2b0
  ? page_counter_cancel+0x2e/0x80
  ? do_user_addr_fault+0x2f2/0x640
  ? refill_obj_stock+0xc4/0x110
  ? exc_page_fault+0x71/0x160
  ? asm_exc_page_fault+0x27/0x30
  ? __mmdrop+0x10/0x180
  ? __mmdrop+0xec/0x180
  ? hrtimer_active+0xd/0x50
  hrtimer_try_to_cancel+0x2c/0xf0
  hrtimer_cancel+0x15/0x30
  napi_disable+0x65/0x90
  mana_destroy_rxq+0x4c/0x2f0
  mana_create_rxq.isra.0+0x56c/0x6d0
  ? mana_uncfg_vport+0x50/0x50
  mana_alloc_queues+0x21b/0x320
  ? skb_dequeue+0x5f/0x80</Note>
    </Notes>
    <CVE>CVE-2024-46784</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.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-20251573-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-46784.html</URL>
        <Description>CVE-2024-46784</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1230771</URL>
        <Description>SUSE Bug 1230771</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:

padata: avoid UAF for reorder_work

Although the previous patch can avoid ps and ps UAF for _do_serial, it
can not avoid potential UAF issue for reorder_work. This issue can
happen just as below:

crypto_request			crypto_request		crypto_del_alg
padata_do_serial
  ...
  padata_reorder
    // processes all remaining
    // requests then breaks
    while (1) {
      if (!padata)
        break;
      ...
    }

				padata_do_serial
				  // new request added
				  list_add
    // sees the new request
    queue_work(reorder_work)
				  padata_reorder
				    queue_work_on(squeue-&gt;work)
...

				&lt;kworker context&gt;
				padata_serial_worker
				// completes new request,
				// no more outstanding
				// requests

							crypto_del_alg
							  // free pd

&lt;kworker context&gt;
invoke_padata_reorder
  // UAF of pd

To avoid UAF for 'reorder_work', get 'pd' ref before put 'reorder_work'
into the 'serial_wq' and put 'pd' ref until the 'serial_wq' finish.</Note>
    </Notes>
    <CVE>CVE-2025-21726</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.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-20251573-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-21726.html</URL>
        <Description>CVE-2025-21726</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1238865</URL>
        <Description>SUSE Bug 1238865</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1240837</URL>
        <Description>SUSE Bug 1240837</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:

arm64: cacheinfo: Avoid out-of-bounds write to cacheinfo array

The loop that detects/populates cache information already has a bounds
check on the array size but does not account for cache levels with
separate data/instructions cache. Fix this by incrementing the index
for any populated leaf (instead of any populated level).</Note>
    </Notes>
    <CVE>CVE-2025-21785</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.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-20251573-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-21785.html</URL>
        <Description>CVE-2025-21785</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1238747</URL>
        <Description>SUSE Bug 1238747</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1240745</URL>
        <Description>SUSE Bug 1240745</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:

vrf: use RCU protection in l3mdev_l3_out()

l3mdev_l3_out() can be called without RCU being held:

raw_sendmsg()
 ip_push_pending_frames()
  ip_send_skb()
   ip_local_out()
    __ip_local_out()
     l3mdev_ip_out()

Add rcu_read_lock() / rcu_read_unlock() pair to avoid
a potential UAF.</Note>
    </Notes>
    <CVE>CVE-2025-21791</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.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-20251573-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-21791.html</URL>
        <Description>CVE-2025-21791</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1238512</URL>
        <Description>SUSE Bug 1238512</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1240744</URL>
        <Description>SUSE Bug 1240744</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:

ax25: rcu protect dev-&gt;ax25_ptr

syzbot found a lockdep issue [1].

We should remove ax25 RTNL dependency in ax25_setsockopt()

This should also fix a variety of possible UAF in ax25.

[1]

WARNING: possible circular locking dependency detected
6.13.0-rc3-syzkaller-00762-g9268abe611b0 #0 Not tainted
------------------------------------------------------
syz.5.1818/12806 is trying to acquire lock:
 ffffffff8fcb3988 (rtnl_mutex){+.+.}-{4:4}, at: ax25_setsockopt+0xa55/0xe90 net/ax25/af_ax25.c:680

but task is already holding lock:
 ffff8880617ac258 (sk_lock-AF_AX25){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1618 [inline]
 ffff8880617ac258 (sk_lock-AF_AX25){+.+.}-{0:0}, at: ax25_setsockopt+0x209/0xe90 net/ax25/af_ax25.c:574

which lock already depends on the new lock.

the existing dependency chain (in reverse order) is:

-&gt; #1 (sk_lock-AF_AX25){+.+.}-{0:0}:
        lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849
        lock_sock_nested+0x48/0x100 net/core/sock.c:3642
        lock_sock include/net/sock.h:1618 [inline]
        ax25_kill_by_device net/ax25/af_ax25.c:101 [inline]
        ax25_device_event+0x24d/0x580 net/ax25/af_ax25.c:146
        notifier_call_chain+0x1a5/0x3f0 kernel/notifier.c:85
       __dev_notify_flags+0x207/0x400
        dev_change_flags+0xf0/0x1a0 net/core/dev.c:9026
        dev_ifsioc+0x7c8/0xe70 net/core/dev_ioctl.c:563
        dev_ioctl+0x719/0x1340 net/core/dev_ioctl.c:820
        sock_do_ioctl+0x240/0x460 net/socket.c:1234
        sock_ioctl+0x626/0x8e0 net/socket.c:1339
        vfs_ioctl fs/ioctl.c:51 [inline]
        __do_sys_ioctl fs/ioctl.c:906 [inline]
        __se_sys_ioctl+0xf5/0x170 fs/ioctl.c:892
        do_syscall_x64 arch/x86/entry/common.c:52 [inline]
        do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-&gt; #0 (rtnl_mutex){+.+.}-{4:4}:
        check_prev_add kernel/locking/lockdep.c:3161 [inline]
        check_prevs_add kernel/locking/lockdep.c:3280 [inline]
        validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904
        __lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5226
        lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849
        __mutex_lock_common kernel/locking/mutex.c:585 [inline]
        __mutex_lock+0x1ac/0xee0 kernel/locking/mutex.c:735
        ax25_setsockopt+0xa55/0xe90 net/ax25/af_ax25.c:680
        do_sock_setsockopt+0x3af/0x720 net/socket.c:2324
        __sys_setsockopt net/socket.c:2349 [inline]
        __do_sys_setsockopt net/socket.c:2355 [inline]
        __se_sys_setsockopt net/socket.c:2352 [inline]
        __x64_sys_setsockopt+0x1ee/0x280 net/socket.c:2352
        do_syscall_x64 arch/x86/entry/common.c:52 [inline]
        do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(sk_lock-AF_AX25);
                               lock(rtnl_mutex);
                               lock(sk_lock-AF_AX25);
  lock(rtnl_mutex);

 *** DEADLOCK ***

1 lock held by syz.5.1818/12806:
  #0: ffff8880617ac258 (sk_lock-AF_AX25){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1618 [inline]
  #0: ffff8880617ac258 (sk_lock-AF_AX25){+.+.}-{0:0}, at: ax25_setsockopt+0x209/0xe90 net/ax25/af_ax25.c:574

stack backtrace:
CPU: 1 UID: 0 PID: 12806 Comm: syz.5.1818 Not tainted 6.13.0-rc3-syzkaller-00762-g9268abe611b0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
 &lt;TASK&gt;
  __dump_stack lib/dump_stack.c:94 [inline]
  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
  print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2074
  check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2206
  check_prev_add kernel/locking/lockdep.c:3161 [inline]
  check_prevs_add kernel/lockin
---truncated---</Note>
    </Notes>
    <CVE>CVE-2025-21812</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.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-20251573-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-21812.html</URL>
        <Description>CVE-2025-21812</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1238471</URL>
        <Description>SUSE Bug 1238471</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1240736</URL>
        <Description>SUSE Bug 1240736</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:

RDMA/mlx5: Fix implicit ODP hang on parent deregistration

Fix the destroy_unused_implicit_child_mr() to prevent hanging during
parent deregistration as of below [1].

Upon entering destroy_unused_implicit_child_mr(), the reference count
for the implicit MR parent is incremented using:
refcount_inc_not_zero().

A corresponding decrement must be performed if
free_implicit_child_mr_work() is not called.

The code has been updated to properly manage the reference count that
was incremented.

[1]
INFO: task python3:2157 blocked for more than 120 seconds.
Not tainted 6.12.0-rc7+ #1633
"echo 0 &gt; /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:python3         state:D stack:0     pid:2157 tgid:2157  ppid:1685   flags:0x00000000
Call Trace:
&lt;TASK&gt;
__schedule+0x420/0xd30
schedule+0x47/0x130
__mlx5_ib_dereg_mr+0x379/0x5d0 [mlx5_ib]
? __pfx_autoremove_wake_function+0x10/0x10
ib_dereg_mr_user+0x5f/0x120 [ib_core]
? lock_release+0xc6/0x280
destroy_hw_idr_uobject+0x1d/0x60 [ib_uverbs]
uverbs_destroy_uobject+0x58/0x1d0 [ib_uverbs]
uobj_destroy+0x3f/0x70 [ib_uverbs]
ib_uverbs_cmd_verbs+0x3e4/0xbb0 [ib_uverbs]
? __pfx_uverbs_destroy_def_handler+0x10/0x10 [ib_uverbs]
? lock_acquire+0xc1/0x2f0
? ib_uverbs_ioctl+0xcb/0x170 [ib_uverbs]
? ib_uverbs_ioctl+0x116/0x170 [ib_uverbs]
? lock_release+0xc6/0x280
ib_uverbs_ioctl+0xe7/0x170 [ib_uverbs]
? ib_uverbs_ioctl+0xcb/0x170 [ib_uverbs]
 __x64_sys_ioctl+0x1b0/0xa70
? kmem_cache_free+0x221/0x400
do_syscall_64+0x6b/0x140
entry_SYSCALL_64_after_hwframe+0x76/0x7e
RIP: 0033:0x7f20f21f017b
RSP: 002b:00007ffcfc4a77c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ffcfc4a78d8 RCX: 00007f20f21f017b
RDX: 00007ffcfc4a78c0 RSI: 00000000c0181b01 RDI: 0000000000000003
RBP: 00007ffcfc4a78a0 R08: 000056147d125190 R09: 00007f20f1f14c60
R10: 0000000000000001 R11: 0000000000000246 R12: 00007ffcfc4a7890
R13: 000000000000001c R14: 000056147d100fc0 R15: 00007f20e365c9d0
&lt;/TASK&gt;</Note>
    </Notes>
    <CVE>CVE-2025-21886</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.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-20251573-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-21886.html</URL>
        <Description>CVE-2025-21886</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1240188</URL>
        <Description>SUSE Bug 1240188</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:

net: atm: fix use after free in lec_send()

The -&gt;send() operation frees skb so save the length before calling
-&gt;send() to avoid a use after free.</Note>
    </Notes>
    <CVE>CVE-2025-22004</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.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-20251573-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-22004.html</URL>
        <Description>CVE-2025-22004</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1240835</URL>
        <Description>SUSE Bug 1240835</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1241090</URL>
        <Description>SUSE Bug 1241090</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:

memstick: rtsx_usb_ms: Fix slab-use-after-free in rtsx_usb_ms_drv_remove

This fixes the following crash:

==================================================================
BUG: KASAN: slab-use-after-free in rtsx_usb_ms_poll_card+0x159/0x200 [rtsx_usb_ms]
Read of size 8 at addr ffff888136335380 by task kworker/6:0/140241

CPU: 6 UID: 0 PID: 140241 Comm: kworker/6:0 Kdump: loaded Tainted: G            E      6.14.0-rc6+ #1
Tainted: [E]=UNSIGNED_MODULE
Hardware name: LENOVO 30FNA1V7CW/1057, BIOS S0EKT54A 07/01/2024
Workqueue: events rtsx_usb_ms_poll_card [rtsx_usb_ms]
Call Trace:
 &lt;TASK&gt;
 dump_stack_lvl+0x51/0x70
 print_address_description.constprop.0+0x27/0x320
 ? rtsx_usb_ms_poll_card+0x159/0x200 [rtsx_usb_ms]
 print_report+0x3e/0x70
 kasan_report+0xab/0xe0
 ? rtsx_usb_ms_poll_card+0x159/0x200 [rtsx_usb_ms]
 rtsx_usb_ms_poll_card+0x159/0x200 [rtsx_usb_ms]
 ? __pfx_rtsx_usb_ms_poll_card+0x10/0x10 [rtsx_usb_ms]
 ? __pfx___schedule+0x10/0x10
 ? kick_pool+0x3b/0x270
 process_one_work+0x357/0x660
 worker_thread+0x390/0x4c0
 ? __pfx_worker_thread+0x10/0x10
 kthread+0x190/0x1d0
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x2d/0x50
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x1a/0x30
 &lt;/TASK&gt;

Allocated by task 161446:
 kasan_save_stack+0x20/0x40
 kasan_save_track+0x10/0x30
 __kasan_kmalloc+0x7b/0x90
 __kmalloc_noprof+0x1a7/0x470
 memstick_alloc_host+0x1f/0xe0 [memstick]
 rtsx_usb_ms_drv_probe+0x47/0x320 [rtsx_usb_ms]
 platform_probe+0x60/0xe0
 call_driver_probe+0x35/0x120
 really_probe+0x123/0x410
 __driver_probe_device+0xc7/0x1e0
 driver_probe_device+0x49/0xf0
 __device_attach_driver+0xc6/0x160
 bus_for_each_drv+0xe4/0x160
 __device_attach+0x13a/0x2b0
 bus_probe_device+0xbd/0xd0
 device_add+0x4a5/0x760
 platform_device_add+0x189/0x370
 mfd_add_device+0x587/0x5e0
 mfd_add_devices+0xb1/0x130
 rtsx_usb_probe+0x28e/0x2e0 [rtsx_usb]
 usb_probe_interface+0x15c/0x460
 call_driver_probe+0x35/0x120
 really_probe+0x123/0x410
 __driver_probe_device+0xc7/0x1e0
 driver_probe_device+0x49/0xf0
 __device_attach_driver+0xc6/0x160
 bus_for_each_drv+0xe4/0x160
 __device_attach+0x13a/0x2b0
 rebind_marked_interfaces.isra.0+0xcc/0x110
 usb_reset_device+0x352/0x410
 usbdev_do_ioctl+0xe5c/0x1860
 usbdev_ioctl+0xa/0x20
 __x64_sys_ioctl+0xc5/0xf0
 do_syscall_64+0x59/0x170
 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Freed by task 161506:
 kasan_save_stack+0x20/0x40
 kasan_save_track+0x10/0x30
 kasan_save_free_info+0x36/0x60
 __kasan_slab_free+0x34/0x50
 kfree+0x1fd/0x3b0
 device_release+0x56/0xf0
 kobject_cleanup+0x73/0x1c0
 rtsx_usb_ms_drv_remove+0x13d/0x220 [rtsx_usb_ms]
 platform_remove+0x2f/0x50
 device_release_driver_internal+0x24b/0x2e0
 bus_remove_device+0x124/0x1d0
 device_del+0x239/0x530
 platform_device_del.part.0+0x19/0xe0
 platform_device_unregister+0x1c/0x40
 mfd_remove_devices_fn+0x167/0x170
 device_for_each_child_reverse+0xc9/0x130
 mfd_remove_devices+0x6e/0xa0
 rtsx_usb_disconnect+0x2e/0xd0 [rtsx_usb]
 usb_unbind_interface+0xf3/0x3f0
 device_release_driver_internal+0x24b/0x2e0
 proc_disconnect_claim+0x13d/0x220
 usbdev_do_ioctl+0xb5e/0x1860
 usbdev_ioctl+0xa/0x20
 __x64_sys_ioctl+0xc5/0xf0
 do_syscall_64+0x59/0x170
 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Last potentially related work creation:
 kasan_save_stack+0x20/0x40
 kasan_record_aux_stack+0x85/0x90
 insert_work+0x29/0x100
 __queue_work+0x34a/0x540
 call_timer_fn+0x2a/0x160
 expire_timers+0x5f/0x1f0
 __run_timer_base.part.0+0x1b6/0x1e0
 run_timer_softirq+0x8b/0xe0
 handle_softirqs+0xf9/0x360
 __irq_exit_rcu+0x114/0x130
 sysvec_apic_timer_interrupt+0x72/0x90
 asm_sysvec_apic_timer_interrupt+0x16/0x20

Second to last potentially related work creation:
 kasan_save_stack+0x20/0x40
 kasan_record_aux_stack+0x85/0x90
 insert_work+0x29/0x100
 __queue_work+0x34a/0x540
 call_timer_fn+0x2a/0x160
 expire_timers+0x5f/0x1f0
 __run_timer_base.part.0+0x1b6/0x1e0
 run_timer_softirq+0x8b/0xe0
 handle_softirqs+0xf9/0x
---truncated---</Note>
    </Notes>
    <CVE>CVE-2025-22020</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.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-20251573-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-22020.html</URL>
        <Description>CVE-2025-22020</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1241280</URL>
        <Description>SUSE Bug 1241280</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">** REJECT ** This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.</Note>
    </Notes>
    <CVE>CVE-2025-22029</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.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-20251573-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-22029.html</URL>
        <Description>CVE-2025-22029</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1241378</URL>
        <Description>SUSE Bug 1241378</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1241379</URL>
        <Description>SUSE Bug 1241379</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:

x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs

On the following path, flush_tlb_range() can be used for zapping normal
PMD entries (PMD entries that point to page tables) together with the PTE
entries in the pointed-to page table:

    collapse_pte_mapped_thp
      pmdp_collapse_flush
        flush_tlb_range

The arm64 version of flush_tlb_range() has a comment describing that it can
be used for page table removal, and does not use any last-level
invalidation optimizations. Fix the X86 version by making it behave the
same way.

Currently, X86 only uses this information for the following two purposes,
which I think means the issue doesn't have much impact:

 - In native_flush_tlb_multi() for checking if lazy TLB CPUs need to be
   IPI'd to avoid issues with speculative page table walks.
 - In Hyper-V TLB paravirtualization, again for lazy TLB stuff.

The patch "x86/mm: only invalidate final translations with INVLPGB" which
is currently under review (see
&lt;https://lore.kernel.org/all/20241230175550.4046587-13-riel@surriel.com/&gt;)
would probably be making the impact of this a lot worse.</Note>
    </Notes>
    <CVE>CVE-2025-22045</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.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-20251573-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-22045.html</URL>
        <Description>CVE-2025-22045</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1241433</URL>
        <Description>SUSE Bug 1241433</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:

net: fix geneve_opt length integer overflow

struct geneve_opt uses 5 bit length for each single option, which
means every vary size option should be smaller than 128 bytes.

However, all current related Netlink policies cannot promise this
length condition and the attacker can exploit a exact 128-byte size
option to *fake* a zero length option and confuse the parsing logic,
further achieve heap out-of-bounds read.

One example crash log is like below:

[    3.905425] ==================================================================
[    3.905925] BUG: KASAN: slab-out-of-bounds in nla_put+0xa9/0xe0
[    3.906255] Read of size 124 at addr ffff888005f291cc by task poc/177
[    3.906646]
[    3.906775] CPU: 0 PID: 177 Comm: poc-oob-read Not tainted 6.1.132 #1
[    3.907131] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014
[    3.907784] Call Trace:
[    3.907925]  &lt;TASK&gt;
[    3.908048]  dump_stack_lvl+0x44/0x5c
[    3.908258]  print_report+0x184/0x4be
[    3.909151]  kasan_report+0xc5/0x100
[    3.909539]  kasan_check_range+0xf3/0x1a0
[    3.909794]  memcpy+0x1f/0x60
[    3.909968]  nla_put+0xa9/0xe0
[    3.910147]  tunnel_key_dump+0x945/0xba0
[    3.911536]  tcf_action_dump_1+0x1c1/0x340
[    3.912436]  tcf_action_dump+0x101/0x180
[    3.912689]  tcf_exts_dump+0x164/0x1e0
[    3.912905]  fw_dump+0x18b/0x2d0
[    3.913483]  tcf_fill_node+0x2ee/0x460
[    3.914778]  tfilter_notify+0xf4/0x180
[    3.915208]  tc_new_tfilter+0xd51/0x10d0
[    3.918615]  rtnetlink_rcv_msg+0x4a2/0x560
[    3.919118]  netlink_rcv_skb+0xcd/0x200
[    3.919787]  netlink_unicast+0x395/0x530
[    3.921032]  netlink_sendmsg+0x3d0/0x6d0
[    3.921987]  __sock_sendmsg+0x99/0xa0
[    3.922220]  __sys_sendto+0x1b7/0x240
[    3.922682]  __x64_sys_sendto+0x72/0x90
[    3.922906]  do_syscall_64+0x5e/0x90
[    3.923814]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[    3.924122] RIP: 0033:0x7e83eab84407
[    3.924331] Code: 48 89 fa 4c 89 df e8 38 aa 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 &lt;5b&gt; c3 0f 1f 80 00 00 00 00 83 e2 39 83 faf
[    3.925330] RSP: 002b:00007ffff505e370 EFLAGS: 00000202 ORIG_RAX: 000000000000002c
[    3.925752] RAX: ffffffffffffffda RBX: 00007e83eaafa740 RCX: 00007e83eab84407
[    3.926173] RDX: 00000000000001a8 RSI: 00007ffff505e3c0 RDI: 0000000000000003
[    3.926587] RBP: 00007ffff505f460 R08: 00007e83eace1000 R09: 000000000000000c
[    3.926977] R10: 0000000000000000 R11: 0000000000000202 R12: 00007ffff505f3c0
[    3.927367] R13: 00007ffff505f5c8 R14: 00007e83ead1b000 R15: 00005d4fbbe6dcb8

Fix these issues by enforing correct length condition in related
policies.</Note>
    </Notes>
    <CVE>CVE-2025-22055</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.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-20251573-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-22055.html</URL>
        <Description>CVE-2025-22055</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1241371</URL>
        <Description>SUSE Bug 1241371</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1241372</URL>
        <Description>SUSE Bug 1241372</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:

drm/vkms: Fix use after free and double free on init error

If the driver initialization fails, the vkms_exit() function might
access an uninitialized or freed default_config pointer and it might
double free it.

Fix both possible errors by initializing default_config only when the
driver initialization succeeded.</Note>
    </Notes>
    <CVE>CVE-2025-22097</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.118.1</ProductID>
        <ProductID>SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.118.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-20251573-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-22097.html</URL>
        <Description>CVE-2025-22097</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1241541</URL>
        <Description>SUSE Bug 1241541</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1241542</URL>
        <Description>SUSE Bug 1241542</Description>
      </Reference>
    </References>
  </Vulnerability>
</cvrfdoc>
