<?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://db.gcve.eu</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>Thu, 19 Nov 2026 17:21:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38236 — af_unix: Don't leave consecutive consumed OOB skbs.</title>
      <link>https://db.gcve.eu/vuln/cve-2025-38236</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;af_unix: Don&amp;#39;t leave consecutive consumed OOB skbs.&lt;/p&gt;
&lt;p&gt;Jann Horn reported a use-after-free in unix_stream_read_generic().&lt;/p&gt;
&lt;p&gt;The following sequences reproduce the issue:&lt;/p&gt;
&lt;p&gt;$ python3
  from socket import *
  s1, s2 = socketpair(AF_UNIX, SOCK_STREAM)
  s1.send(b&amp;#39;x&amp;#39;, MSG_OOB)
  s2.recv(1, MSG_OOB)     # leave a consumed OOB skb
  s1.send(b&amp;#39;y&amp;#39;, MSG_OOB)
  s2.recv(1, MSG_OOB)     # leave a consumed OOB skb
  s1.send(b&amp;#39;z&amp;#39;, MSG_OOB)
  s2.recv(1)              # recv &amp;#39;z&amp;#39; illegally
  s2.recv(1, MSG_OOB)     # access &amp;#39;z&amp;#39; skb (use-after-free)&lt;/p&gt;
&lt;p&gt;Even though a user reads OOB data, the skb holding the data stays on
the recv queue to mark the OOB boundary and break the next recv().&lt;/p&gt;
&lt;p&gt;After the last send() in the scenario above, the sk2&amp;#39;s recv queue has
2 leading consumed OOB skbs and 1 real OOB skb.&lt;/p&gt;
&lt;p&gt;Then, the following happens during the next recv() without MSG_OOB&lt;/p&gt;
&lt;p&gt;1. unix_stream_read_generic() peeks the first consumed OOB skb
  2. manage_oob() returns the next consumed OOB skb
  3. unix_stream_read_generic() fetches the next not-yet-consumed OOB skb
  4. unix_stream_read_generic() reads and frees the OOB skb&lt;/p&gt;
&lt;p&gt;, and the last recv(MSG_OOB) triggers KASAN splat.&lt;/p&gt;
&lt;p&gt;The 3. above occurs because of the SO_PEEK_OFF code, which does not
expect unix_skb_len(skb) to be 0, but this is true for such consumed
OOB skbs.&lt;/p&gt;
&lt;p&gt;while (skip &amp;gt;= unix_skb_len(skb)) {
    skip -= unix_skb_len(skb);
    skb = skb_peek_next(skb, &amp;amp;sk-&amp;gt;sk_receive_queue…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;af_unix: Don&amp;#39;t leave consecutive consumed OOB skbs.&lt;/p&gt;
&lt;p&gt;Jann Horn reported a use-after-free in unix_stream_read_generic().&lt;/p&gt;
&lt;p&gt;The following sequences reproduce the issue:&lt;/p&gt;
&lt;p&gt;$ python3
  from socket import *
  s1, s2 = socketpair(AF_UNIX, SOCK_STREAM)
  s1.send(b&amp;#39;x&amp;#39;, MSG_OOB)
  s2.recv(1, MSG_OOB)     # leave a consumed OOB skb
  s1.send(b&amp;#39;y&amp;#39;, MSG_OOB)
  s2.recv(1, MSG_OOB)     # leave a consumed OOB skb
  s1.send(b&amp;#39;z&amp;#39;, MSG_OOB)
  s2.recv(1)              # recv &amp;#39;z&amp;#39; illegally
  s2.recv(1, MSG_OOB)     # access &amp;#39;z&amp;#39; skb (use-after-free)&lt;/p&gt;
&lt;p&gt;Even though a user reads OOB data, the skb holding the data stays on
the recv queue to mark the OOB boundary and break the next recv().&lt;/p&gt;
&lt;p&gt;After the last send() in the scenario above, the sk2&amp;#39;s recv queue has
2 leading consumed OOB skbs and 1 real OOB skb.&lt;/p&gt;
&lt;p&gt;Then, the following happens during the next recv() without MSG_OOB&lt;/p&gt;
&lt;p&gt;1. unix_stream_read_generic() peeks the first consumed OOB skb
  2. manage_oob() returns the next consumed OOB skb
  3. unix_stream_read_generic() fetches the next not-yet-consumed OOB skb
  4. unix_stream_read_generic() reads and frees the OOB skb&lt;/p&gt;
&lt;p&gt;, and the last recv(MSG_OOB) triggers KASAN splat.&lt;/p&gt;
&lt;p&gt;The 3. above occurs because of the SO_PEEK_OFF code, which does not
expect unix_skb_len(skb) to be 0, but this is true for such consumed
OOB skbs.&lt;/p&gt;
&lt;p&gt;while (skip &amp;gt;= unix_skb_len(skb)) {
    skip -= unix_skb_len(skb);
    skb = skb_peek_next(skb, &amp;amp;sk-&amp;gt;sk_receive_queue…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-38236</guid>
    </item>
    <item>
      <title>USN-7833-1 — linux, linux-aws, linux-gcp, linux-oem-6.14, linux-oracle, linux-oracle-6.14, linux-raspi, linux-realtime vulnerabiliti…</title>
      <link>https://db.gcve.eu/vuln/usn-7833-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-oem-6.14, Ubuntu:24.04:LTS: linux-oracle-6.14&lt;/p&gt;
&lt;p&gt;Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,
and Flavien Solt discovered that some AMD processors may allow an attacker
to infer data from previous stores, potentially resulting in the leakage of
privileged information. A local attacker could possibly use this to expose
sensitive information. (CVE-2024-36350, CVE-2024-36357)&lt;/p&gt;
&lt;p&gt;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:
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - Ublk userspace block driver;
  - Bus devices;
  - DMA engine subsystem;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - Cirrus firmware drivers;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - Multiple devices driver;
  - Media drivers;
  - TI TPS6594 PFSM driver;
  - MMC subsystem;
  - MTD block device drivers;
  - Network drivers;
  - NVME drivers;
  - x86 platform drivers;
  - RapidIO drivers;
  - Voltage and Current Regulator drivers;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI subsystem;
  - TCM subsystem;
  - Trusted Execution Environment drivers;
  - TTY drivers;
  - ChipIdea USB dr…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-oem-6.14, Ubuntu:24.04:LTS: linux-oracle-6.14&lt;/p&gt;
&lt;p&gt;Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,
and Flavien Solt discovered that some AMD processors may allow an attacker
to infer data from previous stores, potentially resulting in the leakage of
privileged information. A local attacker could possibly use this to expose
sensitive information. (CVE-2024-36350, CVE-2024-36357)&lt;/p&gt;
&lt;p&gt;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:
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - Ublk userspace block driver;
  - Bus devices;
  - DMA engine subsystem;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - Cirrus firmware drivers;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - Multiple devices driver;
  - Media drivers;
  - TI TPS6594 PFSM driver;
  - MMC subsystem;
  - MTD block device drivers;
  - Network drivers;
  - NVME drivers;
  - x86 platform drivers;
  - RapidIO drivers;
  - Voltage and Current Regulator drivers;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI subsystem;
  - TCM subsystem;
  - Trusted Execution Environment drivers;
  - TTY drivers;
  - ChipIdea USB dr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7833-1</guid>
    </item>
  </channel>
</rss>
