<?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:07 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:9605 — Moderate: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2024:9605</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 53 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: net: nexthop: Initialize all fields in dumped nexthops (CVE-2024-42283)
  * kernel: iommufd: Require drivers to supply the cache_invalidate_user ops (CVE-2024-46824)
  * kernel: mptcp: pm: Fix uaf in __timer_delete_sync (CVE-2024-46858)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 53 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: net: nexthop: Initialize all fields in dumped nexthops (CVE-2024-42283)
  * kernel: iommufd: Require drivers to supply the cache_invalidate_user ops (CVE-2024-46824)
  * kernel: mptcp: pm: Fix uaf in __timer_delete_sync (CVE-2024-46858)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2024:9605</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-42283</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-42283</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-42283</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0779 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0779</link>
      <description>certfr-2024-avi-0779</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0779</guid>
    </item>
    <item>
      <title>OESA-2024-2255 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2255</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;
drm/i915/gt: Cleanup partial engine discovery failures&#13;
&#13;
If we abort driver initialisation in the middle of gt/engine discovery,
some engines will be fully setup and some not. Those incompletely setup
engines only have &amp;amp;apos;engine-&amp;amp;gt;release == NULL&amp;amp;apos; and so will leak any of the
common objects allocated.&#13;
&#13;
v2:
 - Drop the destroy_pinned_context() helper for now.  It&amp;amp;apos;s not really
   worth it with just a single callsite at the moment.  (Janusz)(CVE-2022-48893)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
f2fs: fix to avoid dirent corruption&#13;
&#13;
As Al reported in link[1]:&#13;
&#13;
f2fs_rename()
...
	if (old_dir != new_dir &amp;amp;amp;&amp;amp;amp; !whiteout)
		f2fs_set_link(old_inode, old_dir_entry,
					old_dir_page, new_dir);
	else
		f2fs_put_page(old_dir_page, 0);&#13;
&#13;
You want correct inumber in the &amp;amp;quot;..&amp;amp;quot; link.  And cross-directory
rename does move the source to new parent, even if you&amp;amp;apos;d been asked
to leave a whiteout in the old place.&#13;
&#13;
[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/&#13;
&#13;
With below testcase, it may cause dirent corruption, due to it missed
to call f2fs_set_link() to update &amp;amp;quot;..&amp;amp;quot; link to new directory.
- mkdir -p dir/foo
- renameat2 -w dir/foo bar&#13;
&#13;
[ASSERT] (__chk_dots_dentries:1421)  --&amp;amp;gt; Bad inode number[0x4] for &amp;amp;apos;..&amp;amp;apos;, parent parent ino is [0…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;
drm/i915/gt: Cleanup partial engine discovery failures&#13;
&#13;
If we abort driver initialisation in the middle of gt/engine discovery,
some engines will be fully setup and some not. Those incompletely setup
engines only have &amp;amp;apos;engine-&amp;amp;gt;release == NULL&amp;amp;apos; and so will leak any of the
common objects allocated.&#13;
&#13;
v2:
 - Drop the destroy_pinned_context() helper for now.  It&amp;amp;apos;s not really
   worth it with just a single callsite at the moment.  (Janusz)(CVE-2022-48893)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
f2fs: fix to avoid dirent corruption&#13;
&#13;
As Al reported in link[1]:&#13;
&#13;
f2fs_rename()
...
	if (old_dir != new_dir &amp;amp;amp;&amp;amp;amp; !whiteout)
		f2fs_set_link(old_inode, old_dir_entry,
					old_dir_page, new_dir);
	else
		f2fs_put_page(old_dir_page, 0);&#13;
&#13;
You want correct inumber in the &amp;amp;quot;..&amp;amp;quot; link.  And cross-directory
rename does move the source to new parent, even if you&amp;amp;apos;d been asked
to leave a whiteout in the old place.&#13;
&#13;
[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/&#13;
&#13;
With below testcase, it may cause dirent corruption, due to it missed
to call f2fs_set_link() to update &amp;amp;quot;..&amp;amp;quot; link to new directory.
- mkdir -p dir/foo
- renameat2 -w dir/foo bar&#13;
&#13;
[ASSERT] (__chk_dots_dentries:1421)  --&amp;amp;gt; Bad inode number[0x4] for &amp;amp;apos;..&amp;amp;apos;, parent parent ino is [0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2255</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-42283</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-42283</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 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: nexthop: Initialize all fields in dumped nexthops struct nexthop_grp contains two reserved fields that are not initialized by nla_put_nh_group(), and carry garbage. This can be observed e.g. with strace (edited for clarity):     # ip nexthop add id 1 dev lo     # ip nexthop add id 101 group 1     # strace -e recvmsg ip nexthop get id 101     ...     recvmsg(... [{nla_len=12, nla_type=NHA_GROUP},                  [{id=1, weight=0, resvd1=0x69, resvd2=0x67}]] ...) = 52 The fields are reserved and therefore not currently used. But as they are, they leak kernel memory, and the fact they are not just zero complicates repurposing of the fields for new ends. Initialize the full structure.&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 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: nexthop: Initialize all fields in dumped nexthops struct nexthop_grp contains two reserved fields that are not initialized by nla_put_nh_group(), and carry garbage. This can be observed e.g. with strace (edited for clarity):     # ip nexthop add id 1 dev lo     # ip nexthop add id 101 group 1     # strace -e recvmsg ip nexthop get id 101     ...     recvmsg(... [{nla_len=12, nla_type=NHA_GROUP},                  [{id=1, weight=0, resvd1=0x69, resvd2=0x67}]] ...) = 52 The fields are reserved and therefore not currently used. But as they are, they leak kernel memory, and the fact they are not just zero complicates repurposing of the fields for new ends. Initialize the full structure.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-42283</guid>
    </item>
  </channel>
</rss>
