<?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>Thu, 19 Nov 2026 19:51:22 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2023-52882</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2023-52882</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-52882</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0472 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0472</link>
      <description>certfr-2024-avi-0472</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0472</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-52882</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2023-52882</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: clk: sunxi-ng: h6: Reparent CPUX during PLL CPUX rate change While PLL CPUX clock rate change when CPU is running from it works in vast majority of cases, now and then it causes instability. This leads to system crashes and other undefined behaviour. After a lot of testing (30+ hours) while also doing a lot of frequency switches, we can&amp;#39;t observe any instability issues anymore when doing reparenting to stable clock like 24 MHz oscillator.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: clk: sunxi-ng: h6: Reparent CPUX during PLL CPUX rate change While PLL CPUX clock rate change when CPU is running from it works in vast majority of cases, now and then it causes instability. This leads to system crashes and other undefined behaviour. After a lot of testing (30+ hours) while also doing a lot of frequency switches, we can&amp;#39;t observe any instability issues anymore when doing reparenting to stable clock like 24 MHz oscillator.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2023-52882</guid>
    </item>
  </channel>
</rss>
