<?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-29T16:01:33.112236+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-2026-53254</id>
    <title>CVE-2026-53254 — Bluetooth: RFCOMM: validate skb length in MCC handlers</title>
    <updated>2026-09-29T16:01:40.716154+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: RFCOMM: validate skb length in MCC handlers</p>
<p>The RFCOMM MCC handlers cast skb-&gt;data to protocol-specific structs
without validating skb-&gt;len first. A malicious remote device can send
truncated MCC frames and trigger out-of-bounds reads in these handlers.</p>
<p>Fix this by using skb_pull_data() to validate and access the required
data before dereferencing it.</p>
<p>rfcomm_recv_rpn() requires special handling since ETSI TS 07.10 allows
1-byte RPN requests. Handle this by validating only the DLCI byte first,
and validating the full struct only when len &gt; 1.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-53254"/>
  </entry>
</feed>
