<?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://cve.radiocsirt.org</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, 02 Oct 2026 13:02:32 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-07320</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-07320</link>
      <description>bdu:2025-07320</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-07320</guid>
    </item>
    <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://cve.radiocsirt.org/vuln/certfr-2024-avi-0496</link>
      <description>certfr-2024-avi-0496</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496</guid>
    </item>
    <item>
      <title>EUVD-2026-309654</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309654</link>
      <description>EUVD-2026-309654</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309654</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47301</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47301</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;igb: Fix use-after-free error during reset&lt;/p&gt;
&lt;p&gt;Cleans the next descriptor to watch (next_to_watch) when cleaning the
TX ring.&lt;/p&gt;
&lt;p&gt;Failure to do so can cause invalid memory accesses. If igb_poll() runs
while the controller is reset this can lead to the driver try to free
a skb that was already freed.&lt;/p&gt;
&lt;p&gt;(The crash is harder to reproduce with the igb driver, but the same
potential problem exists as the code is identical to igc)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;igb: Fix use-after-free error during reset&lt;/p&gt;
&lt;p&gt;Cleans the next descriptor to watch (next_to_watch) when cleaning the
TX ring.&lt;/p&gt;
&lt;p&gt;Failure to do so can cause invalid memory accesses. If igb_poll() runs
while the controller is reset this can lead to the driver try to free
a skb that was already freed.&lt;/p&gt;
&lt;p&gt;(The crash is harder to reproduce with the igb driver, but the same
potential problem exists as the code is identical to igc)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47301</guid>
    </item>
    <item>
      <title>GHSA-9h2q-cwg7-7wx8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9h2q-cwg7-7wx8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;igb: Fix use-after-free error during reset&lt;/p&gt;
&lt;p&gt;Cleans the next descriptor to watch (next_to_watch) when cleaning the
TX ring.&lt;/p&gt;
&lt;p&gt;Failure to do so can cause invalid memory accesses. If igb_poll() runs
while the controller is reset this can lead to the driver try to free
a skb that was already freed.&lt;/p&gt;
&lt;p&gt;(The crash is harder to reproduce with the igb driver, but the same
potential problem exists as the code is identical to igc)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;igb: Fix use-after-free error during reset&lt;/p&gt;
&lt;p&gt;Cleans the next descriptor to watch (next_to_watch) when cleaning the
TX ring.&lt;/p&gt;
&lt;p&gt;Failure to do so can cause invalid memory accesses. If igb_poll() runs
while the controller is reset this can lead to the driver try to free
a skb that was already freed.&lt;/p&gt;
&lt;p&gt;(The crash is harder to reproduce with the igb driver, but the same
potential problem exists as the code is identical to igc)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9h2q-cwg7-7wx8</guid>
    </item>
    <item>
      <title>OESA-2024-1736 — kernel security update</title>
      <link>https://cve.radiocsirt.org/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://cve.radiocsirt.org/vuln/oesa-2024-1736</guid>
    </item>
    <item>
      <title>RHSA-2022:1988 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2022:1988</link>
      <description>&lt;p&gt;kernel: avoid cyclic entity chains due to malformed USB descriptors kernel: speculation on incompletely validated data on IBM Power9 kernel: integer overflow in k_ascii() in drivers/tty/vt/keyboard.c kernel: use-after-free in nouveau kernel module kernel: out-of-bounds read in bpf_skb_change_head() of filter.c due to a use-after-free kernel: joydev: zero size passed to joydev_handle_JSIOCSBTNMAP() kernel: reading /proc/sysvipc/shm does not scale with large shared memory segment counts kernel: out-of-bound Read in qrtr_endpoint_post in net/qrtr/qrtr.c kernel: crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd() kernel: possible use-after-free in bluetooth module kernel: unaccounted ipc objects in Linux kernel lead to breaking memcg limits and DoS attacks kernel: DoS in ccp_run_aes_gcm_cmd() function kernel: sctp: Invalid chunks may be used to remotely remove existing associations kernel: lack of port sanity checking in natd and netfilter leads to exploit of OpenVPN clients kernel: stack information leak in infiniband RDMA kernel: possible leak or coruption of data residing on hugetlbfs kernel: security regression for CVE-2018-13405 kernel: fget: check that the fd still exists after getting a ref to it kernel: KVM: SVM: out-of-bounds read/write in sev_es_string_io kernel: Buffer overwrite in decode_nfs_fh function kernel: cgroup: Use open-time creds and namespace for migration perm checks kernel: Race condition in races in sk_peer_pid and sk_peer_cred accesses kernel: Lin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: avoid cyclic entity chains due to malformed USB descriptors kernel: speculation on incompletely validated data on IBM Power9 kernel: integer overflow in k_ascii() in drivers/tty/vt/keyboard.c kernel: use-after-free in nouveau kernel module kernel: out-of-bounds read in bpf_skb_change_head() of filter.c due to a use-after-free kernel: joydev: zero size passed to joydev_handle_JSIOCSBTNMAP() kernel: reading /proc/sysvipc/shm does not scale with large shared memory segment counts kernel: out-of-bound Read in qrtr_endpoint_post in net/qrtr/qrtr.c kernel: crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd() kernel: possible use-after-free in bluetooth module kernel: unaccounted ipc objects in Linux kernel lead to breaking memcg limits and DoS attacks kernel: DoS in ccp_run_aes_gcm_cmd() function kernel: sctp: Invalid chunks may be used to remotely remove existing associations kernel: lack of port sanity checking in natd and netfilter leads to exploit of OpenVPN clients kernel: stack information leak in infiniband RDMA kernel: possible leak or coruption of data residing on hugetlbfs kernel: security regression for CVE-2018-13405 kernel: fget: check that the fd still exists after getting a ref to it kernel: KVM: SVM: out-of-bounds read/write in sev_es_string_io kernel: Buffer overwrite in decode_nfs_fh function kernel: cgroup: Use open-time creds and namespace for migration perm checks kernel: Race condition in races in sk_peer_pid and sk_peer_cred accesses kernel: Lin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2022:1988</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1979-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1979-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:1979-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47301</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47301</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 101 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: igb: Fix use-after-free error during reset Cleans the next descriptor to watch (next_to_watch) when cleaning the TX ring. Failure to do so can cause invalid memory accesses. If igb_poll() runs while the controller is reset this can lead to the driver try to free a skb that was already freed. (The crash is harder to reproduce with the igb driver, but the same potential problem exists as the code is identical to igc)&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: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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 101 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: igb: Fix use-after-free error during reset Cleans the next descriptor to watch (next_to_watch) when cleaning the TX ring. Failure to do so can cause invalid memory accesses. If igb_poll() runs while the controller is reset this can lead to the driver try to free a skb that was already freed. (The crash is harder to reproduce with the igb driver, but the same potential problem exists as the code is identical to igc)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47301</guid>
    </item>
  </channel>
</rss>
