<?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 02:48:07 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:10943 — Moderate: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2024:10943</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 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: selinux,smack: don&amp;#39;t bypass permissions check in inode_setsecctx hook (CVE-2024-46695)
  * kernel: net: avoid potential underflow in qdisc_pkt_len_init() with UFO (CVE-2024-49949)
  * kernel: blk-rq-qos: fix crash on rq_qos_wait vs. rq_qos_wake_function race (CVE-2024-50082)
  * kernel: arm64: probes: Remove broken LDR (literal) uprobe support (CVE-2024-50099)
  * kernel: xfrm: fix one more kernel-infoleak in algo dumping (CVE-2024-50110)
  * kernel: xfrm: validate new SA&amp;amp;#39;s prefixlen using SA family when sel.family is unset (CVE-2024-50142)
  * kernel: irqchip/gic-v4: Don&amp;#39;t allow a VMOVP on a dying VPE (CVE-2024-50192)
  * kernel: netfilter: nf_reject_ipv6: fix potential crash in nf_send_reset6() (CVE-2024-50256)
  * kernel: vsock/virtio: Initialization of the dangling pointer occurring in vsk-&amp;gt;trans (CVE-2024-50264)&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:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 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: selinux,smack: don&amp;#39;t bypass permissions check in inode_setsecctx hook (CVE-2024-46695)
  * kernel: net: avoid potential underflow in qdisc_pkt_len_init() with UFO (CVE-2024-49949)
  * kernel: blk-rq-qos: fix crash on rq_qos_wait vs. rq_qos_wake_function race (CVE-2024-50082)
  * kernel: arm64: probes: Remove broken LDR (literal) uprobe support (CVE-2024-50099)
  * kernel: xfrm: fix one more kernel-infoleak in algo dumping (CVE-2024-50110)
  * kernel: xfrm: validate new SA&amp;amp;#39;s prefixlen using SA family when sel.family is unset (CVE-2024-50142)
  * kernel: irqchip/gic-v4: Don&amp;#39;t allow a VMOVP on a dying VPE (CVE-2024-50192)
  * kernel: netfilter: nf_reject_ipv6: fix potential crash in nf_send_reset6() (CVE-2024-50256)
  * kernel: vsock/virtio: Initialization of the dangling pointer occurring in vsk-&amp;gt;trans (CVE-2024-50264)&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:10943</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-50142</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-50142</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-50142</guid>
    </item>
    <item>
      <title>certfr-2024-avi-1078 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-1078</link>
      <description>certfr-2024-avi-1078</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-1078</guid>
    </item>
    <item>
      <title>OESA-2024-2424 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2424</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;
pinctrl: single: fix potential NULL dereference in pcs_get_function()&#13;
&#13;
pinmux_generic_get_function() can return NULL and the pointer &amp;amp;apos;function&amp;amp;apos;
was dereferenced without checking against NULL. Add checking of pointer
&amp;amp;apos;function&amp;amp;apos; in pcs_get_function().&#13;
&#13;
Found by code review.(CVE-2024-46685)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
thunderbolt: Mark XDomain as unplugged when router is removed&#13;
&#13;
I noticed that when we do discrete host router NVM upgrade and it gets
hot-removed from the PCIe side as a result of NVM firmware authentication,
if there is another host connected with enabled paths we hang in tearing
them down. This is due to fact that the Thunderbolt networking driver
also tries to cleanup the paths and ends up blocking in
tb_disconnect_xdomain_paths() waiting for the domain lock.&#13;
&#13;
However, at this point we already cleaned the paths in tb_stop() so
there is really no need for tb_disconnect_xdomain_paths() to do that
anymore. Furthermore it already checks if the XDomain is unplugged and
bails out early so take advantage of that and mark the XDomain as
unplugged when we remove the parent router.(CVE-2024-46702)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[]&#13;
&#13;
[WHY &amp;amp;amp;…&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;
pinctrl: single: fix potential NULL dereference in pcs_get_function()&#13;
&#13;
pinmux_generic_get_function() can return NULL and the pointer &amp;amp;apos;function&amp;amp;apos;
was dereferenced without checking against NULL. Add checking of pointer
&amp;amp;apos;function&amp;amp;apos; in pcs_get_function().&#13;
&#13;
Found by code review.(CVE-2024-46685)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
thunderbolt: Mark XDomain as unplugged when router is removed&#13;
&#13;
I noticed that when we do discrete host router NVM upgrade and it gets
hot-removed from the PCIe side as a result of NVM firmware authentication,
if there is another host connected with enabled paths we hang in tearing
them down. This is due to fact that the Thunderbolt networking driver
also tries to cleanup the paths and ends up blocking in
tb_disconnect_xdomain_paths() waiting for the domain lock.&#13;
&#13;
However, at this point we already cleaned the paths in tb_stop() so
there is really no need for tb_disconnect_xdomain_paths() to do that
anymore. Furthermore it already checks if the XDomain is unplugged and
bails out early so take advantage of that and mark the XDomain as
unplugged when we remove the parent router.(CVE-2024-46702)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[]&#13;
&#13;
[WHY &amp;amp;amp;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2424</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-50142</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-50142</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 195 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfrm: validate new SA&amp;#39;s prefixlen using SA family when sel.family is unset This expands the validation introduced in commit 07bf7908950a (&amp;#34;xfrm: Validate address prefix lengths in the xfrm selector.&amp;#34;) syzbot created an SA with     usersa.sel.family = AF_UNSPEC     usersa.sel.prefixlen_s = 128     usersa.family = AF_INET Because of the AF_UNSPEC selector, verify_newsa_info doesn&amp;#39;t put limits on prefixlen_{s,d}. But then copy_from_user_state sets x-&amp;gt;sel.family to usersa.family (AF_INET). Do the same conversion in verify_newsa_info before validating prefixlen_{s,d}, since that&amp;#39;s how prefixlen is going to be used later on.&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 195 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfrm: validate new SA&amp;#39;s prefixlen using SA family when sel.family is unset This expands the validation introduced in commit 07bf7908950a (&amp;#34;xfrm: Validate address prefix lengths in the xfrm selector.&amp;#34;) syzbot created an SA with     usersa.sel.family = AF_UNSPEC     usersa.sel.prefixlen_s = 128     usersa.family = AF_INET Because of the AF_UNSPEC selector, verify_newsa_info doesn&amp;#39;t put limits on prefixlen_{s,d}. But then copy_from_user_state sets x-&amp;gt;sel.family to usersa.family (AF_INET). Do the same conversion in verify_newsa_info before validating prefixlen_{s,d}, since that&amp;#39;s how prefixlen is going to be used later on.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-50142</guid>
    </item>
  </channel>
</rss>
