<?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-18T03:57:40.622799+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-98454</id>
    <title>BELL-CVE-2026-98454</title>
    <updated>2026-11-18T03:57:40.810016+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-98454"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1375</id>
    <title>certfr-2026-avi-1375 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
    <updated>2026-11-18T03:57:40.810072+00:00</updated>
    <content>certfr-2026-avi-1375</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1375"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-395977</id>
    <title>EUVD-2026-395977</title>
    <updated>2026-11-18T03:57:40.810092+00:00</updated>
    <content>EUVD-2026-395977</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-395977"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98454</id>
    <title>fkie_cve-2026-98454</title>
    <updated>2026-11-18T03:57:40.810104+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>smb: client: fix create context out-of-bounds reads</p>
<p>smb2_parse_contexts() validates the complete create-context area but
does not limit each record to its Next field before dispatching it.  A
malformed chain can therefore expose bytes beyond the current context to
a handler.  The QFid handler also used a full response-structure cast
although it only reads DiskFileId.</p>
<p>The SMB2/SMB3 lease parsers made the same layout assumption: they read
LeaseState and LeaseFlags at canonical offsets rather than at
DataOffset.  A valid non-canonical DataOffset could therefore yield
unrelated in-bounds data, while a short DataLength was still accepted.</p>
<p>Limit each context to its Next value, reject offsets before the context
header, and reject malformed chains.  Bound the name range by the current
context and do not dispatch a known handler when DataLength is zero.  Read
the QFid DiskFileId only when the context data covers that field.  Parse the
lease context from DataOffset and require DataLength to match the v1 or v2
lease_context size used by ksmbd.  A size mismatch skips lease parsing
without failing the open.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-98454"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-q4c4-v5h3-5c35</id>
    <title>GHSA-q4c4-v5h3-5c35</title>
    <updated>2026-11-18T03:57:40.810137+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>smb: client: fix create context out-of-bounds reads</p>
<p>smb2_parse_contexts() validates the complete create-context area but
does not limit each record to its Next field before dispatching it.  A
malformed chain can therefore expose bytes beyond the current context to
a handler.  The QFid handler also used a full response-structure cast
although it only reads DiskFileId.</p>
<p>The SMB2/SMB3 lease parsers made the same layout assumption: they read
LeaseState and LeaseFlags at canonical offsets rather than at
DataOffset.  A valid non-canonical DataOffset could therefore yield
unrelated in-bounds data, while a short DataLength was still accepted.</p>
<p>Limit each context to its Next value, reject offsets before the context
header, and reject malformed chains.  Bound the name range by the current
context and do not dispatch a known handler when DataLength is zero.  Read
the QFid DiskFileId only when the context data covers that field.  Parse the
lease context from DataOffset and require DataLength to match the v1 or v2
lease_context size used by ksmbd.  A size mismatch skips lease parsing
without failing the open.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-q4c4-v5h3-5c35"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98454</id>
    <title>msrc_CVE-2026-98454 — smb: client: fix create context out-of-bounds reads</title>
    <updated>2026-11-18T03:57:40.810161+00:00</updated>
    <content>msrc_CVE-2026-98454</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-98454"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2026-4718</id>
    <title>OESA-2026-4718 — kernel security update</title>
    <updated>2026-11-18T03:57:40.810178+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>can: esd_usb: kill anchored URBs before freeing netdevs</p>
<p>esd_usb_disconnect() frees each CAN netdev with free_candev() inside
its per-netdev loop and only calls unlink_all_urbs(dev) afterwards.
The per-netdev private data (struct esd_usb_net_priv) is embedded in
the net_device allocation returned by alloc_candev(), so once
free_candev() has run, dev-&amp;gt;nets[i] points to freed memory.
unlink_all_urbs() then dereferences the freed dev-&amp;gt;nets[i] to kill the
per-netdev TX anchor (usb_kill_anchored_urbs(&amp;amp;priv-&amp;gt;tx_submitted)),
clear active_tx_jobs, and reset priv-&amp;gt;tx_contexts[].</p>
<p>Reorder the teardown so the anchored URBs are killed before the netdevs
are freed, matching other CAN/USB drivers in the same directory such as
ems_usb, usb_8dev and mcba_usb, which unregister, then unlink, then
free: unregister the netdevs first (which stops their TX queues), call
unlink_all_urbs(dev) once, then free the netdevs.</p>
<p>This issue was found by an in-house static analysis tool.(CVE-2026-64585)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ocfs2: avoid moving extents to occupied clusters</p>
<p>For non-auto OCFS2_IOC_MOVE_EXT operations, userspace supplies a physical
me_goal.  ocfs2_move_extent() initializes new_phys_cpos from that goal and
expects ocfs2_probe_alloc_group() to replace it with a free run in the
target block g…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2026-4718"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98454</id>
    <title>UBUNTU-CVE-2026-98454</title>
    <updated>2026-11-18T03:57:40.810335+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, 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 and 248 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: smb: client: fix create context out-of-bounds reads smb2_parse_contexts() validates the complete create-context area but does not limit each record to its Next field before dispatching it.  A malformed chain can therefore expose bytes beyond the current context to a handler.  The QFid handler also used a full response-structure cast although it only reads DiskFileId. The SMB2/SMB3 lease parsers made the same layout assumption: they read LeaseState and LeaseFlags at canonical offsets rather than at DataOffset.  A valid non-canonical DataOffset could therefore yield unrelated in-bounds data, while a short DataLength was still accepted. Limit each context to its Next value, reject offsets before the context header, and reject malformed chains.  Bound the name range by the current context and do not dispatch a known handler when DataLength is zero.  Read the QFid DiskFileId only when the context data covers that field.  Parse the lease context from DataOffset and require DataLength to match the v1 or v2 lease_context size used by ksmbd.  A size mismatch skips lease parsing without failing the open.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98454"/>
  </entry>
</feed>
