<?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>Thu, 19 Nov 2026 22:08:58 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:5363 — Important: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2024:5363</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 52 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.  
Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: phy: (CVE-2024-26600)
  * kernel: netfilter: multiple flaws (CVE-2024-26808, CVE-2024-27065, CVE-2024-35899, CVE-2024-36005)
  * kernel: cifs: (CVE-2024-26828)
  * kernel: wifi: multiple flaws (CVE-2024-26897, CVE-2024-27052, CVE-2024-27049, CVE-2023-52651, CVE-2024-35789, CVE-2024-27434, CVE-2024-35845, CVE-2024-35937, CVE-2024-36941, CVE-2024-36922, CVE-2024-36921, CVE-2024-38575)
  * kernel: nfs: (CVE-2024-26868)
  * kernel: igc: (CVE-2024-26853)
  * kernel: dmaengine/idxd: (CVE-2024-21823)
  * kernel: ipv6: multiple flaws (CVE-2024-27417, CVE-2024-35969, CVE-2024-36903, CVE-2024-40961)
  * kernel: vt: (CVE-2024-35823)
  * kernel: efi: (CVE-2024-35800)
  * kernel: mlxsw: (CVE-2024-35852)
  * kernel: eeprom: (CVE-2024-35848)
  * kernel: ice: (CVE-2024-35911)
  * kernel: platform/x86: (CVE-2023-52864)
  * kernel: i40e: (CVE-2024-36020)
  * kernel: rtnetlink: (CVE-2024-36017)
  * kernel: net: multiple flaws (CVE-2024-36929, CVE-2024-36971, CVE-2021-47606, CVE-2024-38558, CVE-2024-40928, CVE-2024-40954)
  * kernel: ipvlan: (CVE-2024-33621)
  * kernel: tcp: (CVE-2024-37356)
  * kernel: virtio: (CVE-2024-37353)
  * kernel: tls: (CVE-2024-36489)
  * kernel: cxl/region: (CVE-2024-38391)
  * kernel: bonding: (CVE-2024-39487)
  * kernel: netns: (CVE-2024-40958)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, an…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 52 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.  
Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: phy: (CVE-2024-26600)
  * kernel: netfilter: multiple flaws (CVE-2024-26808, CVE-2024-27065, CVE-2024-35899, CVE-2024-36005)
  * kernel: cifs: (CVE-2024-26828)
  * kernel: wifi: multiple flaws (CVE-2024-26897, CVE-2024-27052, CVE-2024-27049, CVE-2023-52651, CVE-2024-35789, CVE-2024-27434, CVE-2024-35845, CVE-2024-35937, CVE-2024-36941, CVE-2024-36922, CVE-2024-36921, CVE-2024-38575)
  * kernel: nfs: (CVE-2024-26868)
  * kernel: igc: (CVE-2024-26853)
  * kernel: dmaengine/idxd: (CVE-2024-21823)
  * kernel: ipv6: multiple flaws (CVE-2024-27417, CVE-2024-35969, CVE-2024-36903, CVE-2024-40961)
  * kernel: vt: (CVE-2024-35823)
  * kernel: efi: (CVE-2024-35800)
  * kernel: mlxsw: (CVE-2024-35852)
  * kernel: eeprom: (CVE-2024-35848)
  * kernel: ice: (CVE-2024-35911)
  * kernel: platform/x86: (CVE-2023-52864)
  * kernel: i40e: (CVE-2024-36020)
  * kernel: rtnetlink: (CVE-2024-36017)
  * kernel: net: multiple flaws (CVE-2024-36929, CVE-2024-36971, CVE-2021-47606, CVE-2024-38558, CVE-2024-40928, CVE-2024-40954)
  * kernel: ipvlan: (CVE-2024-33621)
  * kernel: tcp: (CVE-2024-37356)
  * kernel: virtio: (CVE-2024-37353)
  * kernel: tls: (CVE-2024-36489)
  * kernel: cxl/region: (CVE-2024-38391)
  * kernel: bonding: (CVE-2024-39487)
  * kernel: netns: (CVE-2024-40958)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, an…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2024:5363</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-35848</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-35848</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-35848</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0472 — 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-0472</link>
      <description>certfr-2024-avi-0472</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0472</guid>
    </item>
    <item>
      <title>OESA-2024-1680 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1680</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;
