<?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 00:45:36 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-35931</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-35931</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-35931</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0526 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent une élé…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</link>
      <description>certfr-2024-avi-0526</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</guid>
    </item>
    <item>
      <title>OESA-2024-1941 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1941</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: 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;
clk: sunxi-ng: Unregister clocks/resets when unbinding&#13;
&#13;
Currently, unbinding a CCU driver unmaps the device&amp;amp;apos;s MMIO region, while
leaving its clocks/resets and their providers registered. This can cause
a page fault later when some clock operation tries to perform MMIO. Fix
this by separating the CCU initialization from the memory allocation,
and then using a devres callback to unregister the clocks and resets.&#13;
&#13;
This also fixes a memory leak of the `struct ccu_reset`, and uses the
correct owner (the specific platform driver) for the clocks and resets.&#13;
&#13;
Early OF clock providers are never unregistered, and limited error
handling is possible, so they are mostly unchanged. The error reporting
is made more consistent by moving the message inside of_sunxi_ccu_probe.(CVE-2021-47205)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR&#13;
&#13;
In some case, the GDDV returns a package with a buffer which has
zero length. It causes that kmemdup() returns ZERO_SIZE_PTR (0x10).&#13;
&#13;
Then the data_vault_read() got NULL point dereference problem when
accessing the 0x10 value in data_vault.&#13;
&#13;
[   71.024560] BUG: kernel NULL pointer dereference, address:
0000000000000010&#13;
&#13;
This patch uses ZERO_OR_NULL_PTR() for checking ZERO_SIZE_PTR or
NULL value…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: 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;
clk: sunxi-ng: Unregister clocks/resets when unbinding&#13;
&#13;
Currently, unbinding a CCU driver unmaps the device&amp;amp;apos;s MMIO region, while
leaving its clocks/resets and their providers registered. This can cause
a page fault later when some clock operation tries to perform MMIO. Fix
this by separating the CCU initialization from the memory allocation,
and then using a devres callback to unregister the clocks and resets.&#13;
&#13;
This also fixes a memory leak of the `struct ccu_reset`, and uses the
correct owner (the specific platform driver) for the clocks and resets.&#13;
&#13;
Early OF clock providers are never unregistered, and limited error
handling is possible, so they are mostly unchanged. The error reporting
is made more consistent by moving the message inside of_sunxi_ccu_probe.(CVE-2021-47205)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR&#13;
&#13;
In some case, the GDDV returns a package with a buffer which has
zero length. It causes that kmemdup() returns ZERO_SIZE_PTR (0x10).&#13;
&#13;
Then the data_vault_read() got NULL point dereference problem when
accessing the 0x10 value in data_vault.&#13;
&#13;
[   71.024560] BUG: kernel NULL pointer dereference, address:
0000000000000010&#13;
&#13;
This patch uses ZERO_OR_NULL_PTR() for checking ZERO_SIZE_PTR or
NULL value…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1941</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-35931</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35931</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 179 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Skip do PCI error slot reset during RAS recovery Why:     The PCI error slot reset maybe triggered after inject ue to UMC multi times, this     caused system hang.     [  557.371857] amdgpu 0000:af:00.0: amdgpu: GPU reset succeeded, trying to resume     [  557.373718] [drm] PCIE GART of 512M enabled.     [  557.373722] [drm] PTB located at 0x0000031FED700000     [  557.373788] [drm] VRAM is lost due to GPU reset!     [  557.373789] [drm] PSP is resuming...     [  557.547012] mlx5_core 0000:55:00.0: mlx5_pci_err_detected Device state = 1 pci_status: 0. Exit, result = 3, need reset     [  557.547067] [drm] PCI error: detected callback, state(1)!!     [  557.547069] [drm] No support for XGMI hive yet...     [  557.548125] mlx5_core 0000:55:00.0: mlx5_pci_slot_reset Device state = 1 pci_status: 0. Enter     [  557.607763] mlx5_core 0000:55:00.0: wait vital counter value 0x16b5b after 1 iterations     [  557.607777] mlx5_core 0000:55:00.0: mlx5_pci_slot_reset Device state = 1 pci_status: 1. Exit, err = 0, result = 5, recovered     [  557.610492] [drm] PCI error: slot reset callback!!     ...     [  560.689382] amdgpu 0000:3f:00.0: amdgpu: GPU reset(2) succeeded!     [  560.689546] amdgpu 0000:5a:00.0: amdgpu: GPU reset(2) succeeded!     [  560.689562] general protection fault, probably for non-canonical address 0x5f080b54534f611f: 0000 [#1] SMP NOPTI     [  560.701008] CPU: 16 PID: 2361 Comm: kworker/…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 179 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Skip do PCI error slot reset during RAS recovery Why:     The PCI error slot reset maybe triggered after inject ue to UMC multi times, this     caused system hang.     [  557.371857] amdgpu 0000:af:00.0: amdgpu: GPU reset succeeded, trying to resume     [  557.373718] [drm] PCIE GART of 512M enabled.     [  557.373722] [drm] PTB located at 0x0000031FED700000     [  557.373788] [drm] VRAM is lost due to GPU reset!     [  557.373789] [drm] PSP is resuming...     [  557.547012] mlx5_core 0000:55:00.0: mlx5_pci_err_detected Device state = 1 pci_status: 0. Exit, result = 3, need reset     [  557.547067] [drm] PCI error: detected callback, state(1)!!     [  557.547069] [drm] No support for XGMI hive yet...     [  557.548125] mlx5_core 0000:55:00.0: mlx5_pci_slot_reset Device state = 1 pci_status: 0. Enter     [  557.607763] mlx5_core 0000:55:00.0: wait vital counter value 0x16b5b after 1 iterations     [  557.607777] mlx5_core 0000:55:00.0: mlx5_pci_slot_reset Device state = 1 pci_status: 1. Exit, err = 0, result = 5, recovered     [  557.610492] [drm] PCI error: slot reset callback!!     ...     [  560.689382] amdgpu 0000:3f:00.0: amdgpu: GPU reset(2) succeeded!     [  560.689546] amdgpu 0000:5a:00.0: amdgpu: GPU reset(2) succeeded!     [  560.689562] general protection fault, probably for non-canonical address 0x5f080b54534f611f: 0000 [#1] SMP NOPTI     [  560.701008] CPU: 16 PID: 2361 Comm: kworker/…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35931</guid>
    </item>
  </channel>
</rss>
