<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 16:49:06 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-90174</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-90174</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-90174</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1469 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1469</link>
      <description>certfr-2026-avi-1469</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1469</guid>
    </item>
    <item>
      <title>OESA-2026-4898 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-4898</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: typec: wcove: don&amp;amp;apos;t write past struct pd_message in wcove_read_rx_buffer()&lt;/p&gt;
&lt;p&gt;wcove_read_rx_buffer() copies the PD RX FIFO into the caller&amp;amp;apos;s
struct pd_message with&lt;/p&gt;
&lt;p&gt;for (i = 0; i &amp;amp;lt; USBC_RXINFO_RXBYTES(info); i++)
		regmap_read(wcove-&amp;amp;gt;regmap, USBC_RX_DATA + i, msg + i);&lt;/p&gt;
&lt;p&gt;which has two problems:&lt;/p&gt;
&lt;p&gt;USBC_RXINFO_RXBYTES() is a 5-bit field (max 31) while struct pd_message
is 30 bytes (__le16 header + __le32 payload[PD_MAX_PAYLOAD], packed).
The byte count latched in RXINFO is the number of bytes the port partner
put on the wire, so a malicious partner that transmits a 31-byte frame
can drive the loop one byte past the destination if the WCOVE BMC
receiver does not enforce the PD object-count limit in hardware. The
existing FIXME flagged this as unverified.&lt;/p&gt;
&lt;p&gt;Independently, regmap_read() takes an unsigned int * and stores a full
unsigned int at the destination. Passing the byte pointer msg + i means
each iteration writes four bytes; the high three are zero (val_bits is
8) and are normally overwritten by the next iteration, but the final
iteration&amp;amp;apos;s high bytes are not. With RXBYTES == 30 the i == 29 iteration
already writes three zero bytes past msg, which sits on the IRQ thread&amp;amp;apos;s
stack in wcove_typec_irq().&lt;/p&gt;
&lt;p&gt;Clamp the loop to sizeof(struct pd_message) and read each register into
a local before storing only its low…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: typec: wcove: don&amp;amp;apos;t write past struct pd_message in wcove_read_rx_buffer()&lt;/p&gt;
&lt;p&gt;wcove_read_rx_buffer() copies the PD RX FIFO into the caller&amp;amp;apos;s
struct pd_message with&lt;/p&gt;
&lt;p&gt;for (i = 0; i &amp;amp;lt; USBC_RXINFO_RXBYTES(info); i++)
		regmap_read(wcove-&amp;amp;gt;regmap, USBC_RX_DATA + i, msg + i);&lt;/p&gt;
