<?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://vulnerability.circl.lu</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>Sun, 11 Oct 2026 04:59:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31411 — net: atm: fix crash due to unvalidated vcc pointer in sigd_send()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31411</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;net: atm: fix crash due to unvalidated vcc pointer in sigd_send()&lt;/p&gt;
&lt;p&gt;Reproducer available at [1].&lt;/p&gt;
&lt;p&gt;The ATM send path (sendmsg -&amp;gt; vcc_sendmsg -&amp;gt; sigd_send) reads the vcc
pointer from msg-&amp;gt;vcc and uses it directly without any validation. This
pointer comes from userspace via sendmsg() and can be arbitrarily forged:&lt;/p&gt;
&lt;p&gt;int fd = socket(AF_ATMSVC, SOCK_DGRAM, 0);
    ioctl(fd, ATMSIGD_CTRL);  // become ATM signaling daemon
    struct msghdr msg = { .msg_iov = &amp;amp;iov, ... };
    *(unsigned long *)(buf + 4) = 0xdeadbeef;  // fake vcc pointer
    sendmsg(fd, &amp;amp;msg, 0);  // kernel dereferences 0xdeadbeef&lt;/p&gt;
&lt;p&gt;In normal operation, the kernel sends the vcc pointer to the signaling
daemon via sigd_enq() when processing operations like connect(), bind(),
or listen(). The daemon is expected to return the same pointer when
responding. However, a malicious daemon can send arbitrary pointer values.&lt;/p&gt;
&lt;p&gt;Fix this by introducing find_get_vcc() which validates the pointer by
searching through vcc_hash (similar to how sigd_close() iterates over
all VCCs), and acquires a reference via sock_hold() if found.&lt;/p&gt;
&lt;p&gt;Since struct atm_vcc embeds struct sock as its first member, they share
the same lifetime. Therefore using sock_hold/sock_put is sufficient to
keep the vcc alive while it is being used.&lt;/p&gt;
&lt;p&gt;Note that there may be a race with sigd_close() which could mark the vcc
with various flags (e.g., ATM_VF_RELEASED) after find_get_vcc() returns.
Howev…&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;net: atm: fix crash due to unvalidated vcc pointer in sigd_send()&lt;/p&gt;
&lt;p&gt;Reproducer available at [1].&lt;/p&gt;
&lt;p&gt;The ATM send path (sendmsg -&amp;gt; vcc_sendmsg -&amp;gt; sigd_send) reads the vcc
pointer from msg-&amp;gt;vcc and uses it directly without any validation. This
pointer comes from userspace via sendmsg() and can be arbitrarily forged:&lt;/p&gt;
&lt;p&gt;int fd = socket(AF_ATMSVC, SOCK_DGRAM, 0);
    ioctl(fd, ATMSIGD_CTRL);  // become ATM signaling daemon
    struct msghdr msg = { .msg_iov = &amp;amp;iov, ... };
    *(unsigned long *)(buf + 4) = 0xdeadbeef;  // fake vcc pointer
    sendmsg(fd, &amp;amp;msg, 0);  // kernel dereferences 0xdeadbeef&lt;/p&gt;
&lt;p&gt;In normal operation, the kernel sends the vcc pointer to the signaling
daemon via sigd_enq() when processing operations like connect(), bind(),
or listen(). The daemon is expected to return the same pointer when
responding. However, a malicious daemon can send arbitrary pointer values.&lt;/p&gt;
&lt;p&gt;Fix this by introducing find_get_vcc() which validates the pointer by
searching through vcc_hash (similar to how sigd_close() iterates over
all VCCs), and acquires a reference via sock_hold() if found.&lt;/p&gt;
&lt;p&gt;Since struct atm_vcc embeds struct sock as its first member, they share
the same lifetime. Therefore using sock_hold/sock_put is sufficient to
keep the vcc alive while it is being used.&lt;/p&gt;
&lt;p&gt;Note that there may be a race with sigd_close() which could mark the vcc
with various flags (e.g., ATM_VF_RELEASED) after find_get_vcc() returns.
Howev…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31411</guid>
    </item>
    <item>
      <title>USN-8492-1 — linux, linux-aws, linux-aws-fips, linux-gcp, linux-gcp-fips, linux-ibm, linux-nvidia, linux-nvidia-6.8, linux-oracle, l…</title>
      <link>https://vulnerability.circl.lu/vuln/usn-8492-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-nvidia-6.8, Ubuntu:Pro:Realtime:22.04:LTS: linux-realtime-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-nvidia, Ubuntu:24.04:LTS: linux-oracle, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime, Ubuntu:Pro:FIPS-updates:24.04:LTS: linux-aws-fips and 1 more&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;
  - MIPS architecture;
  - PowerPC architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - ATM drivers;
  - RNBD block device driver;
  - Ublk userspace block driver;
  - Bus devices;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Clocksource drivers;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Multifunction device drivers;
  - Broadcom VK accelerator driver;
  - MOST (Media Oriented Systems Transport) drivers;
  - MTD block device drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NTB driver;
  - NVME drivers;
  - PCI subsystem;
  - Performance monitor drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - Power supply drivers;
  - RapidIO drivers;
  - RAS (Reliability, Availability, Serviceability) subsystem;
  - Remote Processor subsystem;
  - RPMSG subsystem;
  - S/390 drivers;
  - SCSI subsystem;
  - MediaTek SoC dr…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-nvidia-6.8, Ubuntu:Pro:Realtime:22.04:LTS: linux-realtime-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-nvidia, Ubuntu:24.04:LTS: linux-oracle, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime, Ubuntu:Pro:FIPS-updates:24.04:LTS: linux-aws-fips and 1 more&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;
  - MIPS architecture;
  - PowerPC architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - ATM drivers;
  - RNBD block device driver;
  - Ublk userspace block driver;
  - Bus devices;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Clocksource drivers;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Multifunction device drivers;
  - Broadcom VK accelerator driver;
  - MOST (Media Oriented Systems Transport) drivers;
  - MTD block device drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NTB driver;
  - NVME drivers;
  - PCI subsystem;
  - Performance monitor drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - Power supply drivers;
  - RapidIO drivers;
  - RAS (Reliability, Availability, Serviceability) subsystem;
  - Remote Processor subsystem;
  - RPMSG subsystem;
  - S/390 drivers;
  - SCSI subsystem;
  - MediaTek SoC dr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/usn-8492-1</guid>
    </item>
  </channel>
</rss>
