<?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 08:39:29 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-46755</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-46755</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-46755</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0837 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0837</link>
      <description>certfr-2024-avi-0837</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0837</guid>
    </item>
    <item>
      <title>OESA-2024-2184 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2184</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;
x86/mm: Fix pti_clone_pgtable() alignment assumption&#13;
&#13;
Guenter reported dodgy crashes on an i386-nosmp build using GCC-11
that had the form of endless traps until entry stack exhaust and then
#DF from the stack guard.&#13;
&#13;
It turned out that pti_clone_pgtable() had alignment assumptions on
the start address, notably it hard assumes start is PMD aligned. This
is true on x86_64, but very much not true on i386.&#13;
&#13;
These assumptions can cause the end condition to malfunction, leading
to a &amp;amp;apos;short&amp;amp;apos; clone. Guess what happens when the user mapping has a
short copy of the entry text?&#13;
&#13;
Use the correct increment form for addr to avoid alignment
assumptions.(CVE-2024-44965)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
gtp: pull network headers in gtp_dev_xmit()&#13;
&#13;
syzbot/KMSAN reported use of uninit-value in get_dev_xmit() [1]&#13;
&#13;
We must make sure the IPv4 or Ipv6 header is pulled in skb-&amp;amp;gt;head
before accessing fields in them.&#13;
&#13;
Use pskb_inet_may_pull() to fix this issue.&#13;
&#13;
[1]
BUG: KMSAN: uninit-value in ipv6_pdp_find drivers/net/gtp.c:220 [inline]
 BUG: KMSAN: uninit-value in gtp_build_skb_ip6 drivers/net/gtp.c:1229 [inline]
 BUG: KMSAN: uninit-value in gtp_dev_xmit+0x1424/0x2540 drivers/net/gtp.c:1281
  ipv6_pdp_find drivers/net/gtp.c:220 [inline]
  gtp_build_skb_ip6 drivers/net/gtp.c:1229 [inlin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;
x86/mm: Fix pti_clone_pgtable() alignment assumption&#13;
&#13;
Guenter reported dodgy crashes on an i386-nosmp build using GCC-11
that had the form of endless traps until entry stack exhaust and then
#DF from the stack guard.&#13;
&#13;
It turned out that pti_clone_pgtable() had alignment assumptions on
the start address, notably it hard assumes start is PMD aligned. This
is true on x86_64, but very much not true on i386.&#13;
&#13;
These assumptions can cause the end condition to malfunction, leading
to a &amp;amp;apos;short&amp;amp;apos; clone. Guess what happens when the user mapping has a
short copy of the entry text?&#13;
&#13;
Use the correct increment form for addr to avoid alignment
assumptions.(CVE-2024-44965)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
gtp: pull network headers in gtp_dev_xmit()&#13;
&#13;
syzbot/KMSAN reported use of uninit-value in get_dev_xmit() [1]&#13;
&#13;
We must make sure the IPv4 or Ipv6 header is pulled in skb-&amp;amp;gt;head
before accessing fields in them.&#13;
&#13;
Use pskb_inet_may_pull() to fix this issue.&#13;
&#13;
[1]
BUG: KMSAN: uninit-value in ipv6_pdp_find drivers/net/gtp.c:220 [inline]
 BUG: KMSAN: uninit-value in gtp_build_skb_ip6 drivers/net/gtp.c:1229 [inline]
 BUG: KMSAN: uninit-value in gtp_dev_xmit+0x1424/0x2540 drivers/net/gtp.c:1281
  ipv6_pdp_find drivers/net/gtp.c:220 [inline]
  gtp_build_skb_ip6 drivers/net/gtp.c:1229 [inlin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2184</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-46755</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-46755</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: wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() mwifiex_get_priv_by_id() returns the priv pointer corresponding to the bss_num and bss_type, but without checking if the priv is actually currently in use. Unused priv pointers do not have a wiphy attached to them which can lead to NULL pointer dereferences further down the callstack.  Fix this by returning only used priv pointers which have priv-&amp;gt;bss_mode set to something else than NL80211_IFTYPE_UNSPECIFIED. Said NULL pointer dereference happened when an Accesspoint was started with wpa_supplicant -i mlan0 with this config: network={         ssid=&amp;#34;somessid&amp;#34;         mode=2         frequency=2412         key_mgmt=WPA-PSK WPA-PSK-SHA256         proto=RSN         group=CCMP         pairwise=CCMP         psk=&amp;#34;12345678&amp;#34; } When waiting for the AP to be established, interrupting wpa_supplicant with &amp;lt;ctrl-c&amp;gt; and starting it again this happens: | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000140 | Mem abort info: |   ESR = 0x0000000096000004 |   EC = 0x25: DABT (current EL), IL = 32 bits |   SET = 0, FnV = 0 |   EA = 0, S1PTW = 0 |   FSC = 0x04: level 0 translation fault | Data abort info: |   ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 |   CM = 0, WnR = 0, TnD = 0, TagAccess = 0 |   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 | user pgtable: 4k pages, 48-bit VAs, pgdp=0000000046d96000 | [0000000000000140] pgd=000…&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: wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() mwifiex_get_priv_by_id() returns the priv pointer corresponding to the bss_num and bss_type, but without checking if the priv is actually currently in use. Unused priv pointers do not have a wiphy attached to them which can lead to NULL pointer dereferences further down the callstack.  Fix this by returning only used priv pointers which have priv-&amp;gt;bss_mode set to something else than NL80211_IFTYPE_UNSPECIFIED. Said NULL pointer dereference happened when an Accesspoint was started with wpa_supplicant -i mlan0 with this config: network={         ssid=&amp;#34;somessid&amp;#34;         mode=2         frequency=2412         key_mgmt=WPA-PSK WPA-PSK-SHA256         proto=RSN         group=CCMP         pairwise=CCMP         psk=&amp;#34;12345678&amp;#34; } When waiting for the AP to be established, interrupting wpa_supplicant with &amp;lt;ctrl-c&amp;gt; and starting it again this happens: | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000140 | Mem abort info: |   ESR = 0x0000000096000004 |   EC = 0x25: DABT (current EL), IL = 32 bits |   SET = 0, FnV = 0 |   EA = 0, S1PTW = 0 |   FSC = 0x04: level 0 translation fault | Data abort info: |   ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 |   CM = 0, WnR = 0, TnD = 0, TagAccess = 0 |   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 | user pgtable: 4k pages, 48-bit VAs, pgdp=0000000046d96000 | [0000000000000140] pgd=000…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-46755</guid>
    </item>
  </channel>
</rss>
