<?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 08:59:23 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2023-52670</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2023-52670</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-2023-52670</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0526 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent une élé…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</link>
      <description>certfr-2024-avi-0526</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</guid>
    </item>
    <item>
      <title>OESA-2024-1737 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1737</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
afs: Fix corruption in reads at fpos 2G-4G from an OpenAFS server&#13;
&#13;
AFS-3 has two data fetch RPC variants, FS.FetchData and FS.FetchData64, and
Linux&amp;amp;apos;s afs client switches between them when talking to a non-YFS server
if the read size, the file position or the sum of the two have the upper 32
bits set of the 64-bit value.&#13;
&#13;
This is a problem, however, since the file position and length fields of
FS.FetchData are *signed* 32-bit values.&#13;
&#13;
Fix this by capturing the capability bits obtained from the fileserver when
it&amp;amp;apos;s sent an FS.GetCapabilities RPC, rather than just discarding them, and
then picking out the VICED_CAPABILITY_64BITFILES flag.  This can then be
used to decide whether to use FS.FetchData or FS.FetchData64 - and also
FS.StoreData or FS.StoreData64 - rather than using upper_32_bits() to
switch on the parameter values.&#13;
&#13;
This capabilities flag could also be used to limit the maximum size of the
file, but all servers must be checked for that.&#13;
&#13;
Note that the issue does not exist with FS.StoreData - that uses *unsigned*
32-bit values.  It&amp;amp;apos;s also not a problem with Auristor servers as its
YFS.FetchData64 op uses unsigned 64-bit values.&#13;
&#13;
This can be tested by cloning a git repo through an OpenAFS client to an
OpenAFS server and then doing &amp;amp;quot;git status&amp;amp;quot; on it from a Linux afs
client[1].  Provided…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
afs: Fix corruption in reads at fpos 2G-4G from an OpenAFS server&#13;
&#13;
AFS-3 has two data fetch RPC variants, FS.FetchData and FS.FetchData64, and
Linux&amp;amp;apos;s afs client switches between them when talking to a non-YFS server
if the read size, the file position or the sum of the two have the upper 32
bits set of the 64-bit value.&#13;
&#13;
This is a problem, however, since the file position and length fields of
FS.FetchData are *signed* 32-bit values.&#13;
&#13;
Fix this by capturing the capability bits obtained from the fileserver when
it&amp;amp;apos;s sent an FS.GetCapabilities RPC, rather than just discarding them, and
then picking out the VICED_CAPABILITY_64BITFILES flag.  This can then be
used to decide whether to use FS.FetchData or FS.FetchData64 - and also
FS.StoreData or FS.StoreData64 - rather than using upper_32_bits() to
switch on the parameter values.&#13;
&#13;
This capabilities flag could also be used to limit the maximum size of the
file, but all servers must be checked for that.&#13;
&#13;
Note that the issue does not exist with FS.StoreData - that uses *unsigned*
32-bit values.  It&amp;amp;apos;s also not a problem with Auristor servers as its
YFS.FetchData64 op uses unsigned 64-bit values.&#13;
&#13;
This can be tested by cloning a git repo through an OpenAFS client to an
OpenAFS server and then doing &amp;amp;quot;git status&amp;amp;quot; on it from a Linux afs
client[1].  Provided…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1737</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-52670</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2023-52670</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 152 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rpmsg: virtio: Free driver_override when rpmsg_remove() Free driver_override when rpmsg_remove(), otherwise the following memory leak will occur: unreferenced object 0xffff0000d55d7080 (size 128):   comm &amp;#34;kworker/u8:2&amp;#34;, pid 56, jiffies 4294893188 (age 214.272s)   hex dump (first 32 bytes):     72 70 6d 73 67 5f 6e 73 00 00 00 00 00 00 00 00  rpmsg_ns........     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................   backtrace:     [&amp;lt;000000009c94c9c1&amp;gt;] __kmem_cache_alloc_node+0x1f8/0x320     [&amp;lt;000000002300d89b&amp;gt;] __kmalloc_node_track_caller+0x44/0x70     [&amp;lt;00000000228a60c3&amp;gt;] kstrndup+0x4c/0x90     [&amp;lt;0000000077158695&amp;gt;] driver_set_override+0xd0/0x164     [&amp;lt;000000003e9c4ea5&amp;gt;] rpmsg_register_device_override+0x98/0x170     [&amp;lt;000000001c0c89a8&amp;gt;] rpmsg_ns_register_device+0x24/0x30     [&amp;lt;000000008bbf8fa2&amp;gt;] rpmsg_probe+0x2e0/0x3ec     [&amp;lt;00000000e65a68df&amp;gt;] virtio_dev_probe+0x1c0/0x280     [&amp;lt;00000000443331cc&amp;gt;] really_probe+0xbc/0x2dc     [&amp;lt;00000000391064b1&amp;gt;] __driver_probe_device+0x78/0xe0     [&amp;lt;00000000a41c9a5b&amp;gt;] driver_probe_device+0xd8/0x160     [&amp;lt;000000009c3bd5df&amp;gt;] __device_attach_driver+0xb8/0x140     [&amp;lt;0000000043cd7614&amp;gt;] bus_for_each_drv+0x7c/0xd4     [&amp;lt;000000003b929a36&amp;gt;] __device_attach+0x9c/0x19c     [&amp;lt;00000000a94e0ba8&amp;gt;] device_initial_probe+0x14/0x20     [&amp;lt;000000003c999637&amp;gt;] bus_probe_device+0xa0/0xac&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 152 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rpmsg: virtio: Free driver_override when rpmsg_remove() Free driver_override when rpmsg_remove(), otherwise the following memory leak will occur: unreferenced object 0xffff0000d55d7080 (size 128):   comm &amp;#34;kworker/u8:2&amp;#34;, pid 56, jiffies 4294893188 (age 214.272s)   hex dump (first 32 bytes):     72 70 6d 73 67 5f 6e 73 00 00 00 00 00 00 00 00  rpmsg_ns........     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................   backtrace:     [&amp;lt;000000009c94c9c1&amp;gt;] __kmem_cache_alloc_node+0x1f8/0x320     [&amp;lt;000000002300d89b&amp;gt;] __kmalloc_node_track_caller+0x44/0x70     [&amp;lt;00000000228a60c3&amp;gt;] kstrndup+0x4c/0x90     [&amp;lt;0000000077158695&amp;gt;] driver_set_override+0xd0/0x164     [&amp;lt;000000003e9c4ea5&amp;gt;] rpmsg_register_device_override+0x98/0x170     [&amp;lt;000000001c0c89a8&amp;gt;] rpmsg_ns_register_device+0x24/0x30     [&amp;lt;000000008bbf8fa2&amp;gt;] rpmsg_probe+0x2e0/0x3ec     [&amp;lt;00000000e65a68df&amp;gt;] virtio_dev_probe+0x1c0/0x280     [&amp;lt;00000000443331cc&amp;gt;] really_probe+0xbc/0x2dc     [&amp;lt;00000000391064b1&amp;gt;] __driver_probe_device+0x78/0xe0     [&amp;lt;00000000a41c9a5b&amp;gt;] driver_probe_device+0xd8/0x160     [&amp;lt;000000009c3bd5df&amp;gt;] __device_attach_driver+0xb8/0x140     [&amp;lt;0000000043cd7614&amp;gt;] bus_for_each_drv+0x7c/0xd4     [&amp;lt;000000003b929a36&amp;gt;] __device_attach+0x9c/0x19c     [&amp;lt;00000000a94e0ba8&amp;gt;] device_initial_probe+0x14/0x20     [&amp;lt;000000003c999637&amp;gt;] bus_probe_device+0xa0/0xac&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2023-52670</guid>
    </item>
  </channel>
</rss>
