<?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-10-06T12:03:51.209255+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/cve-2023-53331</id>
    <title>CVE-2023-53331 — pstore/ram: Check start of empty przs during init</title>
    <updated>2026-10-06T12:03:51.310214+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>pstore/ram: Check start of empty przs during init</p>
<p>After commit 30696378f68a ("pstore/ram: Do not treat empty buffers as
valid"), initialization would assume a prz was valid after seeing that
the buffer_size is zero (regardless of the buffer start position). This
unchecked start value means it could be outside the bounds of the buffer,
leading to future access panics when written to:</p>
<p>sysdump_panic_event+0x3b4/0x5b8
 atomic_notifier_call_chain+0x54/0x90
 panic+0x1c8/0x42c
 die+0x29c/0x2a8
 die_kernel_fault+0x68/0x78
 __do_kernel_fault+0x1c4/0x1e0
 do_bad_area+0x40/0x100
 do_translation_fault+0x68/0x80
 do_mem_abort+0x68/0xf8
 el1_da+0x1c/0xc0
 __raw_writeb+0x38/0x174
 __memcpy_toio+0x40/0xac
 persistent_ram_update+0x44/0x12c
 persistent_ram_write+0x1a8/0x1b8
 ramoops_pstore_write+0x198/0x1e8
 pstore_console_write+0x94/0xe0
 ...</p>
<p>To avoid this, also check if the prz start is 0 during the initialization
phase. If not, the next prz sanity check case will discover it (start &gt;
size) and zap the buffer back to a sane state.</p>
<p>[kees: update commit log with backtrace and clarifications]</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2023-53331"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2025:19105</id>
    <title>RHSA-2025:19105 — Red Hat Security Advisory: kernel security update</title>
    <updated>2026-10-06T12:03:51.310309+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel: pstore/ram: Check start of empty przs during init kernel: block: fix adding folio to bio kernel: vsock/virtio: Validate length in packet header before skb_put() kernel: NFS: Fix filehandle bounds checking in nfs_fh_to_dentry() kernel: Linux kernel ALSA hda/ca0132 buffer overflow kernel: Linux kernel: Denial of Service via resource leak in SMB2 compound operations</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2025:19105"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2025:19886</id>
    <title>RHSA-2025:19886 — Red Hat Security Advisory: kernel security update</title>
    <updated>2026-10-06T12:03:51.310342+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel: fs: fix UAF/GPF bug in nilfs_mdt_destroy kernel: mm: fix zswap writeback race condition kernel: pstore/ram: Check start of empty przs during init kernel: mm: kmem: fix a NULL pointer dereference in obj_stock_flush_required() kernel: ethtool: check device is present when getting link settings kernel: NFS: Fix filehandle bounds checking in nfs_fh_to_dentry()</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2025:19886"/>
  </entry>
</feed>
