<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 07 Oct 2026 15:40:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43119 — Bluetooth: hci_sync: annotate data-races around hdev-&gt;req_status</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-43119</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_sync: annotate data-races around hdev-&amp;gt;req_status&lt;/p&gt;
&lt;p&gt;__hci_cmd_sync_sk() sets hdev-&amp;gt;req_status under hdev-&amp;gt;req_lock:&lt;/p&gt;
&lt;p&gt;hdev-&amp;gt;req_status = HCI_REQ_PEND;&lt;/p&gt;
&lt;p&gt;However, several other functions read or write hdev-&amp;gt;req_status without
holding any lock:&lt;/p&gt;
&lt;p&gt;- hci_send_cmd_sync() reads req_status in hci_cmd_work (workqueue)
  - hci_cmd_sync_complete() reads/writes from HCI event completion
  - hci_cmd_sync_cancel() / hci_cmd_sync_cancel_sync() read/write
  - hci_abort_conn() reads in connection abort path&lt;/p&gt;
&lt;p&gt;Since __hci_cmd_sync_sk() runs on hdev-&amp;gt;req_workqueue while
hci_send_cmd_sync() runs on hdev-&amp;gt;workqueue, these are different
workqueues that can execute concurrently on different CPUs. The plain
C accesses constitute a data race.&lt;/p&gt;
&lt;p&gt;Add READ_ONCE()/WRITE_ONCE() annotations on all concurrent accesses
to hdev-&amp;gt;req_status to prevent potential compiler optimizations that
could affect correctness (e.g., load fusing in the wait_event
condition or store reordering).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_sync: annotate data-races around hdev-&amp;gt;req_status&lt;/p&gt;
&lt;p&gt;__hci_cmd_sync_sk() sets hdev-&amp;gt;req_status under hdev-&amp;gt;req_lock:&lt;/p&gt;
&lt;p&gt;hdev-&amp;gt;req_status = HCI_REQ_PEND;&lt;/p&gt;
&lt;p&gt;However, several other functions read or write hdev-&amp;gt;req_status without
holding any lock:&lt;/p&gt;
&lt;p&gt;- hci_send_cmd_sync() reads req_status in hci_cmd_work (workqueue)
  - hci_cmd_sync_complete() reads/writes from HCI event completion
  - hci_cmd_sync_cancel() / hci_cmd_sync_cancel_sync() read/write
  - hci_abort_conn() reads in connection abort path&lt;/p&gt;
&lt;p&gt;Since __hci_cmd_sync_sk() runs on hdev-&amp;gt;req_workqueue while
hci_send_cmd_sync() runs on hdev-&amp;gt;workqueue, these are different
workqueues that can execute concurrently on different CPUs. The plain
C accesses constitute a data race.&lt;/p&gt;
&lt;p&gt;Add READ_ONCE()/WRITE_ONCE() annotations on all concurrent accesses
to hdev-&amp;gt;req_status to prevent potential compiler optimizations that
could affect correctness (e.g., load fusing in the wait_event
condition or store reordering).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-43119</guid>
    </item>
  </channel>
</rss>
