<?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>Fri, 20 Nov 2026 23:32:37 +0000</lastBuildDate>
    <item>
      <title>certfr-2024-avi-0496 — 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-0496</link>
      <description>certfr-2024-avi-0496</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0496</guid>
    </item>
    <item>
      <title>OESA-2024-1736 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1736</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;
PCI: aardvark: Fix kernel panic during PIO transfer&#13;
&#13;
Trying to start a new PIO transfer by writing value 0 in PIO_START register
when previous transfer has not yet completed (which is indicated by value 1
in PIO_START) causes an External Abort on CPU, which results in kernel
panic:&#13;
&#13;
    SError Interrupt on CPU0, code 0xbf000002 -- SError
    Kernel panic - not syncing: Asynchronous SError Interrupt&#13;
&#13;
To prevent kernel panic, it is required to reject a new PIO transfer when
previous one has not finished yet.&#13;
&#13;
If previous PIO transfer is not finished yet, the kernel may issue a new
PIO request only if the previous PIO transfer timed out.&#13;
&#13;
In the past the root cause of this issue was incorrectly identified (as it
often happens during link retraining or after link down event) and special
hack was implemented in Trusted Firmware to catch all SError events in EL3,
to ignore errors with code 0xbf000002 and not forwarding any other errors
to kernel and instead throw panic from EL3 Trusted Firmware handler.&#13;
&#13;
Links to discussion and patches about this issue:
https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=3c7dcdac5c50
https://lore.kernel.org/linux-pci/20190316161243.29517-1-repk@triplefau.lt/
https://lore.kernel.org/linux-pci/971be151d24312cc533989a64bd454b4@www.loen.fr/
https://review.trustedfirmware.org/c…&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;
PCI: aardvark: Fix kernel panic during PIO transfer&#13;
&#13;
Trying to start a new PIO transfer by writing value 0 in PIO_START register
when previous transfer has not yet completed (which is indicated by value 1
in PIO_START) causes an External Abort on CPU, which results in kernel
panic:&#13;
&#13;
    SError Interrupt on CPU0, code 0xbf000002 -- SError
    Kernel panic - not syncing: Asynchronous SError Interrupt&#13;
&#13;
To prevent kernel panic, it is required to reject a new PIO transfer when
previous one has not finished yet.&#13;
&#13;
If previous PIO transfer is not finished yet, the kernel may issue a new
PIO request only if the previous PIO transfer timed out.&#13;
&#13;
In the past the root cause of this issue was incorrectly identified (as it
often happens during link retraining or after link down event) and special
hack was implemented in Trusted Firmware to catch all SError events in EL3,
to ignore errors with code 0xbf000002 and not forwarding any other errors
to kernel and instead throw panic from EL3 Trusted Firmware handler.&#13;
&#13;
Links to discussion and patches about this issue:
https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=3c7dcdac5c50
https://lore.kernel.org/linux-pci/20190316161243.29517-1-repk@triplefau.lt/
https://lore.kernel.org/linux-pci/971be151d24312cc533989a64bd454b4@www.loen.fr/
https://review.trustedfirmware.org/c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1736</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47483</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2021-47483</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, 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 109 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: regmap: Fix possible double-free in regcache_rbtree_exit() In regcache_rbtree_insert_to_block(), when &amp;#39;present&amp;#39; realloc failed, the &amp;#39;blk&amp;#39; which is supposed to assign to &amp;#39;rbnode-&amp;gt;block&amp;#39; will be freed, so &amp;#39;rbnode-&amp;gt;block&amp;#39; points a freed memory, in the error handling path of regcache_rbtree_init(), &amp;#39;rbnode-&amp;gt;block&amp;#39; will be freed again in regcache_rbtree_exit(), KASAN will report double-free as follows: BUG: KASAN: double-free or invalid-free in kfree+0xce/0x390 Call Trace:  slab_free_freelist_hook+0x10d/0x240  kfree+0xce/0x390  regcache_rbtree_exit+0x15d/0x1a0  regcache_rbtree_init+0x224/0x2c0  regcache_init+0x88d/0x1310  __regmap_init+0x3151/0x4a80  __devm_regmap_init+0x7d/0x100  madera_spi_probe+0x10f/0x333 [madera_spi]  spi_probe+0x183/0x210  really_probe+0x285/0xc30 To fix this, moving up the assignment of rbnode-&amp;gt;block to immediately after the reallocation has succeeded so that the data structure stays valid even if the second reallocation fails.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, 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 109 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: regmap: Fix possible double-free in regcache_rbtree_exit() In regcache_rbtree_insert_to_block(), when &amp;#39;present&amp;#39; realloc failed, the &amp;#39;blk&amp;#39; which is supposed to assign to &amp;#39;rbnode-&amp;gt;block&amp;#39; will be freed, so &amp;#39;rbnode-&amp;gt;block&amp;#39; points a freed memory, in the error handling path of regcache_rbtree_init(), &amp;#39;rbnode-&amp;gt;block&amp;#39; will be freed again in regcache_rbtree_exit(), KASAN will report double-free as follows: BUG: KASAN: double-free or invalid-free in kfree+0xce/0x390 Call Trace:  slab_free_freelist_hook+0x10d/0x240  kfree+0xce/0x390  regcache_rbtree_exit+0x15d/0x1a0  regcache_rbtree_init+0x224/0x2c0  regcache_init+0x88d/0x1310  __regmap_init+0x3151/0x4a80  __devm_regmap_init+0x7d/0x100  madera_spi_probe+0x10f/0x333 [madera_spi]  spi_probe+0x183/0x210  really_probe+0x285/0xc30 To fix this, moving up the assignment of rbnode-&amp;gt;block to immediately after the reallocation has succeeded so that the data structure stays valid even if the second reallocation fails.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2021-47483</guid>
    </item>
  </channel>
</rss>
