<?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:57:19 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:8617 — Moderate: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2024:8617</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.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* hw: cpu: intel: Native Branch History Injection (BHI) (CVE-2024-2201)
  * kernel: tcp: add sanity checks to rx zerocopy (CVE-2024-26640)
  * kernel: mptcp: fix data re-injection from stale subflow (CVE-2024-26826)
  * kernel: af_unix: Fix garbage collector racing against connect() (CVE-2024-26923)
  * kernel: mac802154: fix llsec key resources release in mac802154_llsec_key_del (CVE-2024-26961)
  * kernel: scsi: core: Fix unremoved procfs host directory regression (CVE-2024-26935)
  * kernel: tty: Fix out-of-bound vmalloc access in imageblit (CVE-2021-47383)
  * kernel: net/sched: taprio: extend minimum interval restriction to entire cycle too (CVE-2024-36244)
  * kernel: xfs: fix log recovery buffer allocation for the legacy h_size fixup (CVE-2024-39472)
  * kernel: netfilter: nft_inner: validate mandatory meta and payload (CVE-2024-39504)
  * kernel: USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages (CVE-2024-40904)
  * kernel: mptcp: ensure snd_una is properly initialized on connect (CVE-2024-40931)
  * kernel: ipv6: prevent possible NULL dereference in rt6_probe() (CVE-2024-40960)
  * kernel: ext4: do not create EA inode under buffer lock (CVE-2024-40972)
  * kernel: wifi: mt76: mt7921s: fix potential hung tasks during chip recovery (CVE-2024-40977)
  * kernel: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() (CVE-202…&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.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* hw: cpu: intel: Native Branch History Injection (BHI) (CVE-2024-2201)
  * kernel: tcp: add sanity checks to rx zerocopy (CVE-2024-26640)
  * kernel: mptcp: fix data re-injection from stale subflow (CVE-2024-26826)
  * kernel: af_unix: Fix garbage collector racing against connect() (CVE-2024-26923)
  * kernel: mac802154: fix llsec key resources release in mac802154_llsec_key_del (CVE-2024-26961)
  * kernel: scsi: core: Fix unremoved procfs host directory regression (CVE-2024-26935)
  * kernel: tty: Fix out-of-bound vmalloc access in imageblit (CVE-2021-47383)
  * kernel: net/sched: taprio: extend minimum interval restriction to entire cycle too (CVE-2024-36244)
  * kernel: xfs: fix log recovery buffer allocation for the legacy h_size fixup (CVE-2024-39472)
  * kernel: netfilter: nft_inner: validate mandatory meta and payload (CVE-2024-39504)
  * kernel: USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages (CVE-2024-40904)
  * kernel: mptcp: ensure snd_una is properly initialized on connect (CVE-2024-40931)
  * kernel: ipv6: prevent possible NULL dereference in rt6_probe() (CVE-2024-40960)
  * kernel: ext4: do not create EA inode under buffer lock (CVE-2024-40972)
  * kernel: wifi: mt76: mt7921s: fix potential hung tasks during chip recovery (CVE-2024-40977)
  * kernel: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() (CVE-202…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2024:8617</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-36244</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-36244</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-36244</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0778 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0778</link>
      <description>certfr-2024-avi-0778</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0778</guid>
    </item>
    <item>
      <title>OESA-2024-2292 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2292</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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
octeontx2-af: Use separate handlers for interrupts&#13;
&#13;
For PF to AF interrupt vector and VF to AF vector same
interrupt handler is registered which is causing race condition.
When two interrupts are raised to two CPUs at same time
then two cores serve same event corrupting the data.(CVE-2024-27030)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
media: go7007: fix a memleak in go7007_load_encoder&#13;
&#13;
In go7007_load_encoder, bounce(i.e. go-&amp;amp;gt;boot_fw), is allocated without
a deallocation thereafter. After the following call chain:&#13;
&#13;
saa7134_go7007_init
  |-&amp;amp;gt; go7007_boot_encoder
        |-&amp;amp;gt; go7007_load_encoder
  |-&amp;amp;gt; kfree(go)&#13;
&#13;
go is freed and thus bounce is leaked.(CVE-2024-27074)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
netfilter: nf_tables: use timestamp to check for set element timeout&#13;
&#13;
Add a timestamp field at the beginning of the transaction, store it
in the nftables per-netns area.&#13;
&#13;
Update set backend .insert, .deactivate and sync gc path to use the
timestamp, this avoids that an element expires while control plane
transaction is still unfinished.&#13;
&#13;
.lookup and .update, which are used from packet path, still use the
current time to check if the element has expired. And .get path and dump
also since this runs lockless under rcu read size lock. Then, ther…&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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
octeontx2-af: Use separate handlers for interrupts&#13;
&#13;
For PF to AF interrupt vector and VF to AF vector same
interrupt handler is registered which is causing race condition.
When two interrupts are raised to two CPUs at same time
then two cores serve same event corrupting the data.(CVE-2024-27030)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
media: go7007: fix a memleak in go7007_load_encoder&#13;
&#13;
In go7007_load_encoder, bounce(i.e. go-&amp;amp;gt;boot_fw), is allocated without
a deallocation thereafter. After the following call chain:&#13;
&#13;
saa7134_go7007_init
  |-&amp;amp;gt; go7007_boot_encoder
        |-&amp;amp;gt; go7007_load_encoder
  |-&amp;amp;gt; kfree(go)&#13;
&#13;
go is freed and thus bounce is leaked.(CVE-2024-27074)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
netfilter: nf_tables: use timestamp to check for set element timeout&#13;
&#13;
Add a timestamp field at the beginning of the transaction, store it
in the nftables per-netns area.&#13;
&#13;
Update set backend .insert, .deactivate and sync gc path to use the
timestamp, this avoids that an element expires while control plane
transaction is still unfinished.&#13;
&#13;
.lookup and .update, which are used from packet path, still use the
current time to check if the element has expired. And .get path and dump
also since this runs lockless under rcu read size lock. Then, ther…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2292</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-36244</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-36244</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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/sched: taprio: extend minimum interval restriction to entire cycle too It is possible for syzbot to side-step the restriction imposed by the blamed commit in the Fixes: tag, because the taprio UAPI permits a cycle-time different from (and potentially shorter than) the sum of entry intervals. We need one more restriction, which is that the cycle time itself must be larger than N * ETH_ZLEN bit times, where N is the number of schedule entries. This restriction needs to apply regardless of whether the cycle time came from the user or was the implicit, auto-calculated value, so we move the existing &amp;#34;cycle == 0&amp;#34; check outside the &amp;#34;if &amp;#34;(!new-&amp;gt;cycle_time)&amp;#34; branch. This way covers both conditions and scenarios. Add a selftest which illustrates the issue triggered by syzbot.&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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/sched: taprio: extend minimum interval restriction to entire cycle too It is possible for syzbot to side-step the restriction imposed by the blamed commit in the Fixes: tag, because the taprio UAPI permits a cycle-time different from (and potentially shorter than) the sum of entry intervals. We need one more restriction, which is that the cycle time itself must be larger than N * ETH_ZLEN bit times, where N is the number of schedule entries. This restriction needs to apply regardless of whether the cycle time came from the user or was the implicit, auto-calculated value, so we move the existing &amp;#34;cycle == 0&amp;#34; check outside the &amp;#34;if &amp;#34;(!new-&amp;gt;cycle_time)&amp;#34; branch. This way covers both conditions and scenarios. Add a selftest which illustrates the issue triggered by syzbot.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-36244</guid>
    </item>
  </channel>
</rss>
