<?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 00:44:25 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-47659</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-47659</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-47659</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0957 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0957</link>
      <description>certfr-2024-avi-0957</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0957</guid>
    </item>
    <item>
      <title>OESA-2024-2325 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2325</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: make sure that WRITTEN is set on all metadata blocks&#13;
&#13;
We previously would call btrfs_check_leaf() if we had the check
integrity code enabled, which meant that we could only run the extended
leaf checks if we had WRITTEN set on the header flags.&#13;
&#13;
This leaves a gap in our checking, because we could end up with
corruption on disk where WRITTEN isn&amp;amp;apos;t set on the leaf, and then the
extended leaf checks don&amp;amp;apos;t get run which we rely on to validate all of
the item pointers to make sure we don&amp;amp;apos;t access memory outside of the
extent buffer.&#13;
&#13;
However, since 732fab95abe2 (&amp;amp;quot;btrfs: check-integrity: remove
CONFIG_BTRFS_FS_CHECK_INTEGRITY option&amp;amp;quot;) we no longer call
btrfs_check_leaf() from btrfs_mark_buffer_dirty(), which means we only
ever c…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: make sure that WRITTEN is set on all metadata blocks&#13;
&#13;
We previously would call btrfs_check_leaf() if we had the check
integrity code enabled, which meant that we could only run the extended
leaf checks if we had WRITTEN set on the header flags.&#13;
&#13;
This leaves a gap in our checking, because we could end up with
corruption on disk where WRITTEN isn&amp;amp;apos;t set on the leaf, and then the
extended leaf checks don&amp;amp;apos;t get run which we rely on to validate all of
the item pointers to make sure we don&amp;amp;apos;t access memory outside of the
extent buffer.&#13;
&#13;
However, since 732fab95abe2 (&amp;amp;quot;btrfs: check-integrity: remove
CONFIG_BTRFS_FS_CHECK_INTEGRITY option&amp;amp;quot;) we no longer call
btrfs_check_leaf() from btrfs_mark_buffer_dirty(), which means we only
ever c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2325</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-47659</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-47659</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: smack: tcp: ipv4, fix incorrect labeling Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label &amp;#39;foo&amp;#39; connects to a label &amp;#39;bar&amp;#39; with tcp/ipv4, &amp;#39;foo&amp;#39; always gets &amp;#39;foo&amp;#39; in returned ipv4 packets. So, 1) returned packets are incorrectly labeled (&amp;#39;foo&amp;#39; instead of &amp;#39;bar&amp;#39;) 2) &amp;#39;bar&amp;#39; can write to &amp;#39;foo&amp;#39; without being authorized to write. Here is a scenario how to see this: * Take two machines, let&amp;#39;s call them C and S,    with active Smack in the default state    (no settings, no rules, no labeled hosts, only builtin labels) * At S, add Smack rule &amp;#39;foo bar w&amp;#39;    (labels &amp;#39;foo&amp;#39; and &amp;#39;bar&amp;#39; are instantiated at S at this moment) * At S, at label &amp;#39;bar&amp;#39;, launch a program    that listens for incoming tcp/ipv4 connections * From C, at label &amp;#39;foo&amp;#39;, connect to the listener at S.    (label &amp;#39;foo&amp;#39; is instantiated at C at this moment)    Connection succeedes and works. * Send some data in both directions. * Collect network traffic of this connection. All packets in both directions are labeled with the CIPSO of the label &amp;#39;foo&amp;#39;. Hence, label &amp;#39;bar&amp;#39; writes to &amp;#39;foo&amp;#39; without being authorized, and even without ever being known at C. If anybody cares: exactly the same happens with DCCP. This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided. I changed returned packes label into the &amp;#39;bar&amp;#39;, to bring it into line with the Smack documentation c…&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: smack: tcp: ipv4, fix incorrect labeling Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label &amp;#39;foo&amp;#39; connects to a label &amp;#39;bar&amp;#39; with tcp/ipv4, &amp;#39;foo&amp;#39; always gets &amp;#39;foo&amp;#39; in returned ipv4 packets. So, 1) returned packets are incorrectly labeled (&amp;#39;foo&amp;#39; instead of &amp;#39;bar&amp;#39;) 2) &amp;#39;bar&amp;#39; can write to &amp;#39;foo&amp;#39; without being authorized to write. Here is a scenario how to see this: * Take two machines, let&amp;#39;s call them C and S,    with active Smack in the default state    (no settings, no rules, no labeled hosts, only builtin labels) * At S, add Smack rule &amp;#39;foo bar w&amp;#39;    (labels &amp;#39;foo&amp;#39; and &amp;#39;bar&amp;#39; are instantiated at S at this moment) * At S, at label &amp;#39;bar&amp;#39;, launch a program    that listens for incoming tcp/ipv4 connections * From C, at label &amp;#39;foo&amp;#39;, connect to the listener at S.    (label &amp;#39;foo&amp;#39; is instantiated at C at this moment)    Connection succeedes and works. * Send some data in both directions. * Collect network traffic of this connection. All packets in both directions are labeled with the CIPSO of the label &amp;#39;foo&amp;#39;. Hence, label &amp;#39;bar&amp;#39; writes to &amp;#39;foo&amp;#39; without being authorized, and even without ever being known at C. If anybody cares: exactly the same happens with DCCP. This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided. I changed returned packes label into the &amp;#39;bar&amp;#39;, to bring it into line with the Smack documentation c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-47659</guid>
    </item>
  </channel>
</rss>
