<?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:41:52 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-46822</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-46822</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-2024-46822</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0837 — 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-0837</link>
      <description>certfr-2024-avi-0837</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0837</guid>
    </item>
    <item>
      <title>OESA-2024-2292 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2292</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: 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;
octeontx2-af: Use separate handlers for interrupts&#13;
&#13;
For PF to AF interrupt vector and VF to AF vector same
interrupt handler is registered which is causing race condition.
When two interrupts are raised to two CPUs at same time
then two cores serve same event corrupting the data.(CVE-2024-27030)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
media: go7007: fix a memleak in go7007_load_encoder&#13;
&#13;
In go7007_load_encoder, bounce(i.e. go-&amp;amp;gt;boot_fw), is allocated without
a deallocation thereafter. After the following call chain:&#13;
&#13;
saa7134_go7007_init
  |-&amp;amp;gt; go7007_boot_encoder
        |-&amp;amp;gt; go7007_load_encoder
  |-&amp;amp;gt; kfree(go)&#13;
&#13;
go is freed and thus bounce is leaked.(CVE-2024-27074)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
netfilter: nf_tables: use timestamp to check for set element timeout&#13;
&#13;
Add a timestamp field at the beginning of the transaction, store it
in the nftables per-netns area.&#13;
&#13;
Update set backend .insert, .deactivate and sync gc path to use the
timestamp, this avoids that an element expires while control plane
transaction is still unfinished.&#13;
&#13;
.lookup and .update, which are used from packet path, still use the
current time to check if the element has expired. And .get path and dump
also since this runs lockless under rcu read size lock. Then, ther…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: 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;
octeontx2-af: Use separate handlers for interrupts&#13;
&#13;
For PF to AF interrupt vector and VF to AF vector same
interrupt handler is registered which is causing race condition.
When two interrupts are raised to two CPUs at same time
then two cores serve same event corrupting the data.(CVE-2024-27030)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
media: go7007: fix a memleak in go7007_load_encoder&#13;
&#13;
In go7007_load_encoder, bounce(i.e. go-&amp;amp;gt;boot_fw), is allocated without
a deallocation thereafter. After the following call chain:&#13;
&#13;
saa7134_go7007_init
  |-&amp;amp;gt; go7007_boot_encoder
        |-&amp;amp;gt; go7007_load_encoder
  |-&amp;amp;gt; kfree(go)&#13;
&#13;
go is freed and thus bounce is leaked.(CVE-2024-27074)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
netfilter: nf_tables: use timestamp to check for set element timeout&#13;
&#13;
Add a timestamp field at the beginning of the transaction, store it
in the nftables per-netns area.&#13;
&#13;
Update set backend .insert, .deactivate and sync gc path to use the
timestamp, this avoids that an element expires while control plane
transaction is still unfinished.&#13;
&#13;
.lookup and .update, which are used from packet path, still use the
current time to check if the element has expired. And .get path and dump
also since this runs lockless under rcu read size lock. Then, ther…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2292</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-46822</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-46822</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 187 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry In a review discussion of the changes to support vCPU hotplug where a check was added on the GICC being enabled if was online, it was noted that there is need to map back to the cpu and use that to index into a cpumask. As such, a valid ID is needed. If an MPIDR check fails in acpi_map_gic_cpu_interface() it is possible for the entry in cpu_madt_gicc[cpu] == NULL.  This function would then cause a NULL pointer dereference.   Whilst a path to trigger this has not been established, harden this caller against the possibility.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 187 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry In a review discussion of the changes to support vCPU hotplug where a check was added on the GICC being enabled if was online, it was noted that there is need to map back to the cpu and use that to index into a cpumask. As such, a valid ID is needed. If an MPIDR check fails in acpi_map_gic_cpu_interface() it is possible for the entry in cpu_madt_gicc[cpu] == NULL.  This function would then cause a NULL pointer dereference.   Whilst a path to trigger this has not been established, harden this caller against the possibility.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-46822</guid>
    </item>
  </channel>
</rss>
