<?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-29T10:39:50.579212+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-2024-47711</id>
    <title>CVE-2024-47711 — af_unix: Don't return OOB skb in manage_oob().</title>
    <updated>2026-09-29T10:39:50.654260+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>af_unix: Don't return OOB skb in manage_oob().</p>
<p>syzbot reported use-after-free in unix_stream_recv_urg(). [0]</p>
<p>The scenario is</p>
<p>1. send(MSG_OOB)
  2. recv(MSG_OOB)
     -&gt; The consumed OOB remains in recv queue
  3. send(MSG_OOB)
  4. recv()
     -&gt; manage_oob() returns the next skb of the consumed OOB
     -&gt; This is also OOB, but unix_sk(sk)-&gt;oob_skb is not cleared
  5. recv(MSG_OOB)
     -&gt; unix_sk(sk)-&gt;oob_skb is used but already freed</p>
<p>The recent commit 8594d9b85c07 ("af_unix: Don't call skb_get() for OOB
skb.") uncovered the issue.</p>
<p>If the OOB skb is consumed and the next skb is peeked in manage_oob(),
we still need to check if the skb is OOB.</p>
<p>Let's do so by falling back to the following checks in manage_oob()
and add the test case in selftest.</p>
<p>Note that we need to add a similar check for SIOCATMARK.</p>
<p>[0]:
BUG: KASAN: slab-use-after-free in unix_stream_read_actor+0xa6/0xb0 net/unix/af_unix.c:2959
Read of size 4 at addr ffff8880326abcc4 by task syz-executor178/5235</p>
<p>CPU: 0 UID: 0 PID: 5235 Comm: syz-executor178 Not tainted 6.11.0-rc5-syzkaller-00742-gfbdaffe41adc #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call Trace:
 &lt;TASK&gt;
 __dump_stack lib/dump_stack.c:93 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119
 print_address_description mm/kasan/report.c:377 [inline]
 print_report+0x169/0x550 mm/kasan/report.c:488
 kasan_report+0x143/0x180 mm/k…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-47711"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/usn-7276-1</id>
    <title>USN-7276-1 — linux, linux-lowlatency vulnerabilities</title>
    <updated>2026-09-29T10:39:50.654456+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:24.10: linux, Ubuntu:24.10: linux-lowlatency</p>
<p>Attila Szász discovered that the HFS+ file system implementation in the
Linux Kernel contained a heap overflow vulnerability. An attacker could use
a specially crafted file system image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2025-0927)</p>
<p>Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - SuperH RISC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - RAM backed block device driver;
  - Network block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - TPM device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - Buffer Sharing and Synchronization framework;
  - EDAC drivers;
  - FireWire subsystem;
  - ARM SCMI message protocol;
  - ARM SCPI message protocol;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/usn-7276-1"/>
  </entry>
</feed>
