<?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-01T14:02:00.536050+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-68143</id>
    <title>CVE-2026-68143 — net: slip: serialize receive against buffer reallocation</title>
    <updated>2026-10-01T14:02:00.552413+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>net: slip: serialize receive against buffer reallocation</p>
<p>sl_realloc_bufs() replaces rbuff and updates buffsize while holding
sl-&gt;lock. slip_receive_buf() reads those fields and writes through rbuff
without holding the lock.</p>
<p>An MTU change can therefore race with receive processing. An MTU shrink
can expose the new smaller rbuff with the old larger bound, causing an
out-of-bounds write. A receive callback which already loaded the old
rbuff can instead continue writing after that buffer has been freed.</p>
<p>Serialize receive processing with sl_realloc_bufs() by holding sl-&gt;lock
while consuming each receive batch.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-68143"/>
  </entry>
</feed>
