<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T04:43:36.311812+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2023-53529</id>
    <title>CVE-2023-53529 — wifi: rtw88: Fix memory leak in rtw88_usb</title>
    <updated>2026-09-29T04:43:36.325949+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>wifi: rtw88: Fix memory leak in rtw88_usb</p>
<p>Kmemleak shows the following leak arising from routine in the usb
probe routine:</p>
<p>unreferenced object 0xffff895cb29bba00 (size 512):
  comm "(udev-worker)", pid 534, jiffies 4294903932 (age 102751.088s)
  hex dump (first 32 bytes):
    77 30 30 30 00 00 00 00 02 2f 2d 2b 30 00 00 00  w000...../-+0...
    02 00 2a 28 00 00 00 00 ff 55 ff ff ff 00 00 00  ..*(.....U......
  backtrace:
    [&lt;ffffffff9265fa36&gt;] kmalloc_trace+0x26/0x90
    [&lt;ffffffffc17eec41&gt;] rtw_usb_probe+0x2f1/0x680 [rtw_usb]
    [&lt;ffffffffc03e19fd&gt;] usb_probe_interface+0xdd/0x2e0 [usbcore]
    [&lt;ffffffff92b4f2fe&gt;] really_probe+0x18e/0x3d0
    [&lt;ffffffff92b4f5b8&gt;] __driver_probe_device+0x78/0x160
    [&lt;ffffffff92b4f6bf&gt;] driver_probe_device+0x1f/0x90
    [&lt;ffffffff92b4f8df&gt;] __driver_attach+0xbf/0x1b0
    [&lt;ffffffff92b4d350&gt;] bus_for_each_dev+0x70/0xc0
    [&lt;ffffffff92b4e51e&gt;] bus_add_driver+0x10e/0x210
    [&lt;ffffffff92b50935&gt;] driver_register+0x55/0xf0
    [&lt;ffffffffc03e0708&gt;] usb_register_driver+0x88/0x140 [usbcore]
    [&lt;ffffffff92401153&gt;] do_one_initcall+0x43/0x210
    [&lt;ffffffff9254f42a&gt;] do_init_module+0x4a/0x200
    [&lt;ffffffff92551d1c&gt;] __do_sys_finit_module+0xac/0x120
    [&lt;ffffffff92ee6626&gt;] do_syscall_64+0x56/0x80
    [&lt;ffffffff9300006a&gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0</p>
<p>The leak was verified to be real by unloading the driver, which resulted
in a dangling pointer to the allocation.…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-53529"/>
  </entry>
</feed>
