<?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 05:29:30 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-50186</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-50186</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-50186</guid>
    </item>
    <item>
      <title>certfr-2024-avi-1101 — 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-1101</link>
      <description>certfr-2024-avi-1101</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-1101</guid>
    </item>
    <item>
      <title>OESA-2024-2423 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2423</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:&#13;
&#13;
usb: typec: ucsi: Fix null pointer dereference in trace&#13;
&#13;
ucsi_register_altmode checks IS_ERR for the alt pointer and treats
NULL as valid. When CONFIG_TYPEC_DP_ALTMODE is not enabled,
ucsi_register_displayport returns NULL which causes a NULL pointer
dereference in trace. Rather than return NULL, call
typec_port_register_altmode to register DisplayPort alternate mode
as a non-controllable mode when CONFIG_TYPEC_DP_ALTMODE is not enabled.(CVE-2024-46719)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
x86/tdx: Fix data leak in mmio_read()&#13;
&#13;
The mmio_read() function makes a TDVMCALL to retrieve MMIO data for an
address from the VMM.&#13;
&#13;
Sean noticed that mmio_read() unintentionally exposes the value of an
initialized variable (val) on the stack to the VMM.&#13;
&#13;
This variable is only needed as an output value. It did not need to be
passed to the VMM in the first place.&#13;
&#13;
Do not send the original value of *val to the VMM.&#13;
&#13;
[ dhansen: clarify what &amp;amp;apos;val&amp;amp;apos; is used for. ](CVE-2024-46794)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/amdkfd: Check debug trap enable before write dbg_ev_file&#13;
&#13;
In interrupt context, write dbg_ev_file will be run by work queue. It
will cause write dbg_ev_file execution after debug_trap_disable, which
will cause NULL pointer access.
v2: canc…&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:&#13;
&#13;
usb: typec: ucsi: Fix null pointer dereference in trace&#13;
&#13;
ucsi_register_altmode checks IS_ERR for the alt pointer and treats
NULL as valid. When CONFIG_TYPEC_DP_ALTMODE is not enabled,
ucsi_register_displayport returns NULL which causes a NULL pointer
dereference in trace. Rather than return NULL, call
typec_port_register_altmode to register DisplayPort alternate mode
as a non-controllable mode when CONFIG_TYPEC_DP_ALTMODE is not enabled.(CVE-2024-46719)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
x86/tdx: Fix data leak in mmio_read()&#13;
&#13;
The mmio_read() function makes a TDVMCALL to retrieve MMIO data for an
address from the VMM.&#13;
&#13;
Sean noticed that mmio_read() unintentionally exposes the value of an
initialized variable (val) on the stack to the VMM.&#13;
&#13;
This variable is only needed as an output value. It did not need to be
passed to the VMM in the first place.&#13;
&#13;
Do not send the original value of *val to the VMM.&#13;
&#13;
[ dhansen: clarify what &amp;amp;apos;val&amp;amp;apos; is used for. ](CVE-2024-46794)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/amdkfd: Check debug trap enable before write dbg_ev_file&#13;
&#13;
In interrupt context, write dbg_ev_file will be run by work queue. It
will cause write dbg_ev_file execution after debug_trap_disable, which
will cause NULL pointer access.
v2: canc…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2423</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-50186</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-50186</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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 134 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: explicitly clear the sk pointer, when pf-&amp;gt;create fails We have recently noticed the exact same KASAN splat as in commit 6cd4a78d962b (&amp;#34;net: do not leave a dangling sk pointer, when socket creation fails&amp;#34;). The problem is that commit did not fully address the problem, as some pf-&amp;gt;create implementations do not use sk_common_release in their error paths. For example, we can use the same reproducer as in the above commit, but changing ping to arping. arping uses AF_PACKET socket and if packet_create fails, it will just sk_free the allocated sk object. While we could chase all the pf-&amp;gt;create implementations and make sure they NULL the freed sk object on error from the socket, we can&amp;#39;t guarantee future protocols will not make the same mistake. So it is easier to just explicitly NULL the sk pointer upon return from pf-&amp;gt;create in __sock_create. We do know that pf-&amp;gt;create always releases the allocated sk object on error, so if the pointer is not NULL, it is definitely dangling.&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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 134 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: explicitly clear the sk pointer, when pf-&amp;gt;create fails We have recently noticed the exact same KASAN splat as in commit 6cd4a78d962b (&amp;#34;net: do not leave a dangling sk pointer, when socket creation fails&amp;#34;). The problem is that commit did not fully address the problem, as some pf-&amp;gt;create implementations do not use sk_common_release in their error paths. For example, we can use the same reproducer as in the above commit, but changing ping to arping. arping uses AF_PACKET socket and if packet_create fails, it will just sk_free the allocated sk object. While we could chase all the pf-&amp;gt;create implementations and make sure they NULL the freed sk object on error from the socket, we can&amp;#39;t guarantee future protocols will not make the same mistake. So it is easier to just explicitly NULL the sk pointer upon return from pf-&amp;gt;create in __sock_create. We do know that pf-&amp;gt;create always releases the allocated sk object on error, so if the pointer is not NULL, it is definitely dangling.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-50186</guid>
    </item>
  </channel>
</rss>
