<?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 04:09:47 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-31521</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-31521</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-2026-31521</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0519 — De multiples vulnérabilités ont été découvertes dans Microsoft Azure Linux. Elles permettent à un attaquant de provoque…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0519</link>
      <description>certfr-2026-avi-0519</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0519</guid>
    </item>
    <item>
      <title>OESA-2026-2311 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-2311</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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/vmwgfx: Return the correct value in vmw_translate_ptr functions&lt;/p&gt;
&lt;p&gt;Before the referenced fixes these functions used a lookup function that
returned a pointer. This was changed to another lookup function that
returned an error code with the pointer becoming an out parameter.&lt;/p&gt;
&lt;p&gt;The error path when the lookup failed was not changed to reflect this
change and the code continued to return the PTR_ERR of the now
uninitialized pointer. This could cause the vmw_translate_ptr functions
to return success when they actually failed causing further uninitialized
and OOB accesses.(CVE-2026-23317)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;NFSD: Defer sub-object cleanup in export put callbacks&lt;/p&gt;
&lt;p&gt;svc_export_put() calls path_put() and auth_domain_put() immediately
when the last reference drops, before the RCU grace period. RCU
readers in e_show() and c_show() access both ex_path (via
seq_path/d_path) and ex_client-&amp;amp;gt;name (via seq_escape) without
holding a reference. If cache_clean removes the entry and drops the
last reference concurrently, the sub-objects are freed while still
in use, producing a NULL pointer dereference in d_path.&lt;/p&gt;
&lt;p&gt;Commit 2530766492ec (&amp;amp;quot;nfsd: fix UAF when access ex_uuid or
ex_stats&amp;amp;quot;) moved kfree of ex_uuid and ex_stats into the
call_rcu callback, but left path_put() and auth_domain_put() runnin…&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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/vmwgfx: Return the correct value in vmw_translate_ptr functions&lt;/p&gt;
&lt;p&gt;Before the referenced fixes these functions used a lookup function that
returned a pointer. This was changed to another lookup function that
returned an error code with the pointer becoming an out parameter.&lt;/p&gt;
&lt;p&gt;The error path when the lookup failed was not changed to reflect this
change and the code continued to return the PTR_ERR of the now
uninitialized pointer. This could cause the vmw_translate_ptr functions
to return success when they actually failed causing further uninitialized
and OOB accesses.(CVE-2026-23317)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;NFSD: Defer sub-object cleanup in export put callbacks&lt;/p&gt;
&lt;p&gt;svc_export_put() calls path_put() and auth_domain_put() immediately
when the last reference drops, before the RCU grace period. RCU
readers in e_show() and c_show() access both ex_path (via
seq_path/d_path) and ex_client-&amp;amp;gt;name (via seq_escape) without
holding a reference. If cache_clean removes the entry and drops the
last reference concurrently, the sub-objects are freed while still
in use, producing a NULL pointer dereference in d_path.&lt;/p&gt;
&lt;p&gt;Commit 2530766492ec (&amp;amp;quot;nfsd: fix UAF when access ex_uuid or
ex_stats&amp;amp;quot;) moved kfree of ex_uuid and ex_stats into the
call_rcu callback, but left path_put() and auth_domain_put() runnin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-2311</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-31521</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-31521</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 234 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: module: Fix kernel panic when a symbol st_shndx is out of bounds The module loader doesn&amp;#39;t check for bounds of the ELF section index in simplify_symbols():        for (i = 1; i &amp;lt; symsec-&amp;gt;sh_size / sizeof(Elf_Sym); i++) { 		const char *name = info-&amp;gt;strtab + sym[i].st_name; 		switch (sym[i].st_shndx) { 		case SHN_COMMON: 		[...] 		default: 			/* Divert to percpu allocation if a percpu var. */ 			if (sym[i].st_shndx == info-&amp;gt;index.pcpu) 				secbase = (unsigned long)mod_percpu(mod); 			else   /** HERE --&amp;gt; **/		secbase = info-&amp;gt;sechdrs[sym[i].st_shndx].sh_addr; 			sym[i].st_value += secbase; 			break; 		} 	} A symbol with an out-of-bounds st_shndx value, for example 0xffff (known as SHN_XINDEX or SHN_HIRESERVE), may cause a kernel panic:   BUG: unable to handle page fault for address: ...   RIP: 0010:simplify_symbols+0x2b2/0x480   ...   Kernel panic - not syncing: Fatal exception This can happen when module ELF is legitimately using SHN_XINDEX or when it is corrupted. Add a bounds check in simplify_symbols() to validate that st_shndx is within the valid range before using it. This issue was discovered due to a bug in llvm-objcopy, see relevant discussion for details [1]. [1] https://lore.kernel.org/linux-modules/20251224005752.201911-1-ihor.solodrai@linux.dev/&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 234 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: module: Fix kernel panic when a symbol st_shndx is out of bounds The module loader doesn&amp;#39;t check for bounds of the ELF section index in simplify_symbols():        for (i = 1; i &amp;lt; symsec-&amp;gt;sh_size / sizeof(Elf_Sym); i++) { 		const char *name = info-&amp;gt;strtab + sym[i].st_name; 		switch (sym[i].st_shndx) { 		case SHN_COMMON: 		[...] 		default: 			/* Divert to percpu allocation if a percpu var. */ 			if (sym[i].st_shndx == info-&amp;gt;index.pcpu) 				secbase = (unsigned long)mod_percpu(mod); 			else   /** HERE --&amp;gt; **/		secbase = info-&amp;gt;sechdrs[sym[i].st_shndx].sh_addr; 			sym[i].st_value += secbase; 			break; 		} 	} A symbol with an out-of-bounds st_shndx value, for example 0xffff (known as SHN_XINDEX or SHN_HIRESERVE), may cause a kernel panic:   BUG: unable to handle page fault for address: ...   RIP: 0010:simplify_symbols+0x2b2/0x480   ...   Kernel panic - not syncing: Fatal exception This can happen when module ELF is legitimately using SHN_XINDEX or when it is corrupted. Add a bounds check in simplify_symbols() to validate that st_shndx is within the valid range before using it. This issue was discovered due to a bug in llvm-objcopy, see relevant discussion for details [1]. [1] https://lore.kernel.org/linux-modules/20251224005752.201911-1-ihor.solodrai@linux.dev/&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-31521</guid>
    </item>
  </channel>
</rss>
