<?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-10-01T05:18:59.922969+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-2025-71082</id>
    <title>CVE-2025-71082 — Bluetooth: btusb: revert use of devm_kzalloc in btusb</title>
    <updated>2026-10-01T05:18:59.926028+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>Bluetooth: btusb: revert use of devm_kzalloc in btusb</p>
<p>This reverts commit 98921dbd00c4e ("Bluetooth: Use devm_kzalloc in
btusb.c file").</p>
<p>In btusb_probe(), we use devm_kzalloc() to allocate the btusb data. This
ties the lifetime of all the btusb data to the binding of a driver to
one interface, INTF. In a driver that binds to other interfaces, ISOC
and DIAG, this is an accident waiting to happen.</p>
<p>The issue is revealed in btusb_disconnect(), where calling
usb_driver_release_interface(&amp;btusb_driver, data-&gt;intf) will have devm
free the data that is also being used by the other interfaces of the
driver that may not be released yet.</p>
<p>To fix this, revert the use of devm and go back to freeing memory
explicitly.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-71082"/>
  </entry>
</feed>
