<?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:44:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68187 — exec: fix unsigned loop counter wrap in transfer_args_to_stack()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-68187</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;exec: fix unsigned loop counter wrap in transfer_args_to_stack()&lt;/p&gt;
&lt;p&gt;The stop value is derived from bprm-&amp;gt;p &amp;gt;&amp;gt; PAGE_SHIFT. The index variable
is an unsigned long. If bprm-&amp;gt;p drops below PAGE_SIZE and stop becomes
zero the loop condition index &amp;gt;= stop is always true.&lt;/p&gt;
&lt;p&gt;After the index == 0 iteration the decrement wraps to ULONG_MAX and
bprm-&amp;gt;page[ULONG_MAX] reads sizeof(void *) bytes in front of the array.
The pointer has wrapped to -1. That garbage pointer is then passed to
kmap_local_page() and PAGE_SIZE bytes are copied from wherever that
lands into the stack of the process being created. And the loop doesn&amp;#39;t
terminate either...&lt;/p&gt;
&lt;p&gt;Getting there only requires bprm-&amp;gt;p &amp;lt; PAGE_SIZE. On !MMU
bprm_set_stack_limit() and bprm_hit_stack_limit() are empty. So the only
constraint on how far bprm-&amp;gt;p is pushed down is valid_arg_len(), i.e.
that each individual string still fits in what is left.&lt;/p&gt;
&lt;p&gt;bprm-&amp;gt;p starts at PAGE_SIZE * MAX_ARG_PAGES - sizeof(void *) so a
single argument or environment string of a little over 31 pages leaves
it in the first page:&lt;/p&gt;
&lt;p&gt;Oops - load access fault [#1]
  CPU: 0 UID: 0 PID: 1 Comm: victim Not tainted 7.2.0-rc4 #1
  epc : __memcpy+0xd4/0xf8
   ra : transfer_args_to_stack+0xaa/0xae
   s4 : ffffffffffffffff   s2 : 0000000000000000
   a1 : ffffffdc98000000   a2 : 0000000000001000
  status: 0000000a00001880 badaddr: ffffffdc98000000 cause: 0000000000000005
  [&amp;lt;801a5324&amp;gt;] __memcpy+0xd4/0xf8
  [&amp;lt;800…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;exec: fix unsigned loop counter wrap in transfer_args_to_stack()&lt;/p&gt;
&lt;p&gt;The stop value is derived from bprm-&amp;gt;p &amp;gt;&amp;gt; PAGE_SHIFT. The index variable
is an unsigned long. If bprm-&amp;gt;p drops below PAGE_SIZE and stop becomes
zero the loop condition index &amp;gt;= stop is always true.&lt;/p&gt;
&lt;p&gt;After the index == 0 iteration the decrement wraps to ULONG_MAX and
bprm-&amp;gt;page[ULONG_MAX] reads sizeof(void *) bytes in front of the array.
The pointer has wrapped to -1. That garbage pointer is then passed to
kmap_local_page() and PAGE_SIZE bytes are copied from wherever that
lands into the stack of the process being created. And the loop doesn&amp;#39;t
terminate either...&lt;/p&gt;
&lt;p&gt;Getting there only requires bprm-&amp;gt;p &amp;lt; PAGE_SIZE. On !MMU
bprm_set_stack_limit() and bprm_hit_stack_limit() are empty. So the only
constraint on how far bprm-&amp;gt;p is pushed down is valid_arg_len(), i.e.
that each individual string still fits in what is left.&lt;/p&gt;
&lt;p&gt;bprm-&amp;gt;p starts at PAGE_SIZE * MAX_ARG_PAGES - sizeof(void *) so a
single argument or environment string of a little over 31 pages leaves
it in the first page:&lt;/p&gt;
&lt;p&gt;Oops - load access fault [#1]
  CPU: 0 UID: 0 PID: 1 Comm: victim Not tainted 7.2.0-rc4 #1
  epc : __memcpy+0xd4/0xf8
   ra : transfer_args_to_stack+0xaa/0xae
   s4 : ffffffffffffffff   s2 : 0000000000000000
   a1 : ffffffdc98000000   a2 : 0000000000001000
  status: 0000000a00001880 badaddr: ffffffdc98000000 cause: 0000000000000005
  [&amp;lt;801a5324&amp;gt;] __memcpy+0xd4/0xf8
  [&amp;lt;800…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-68187</guid>
    </item>
    <item>
      <title>USN-8875-1 — linux, linux-aws, linux-aws-5.15, linux-aws-fips, linux-azure, linux-azure-5.15, linux-azure-fde-5.15, linux-azure-fips…</title>
      <link>https://db.gcve.eu/vuln/usn-8875-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-aws-5.15, Ubuntu:Pro:20.04:LTS: linux-azure-5.15, Ubuntu:Pro:20.04:LTS: linux-azure-fde-5.15, Ubuntu:Pro:20.04:LTS: linux-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-ibm-5.15, Ubuntu:Pro:20.04:LTS: linux-intel-iotg-5.15, Ubuntu:Pro:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-aws, Ubuntu:22.04:LTS: linux-azure and 13 more&lt;/p&gt;
&lt;p&gt;It was discovered that the i.MX clock driver in the Linux kernel did not
properly handle certain memory allocation failure conditions, leading to a
null pointer dereference vulnerability. A local attacker could possibly use
this to cause a denial of service (system crash). (CVE-2022-3114)&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:
  - User-space API (UAPI);
  - ARM32 architecture;
  - ARM64 architecture;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - Android drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - DRBD Distributed Replicated Block Device drivers;
  - Rados block device (RBD) driver;
  - Bluetooth drivers;
  - Cdrom driver;
  - Character device driver;
  - Hardware random number generator core;
  - TPM device driver;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - DAX dirext access to differentiated memory framework;
  - DMA engine subsystem;
  - FireWire subsystem;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - ARM SCMI message protocol;
  - Intel Stratix 10 firmware drivers;
  - FPGA Framework;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - In…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-aws-5.15, Ubuntu:Pro:20.04:LTS: linux-azure-5.15, Ubuntu:Pro:20.04:LTS: linux-azure-fde-5.15, Ubuntu:Pro:20.04:LTS: linux-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-ibm-5.15, Ubuntu:Pro:20.04:LTS: linux-intel-iotg-5.15, Ubuntu:Pro:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-aws, Ubuntu:22.04:LTS: linux-azure and 13 more&lt;/p&gt;
&lt;p&gt;It was discovered that the i.MX clock driver in the Linux kernel did not
properly handle certain memory allocation failure conditions, leading to a
null pointer dereference vulnerability. A local attacker could possibly use
this to cause a denial of service (system crash). (CVE-2022-3114)&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:
  - User-space API (UAPI);
  - ARM32 architecture;
  - ARM64 architecture;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - Android drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - DRBD Distributed Replicated Block Device drivers;
  - Rados block device (RBD) driver;
  - Bluetooth drivers;
  - Cdrom driver;
  - Character device driver;
  - Hardware random number generator core;
  - TPM device driver;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - DAX dirext access to differentiated memory framework;
  - DMA engine subsystem;
  - FireWire subsystem;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - ARM SCMI message protocol;
  - Intel Stratix 10 firmware drivers;
  - FPGA Framework;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - In…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8875-1</guid>
    </item>
  </channel>
</rss>
