<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T03:35:07.679498+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/bell-cve-2026-99224</id>
    <title>BELL-CVE-2026-99224</title>
    <updated>2026-11-19T03:35:07.688046+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-99224"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-399105</id>
    <title>EUVD-2026-399105</title>
    <updated>2026-11-19T03:35:07.688095+00:00</updated>
    <content>EUVD-2026-399105</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-399105"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99224</id>
    <title>fkie_cve-2026-99224</title>
    <updated>2026-11-19T03:35:07.688109+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>keys: Protect the type name while describing a key</p>
<p>keyctl_describe_key() must keep the key type's name alive until
kasprintf() has consumed it. The retained key reference keeps the key
and its description alive, but does not pin the module providing its
type. The name is passed to kasprintf() without holding key-&gt;sem.</p>
<p>kvasprintf() uses the saved name pointer in two formatting passes, with
a GFP_KERNEL allocation between them. With AF_RXRPC=m, a task that
passes View permission before type retirement can overlap a privileged
module unload in this order:</p>
<p>1. KEYCTL_DESCRIBE looks up the key, saves key-&gt;type-&gt;name in the
   kasprintf() arguments and completes the first formatting pass.
2. While the formatter is delayed before its second pass,
   af_rxrpc_exit() calls unregister_key_type(), which removes the type
   from the registry and waits for key_gc_keytype().
3. The collector takes key-&gt;sem for writing, retypes the retained key
   to key_type_dead and completes retirement. Unregistration and module
   exit return, allowing free_module() to release the type and name.
4. The formatter resumes its second pass and reads the saved name from
   released module storage, which can fault in string().</p>
<p>Hold key-&gt;sem for reading across kasprintf(). The collector then cannot
retype the key or complete retirement until both formatting passes have
finished. If retirement wins the lock first, formatting uses the core…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-99224"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-hcgw-fq49-4f77</id>
    <title>GHSA-hcgw-fq49-4f77</title>
    <updated>2026-11-19T03:35:07.688153+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>keys: Protect the type name while describing a key</p>
<p>keyctl_describe_key() must keep the key type's name alive until
kasprintf() has consumed it. The retained key reference keeps the key
and its description alive, but does not pin the module providing its
type. The name is passed to kasprintf() without holding key-&gt;sem.</p>
<p>kvasprintf() uses the saved name pointer in two formatting passes, with
a GFP_KERNEL allocation between them. With AF_RXRPC=m, a task that
passes View permission before type retirement can overlap a privileged
module unload in this order:</p>
<p>1. KEYCTL_DESCRIBE looks up the key, saves key-&gt;type-&gt;name in the
   kasprintf() arguments and completes the first formatting pass.
2. While the formatter is delayed before its second pass,
   af_rxrpc_exit() calls unregister_key_type(), which removes the type
   from the registry and waits for key_gc_keytype().
3. The collector takes key-&gt;sem for writing, retypes the retained key
   to key_type_dead and completes retirement. Unregistration and module
   exit return, allowing free_module() to release the type and name.
4. The formatter resumes its second pass and reads the saved name from
   released module storage, which can fault in string().</p>
<p>Hold key-&gt;sem for reading across kasprintf(). The collector then cannot
retype the key or complete retirement until both formatting passes have
finished. If retirement wins the lock first, formatting uses the core…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-hcgw-fq49-4f77"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99224</id>
    <title>msrc_CVE-2026-99224 — keys: Protect the type name while describing a key</title>
    <updated>2026-11-19T03:35:07.688185+00:00</updated>
    <content>msrc_CVE-2026-99224</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-99224"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2026-4898</id>
    <title>OESA-2026-4898 — kernel security update</title>
    <updated>2026-11-19T03:35:07.688202+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>usb: typec: wcove: don&amp;apos;t write past struct pd_message in wcove_read_rx_buffer()</p>
<p>wcove_read_rx_buffer() copies the PD RX FIFO into the caller&amp;apos;s
struct pd_message with</p>
<p>for (i = 0; i &amp;lt; USBC_RXINFO_RXBYTES(info); i++)
		regmap_read(wcove-&amp;gt;regmap, USBC_RX_DATA + i, msg + i);</p>
<p>which has two problems:</p>
<p>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.</p>
<p>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;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;apos;s
stack in wcove_typec_irq().</p>
<p>Clamp the loop to sizeof(struct pd_message) and read each register into
a local before storing only its low…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2026-4898"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99224</id>
    <title>UBUNTU-CVE-2026-99224</title>
    <updated>2026-11-19T03:35:07.688336+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 257 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: keys: Protect the type name while describing a key keyctl_describe_key() must keep the key type's name alive until kasprintf() has consumed it. The retained key reference keeps the key and its description alive, but does not pin the module providing its type. The name is passed to kasprintf() without holding key-&gt;sem. kvasprintf() uses the saved name pointer in two formatting passes, with a GFP_KERNEL allocation between them. With AF_RXRPC=m, a task that passes View permission before type retirement can overlap a privileged module unload in this order: 1. KEYCTL_DESCRIBE looks up the key, saves key-&gt;type-&gt;name in the    kasprintf() arguments and completes the first formatting pass. 2. While the formatter is delayed before its second pass,    af_rxrpc_exit() calls unregister_key_type(), which removes the type    from the registry and waits for key_gc_keytype(). 3. The collector takes key-&gt;sem for writing, retypes the retained key    to key_type_dead and completes retirement. Unregistration and module    exit return, allowing free_module() to release the type and name. 4. The formatter resumes its second pass and reads the saved name from    released module storage, which can fault in string(). Hold key-&gt;sem for reading across kasprintf(). The collector then cannot retype the key or complete retirement until both formatting passes have finished. If retirement wins the lock first, formatting uses the core key_t…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99224"/>
  </entry>
</feed>
