<?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:10:45 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-47702</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-47702</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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: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-47702</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0999 — 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-0999</link>
      <description>certfr-2024-avi-0999</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0999</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-47702</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-47702</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 91 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fail verification for sign-extension of packet data/data_end/data_meta syzbot reported a kernel crash due to   commit 1f1e864b6555 (&amp;#34;bpf: Handle sign-extenstin ctx member accesses&amp;#34;). The reason is due to sign-extension of 32-bit load for packet data/data_end/data_meta uapi field. The original code looks like:         r2 = *(s32 *)(r1 + 76) /* load __sk_buff-&amp;gt;data */         r3 = *(u32 *)(r1 + 80) /* load __sk_buff-&amp;gt;data_end */         r0 = r2         r0 += 8         if r3 &amp;gt; r0 goto +1         ... Note that __sk_buff-&amp;gt;data load has 32-bit sign extension. After verification and convert_ctx_accesses(), the final asm code looks like:         r2 = *(u64 *)(r1 +208)         r2 = (s32)r2         r3 = *(u64 *)(r1 +80)         r0 = r2         r0 += 8         if r3 &amp;gt; r0 goto pc+1         ... Note that &amp;#39;r2 = (s32)r2&amp;#39; may make the kernel __sk_buff-&amp;gt;data address invalid which may cause runtime failure. Currently, in C code, typically we have         void *data = (void *)(long)skb-&amp;gt;data;         void *data_end = (void *)(long)skb-&amp;gt;data_end;         ... and it will generate         r2 = *(u64 *)(r1 +208)         r3 = *(u64 *)(r1 +80)         r0 = r2         r0 += 8         if r3 &amp;gt; r0 goto pc+1 If we allow sign-extension,         void *data = (void *)(long)(int)skb-&amp;gt;data;         void *data_end = (void *)(long)skb-&amp;gt;data_end;         ... the generated code looks like         r2 = *(u64 *)(r1 +208)         r2 &amp;lt;&amp;lt;= 32…&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 91 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fail verification for sign-extension of packet data/data_end/data_meta syzbot reported a kernel crash due to   commit 1f1e864b6555 (&amp;#34;bpf: Handle sign-extenstin ctx member accesses&amp;#34;). The reason is due to sign-extension of 32-bit load for packet data/data_end/data_meta uapi field. The original code looks like:         r2 = *(s32 *)(r1 + 76) /* load __sk_buff-&amp;gt;data */         r3 = *(u32 *)(r1 + 80) /* load __sk_buff-&amp;gt;data_end */         r0 = r2         r0 += 8         if r3 &amp;gt; r0 goto +1         ... Note that __sk_buff-&amp;gt;data load has 32-bit sign extension. After verification and convert_ctx_accesses(), the final asm code looks like:         r2 = *(u64 *)(r1 +208)         r2 = (s32)r2         r3 = *(u64 *)(r1 +80)         r0 = r2         r0 += 8         if r3 &amp;gt; r0 goto pc+1         ... Note that &amp;#39;r2 = (s32)r2&amp;#39; may make the kernel __sk_buff-&amp;gt;data address invalid which may cause runtime failure. Currently, in C code, typically we have         void *data = (void *)(long)skb-&amp;gt;data;         void *data_end = (void *)(long)skb-&amp;gt;data_end;         ... and it will generate         r2 = *(u64 *)(r1 +208)         r3 = *(u64 *)(r1 +80)         r0 = r2         r0 += 8         if r3 &amp;gt; r0 goto pc+1 If we allow sign-extension,         void *data = (void *)(long)(int)skb-&amp;gt;data;         void *data_end = (void *)(long)skb-&amp;gt;data_end;         ... the generated code looks like         r2 = *(u64 *)(r1 +208)         r2 &amp;lt;&amp;lt;= 32…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-47702</guid>
    </item>
  </channel>
</rss>