&lt;p&gt;which has two problems:&lt;/p&gt;
&lt;p&gt;USBC_RXINFO_RXBYTES() is a 5-bit field (max 31) while struct pd_message
is 30 bytes (__le16 header + __le32 payload[PD_MAX_PAYLOAD], packed).
The byte count latched in RXINFO is the number of bytes the port partner
put on the wire, so a malicious partner that transmits a 31-byte frame
can drive the loop one byte past the destination if the WCOVE BMC
receiver does not enforce the PD object-count limit in hardware. The
existing FIXME flagged this as unverified.&lt;/p&gt;
&lt;p&gt;Independently, regmap_read() takes an unsigned int * and stores a full
unsigned int at the destination. Passing the byte pointer msg + i means
each iteration writes four bytes; the high three are zero (val_bits is
8) and are normally overwritten by the next iteration, but the final
iteration&amp;amp;apos;s high bytes are not. With RXBYTES == 30 the i == 29 iteration
already writes three zero bytes past msg, which sits on the IRQ thread&amp;amp;apos;s
stack in wcove_typec_irq().&lt;/p&gt;
&lt;p&gt;Clamp the loop to sizeof(struct pd_message) and read each register into
a local before storing only its low…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-4898</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-90174</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-90174</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 194 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix slab-out-of-bounds read in ksmbd_alloc_user() ksmbd_alloc_user() copies resp-&amp;gt;hash_sz bytes out of the mountd IPC login response with 	user-&amp;gt;passkey_sz = resp-&amp;gt;hash_sz; 	user-&amp;gt;passkey = kmalloc(resp-&amp;gt;hash_sz, KSMBD_DEFAULT_GFP); 	if (user-&amp;gt;passkey) 		memcpy(user-&amp;gt;passkey, resp-&amp;gt;hash, resp-&amp;gt;hash_sz); resp-&amp;gt;hash_sz is a __u16 supplied by the response, but resp-&amp;gt;hash[] is only KSMBD_REQ_MAX_HASH_SZ bytes.  A malformed or malicious login response can set hash_sz well beyond that (up to 65535), so the memcpy() reads past the end of the response object.  ipc_validate_msg() does not bound hash_sz, so reject any response whose hash_sz exceeds the on-stack hash[] buffer before allocating and copying. [ 2030.238706] BUG: KASAN: slab-out-of-bounds in ksmbd_alloc_user+0x278/0x680 [ 2030.240549] Read of size 65535 at addr ffff888121bb6680 by task kworker/4:1/18611 [ 2030.242296] [ 2030.242710] CPU: 4 UID: 0 PID: 18611 Comm: kworker/4:1 Not tainted 7.1.0-next-20260623-virtme #96 PREEMPT(lazy) [ 2030.242732] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 [ 2030.242743] Workqueue: ksmbd-io handle_ksmbd_work [ 2030.242763] Call Trace: [ 2030.242769]  &amp;lt;TASK&amp;gt; [ 2030.242776]  dump_stack_lvl+0xa2/0xd0 [ 2030.242794]  print_address_description+0x77/0x200 [ 2030.242815]  ? ksmbd_alloc_user+0x278/0x680 [ 2030.242831]  print_report+0x58/0x70 [ 2030.242848]  kasan_report+0x117…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 194 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix slab-out-of-bounds read in ksmbd_alloc_user() ksmbd_alloc_user() copies resp-&amp;gt;hash_sz bytes out of the mountd IPC login response with 	user-&amp;gt;passkey_sz = resp-&amp;gt;hash_sz; 	user-&amp;gt;passkey = kmalloc(resp-&amp;gt;hash_sz, KSMBD_DEFAULT_GFP); 	if (user-&amp;gt;passkey) 		memcpy(user-&amp;gt;passkey, resp-&amp;gt;hash, resp-&amp;gt;hash_sz); resp-&amp;gt;hash_sz is a __u16 supplied by the response, but resp-&amp;gt;hash[] is only KSMBD_REQ_MAX_HASH_SZ bytes.  A malformed or malicious login response can set hash_sz well beyond that (up to 65535), so the memcpy() reads past the end of the response object.  ipc_validate_msg() does not bound hash_sz, so reject any response whose hash_sz exceeds the on-stack hash[] buffer before allocating and copying. [ 2030.238706] BUG: KASAN: slab-out-of-bounds in ksmbd_alloc_user+0x278/0x680 [ 2030.240549] Read of size 65535 at addr ffff888121bb6680 by task kworker/4:1/18611 [ 2030.242296] [ 2030.242710] CPU: 4 UID: 0 PID: 18611 Comm: kworker/4:1 Not tainted 7.1.0-next-20260623-virtme #96 PREEMPT(lazy) [ 2030.242732] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 [ 2030.242743] Workqueue: ksmbd-io handle_ksmbd_work [ 2030.242763] Call Trace: [ 2030.242769]  &amp;lt;TASK&amp;gt; [ 2030.242776]  dump_stack_lvl+0xa2/0xd0 [ 2030.242794]  print_address_description+0x77/0x200 [ 2030.242815]  ? ksmbd_alloc_user+0x278/0x680 [ 2030.242831]  print_report+0x58/0x70 [ 2030.242848]  kasan_report+0x117…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-90174</guid>
    </item>
  </channel>
</rss>