drm/amdgpu: handle the case of pci_channel_io_frozen only in amdgpu_pci_resume&#13;
&#13;
In current code, when a PCI error state pci_channel_io_normal is detectd,
it will report PCI_ERS_RESULT_CAN_RECOVER status to PCI driver, and PCI
driver will continue the execution of PCI resume callback report_resume by
pci_walk_bridge, and the callback will go into amdgpu_pci_resume
finally, where write lock is releasd unconditionally without acquiring
such lock first. In this case, a deadlock will happen when other threads
start to acquire the read lock.&#13;
&#13;
To fix this, add a member in amdgpu_device strucutre to cache
pci_channel_state, and only continue the execution in amdgpu_pci_resume
when it&amp;amp;apos;s pci_channel_io_frozen.(CVE-2021-47421)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
ptp: Fix possible memory leak in ptp_clock_register()&#13;
&#13;
I got memory leak as follows when doing fault injection test:&#13;
&#13;
unreferenced object 0xffff88800906c618 (size 8):
  comm &amp;amp;quot;i2c-idt82p33931&amp;amp;quot;, pid 4421, jiffies 4294948083 (age 13.188s)
  hex dump (first 8 bytes):
    70 74 70 30 00 00 00 00                          ptp0....
  backtrace:
    [&amp;amp;lt;00000000312ed458&amp;amp;gt;] __kmalloc_track_caller+0x19f/0x3a0
    [&amp;amp;lt;0000000079f6e2ff&amp;amp;gt;] kvasprintf+0xb5/0x150
    [&amp;amp;lt;0000000026aae54f&amp;amp;gt;] kvasprintf_const+0x60/0x190
    [&amp;amp;lt;000…&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;
drm/amdgpu: handle the case of pci_channel_io_frozen only in amdgpu_pci_resume&#13;
&#13;
In current code, when a PCI error state pci_channel_io_normal is detectd,
it will report PCI_ERS_RESULT_CAN_RECOVER status to PCI driver, and PCI
driver will continue the execution of PCI resume callback report_resume by
pci_walk_bridge, and the callback will go into amdgpu_pci_resume
finally, where write lock is releasd unconditionally without acquiring
such lock first. In this case, a deadlock will happen when other threads
start to acquire the read lock.&#13;
&#13;
To fix this, add a member in amdgpu_device strucutre to cache
pci_channel_state, and only continue the execution in amdgpu_pci_resume
when it&amp;amp;apos;s pci_channel_io_frozen.(CVE-2021-47421)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
ptp: Fix possible memory leak in ptp_clock_register()&#13;
&#13;
I got memory leak as follows when doing fault injection test:&#13;
&#13;
unreferenced object 0xffff88800906c618 (size 8):
  comm &amp;amp;quot;i2c-idt82p33931&amp;amp;quot;, pid 4421, jiffies 4294948083 (age 13.188s)
  hex dump (first 8 bytes):
    70 74 70 30 00 00 00 00                          ptp0....
  backtrace:
    [&amp;amp;lt;00000000312ed458&amp;amp;gt;] __kmalloc_track_caller+0x19f/0x3a0
    [&amp;amp;lt;0000000079f6e2ff&amp;amp;gt;] kvasprintf+0xb5/0x150
    [&amp;amp;lt;0000000026aae54f&amp;amp;gt;] kvasprintf_const+0x60/0x190
    [&amp;amp;lt;000…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1680</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-35848</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35848</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: eeprom: at24: fix memory corruption race condition If the eeprom is not accessible, an nvmem device will be registered, the read will fail, and the device will be torn down. If another driver accesses the nvmem device after the teardown, it will reference invalid memory. Move the failure point before registering the nvmem device.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: eeprom: at24: fix memory corruption race condition If the eeprom is not accessible, an nvmem device will be registered, the read will fail, and the device will be torn down. If another driver accesses the nvmem device after the teardown, it will reference invalid memory. Move the failure point before registering the nvmem device.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35848</guid>
    </item>
  </channel>
</rss>
