<?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>Sun, 04 Oct 2026 09:09:52 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-01866</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-01866</link>
      <description>bdu:2024-01866</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-01866</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-26589</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-26589</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://cve.radiocsirt.org/vuln/bell-cve-2024-26589</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0226 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux d'Ubuntu&lt;/span&gt;. Certaines d'e…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0226</link>
      <description>certfr-2024-avi-0226</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0226</guid>
    </item>
    <item>
      <title>EUVD-2026-345454</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345454</link>
      <description>EUVD-2026-345454</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345454</guid>
    </item>
    <item>
      <title>fkie_cve-2024-26589</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-26589</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS&lt;/p&gt;
&lt;p&gt;For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off
for validation. However, variable offset ptr alu is not prohibited
for this ptr kind. So the variable offset is not checked.&lt;/p&gt;
&lt;p&gt;The following prog is accepted:&lt;/p&gt;
&lt;p&gt;func#0 @0
  0: R1=ctx() R10=fp0
  0: (bf) r6 = r1                       ; R1=ctx() R6_w=ctx()
  1: (79) r7 = *(u64 *)(r6 +144)        ; R6_w=ctx() R7_w=flow_keys()
  2: (b7) r8 = 1024                     ; R8_w=1024
  3: (37) r8 /= 1                       ; R8_w=scalar()
  4: (57) r8 &amp;amp;= 1024                    ; R8_w=scalar(smin=smin32=0,
  smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400))
  5: (0f) r7 += r8
  mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1
  mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &amp;amp;= 1024
  mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1
  mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024
  6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off
  =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024,
  var_off=(0x0; 0x400))
  6: (79) r0 = *(u64 *)(r7 +0)          ; R0_w=scalar()
  7: (95) exit&lt;/p&gt;
&lt;p&gt;This prog loads flow_keys to r7, and adds the variable offset r8
to r7, and finally causes out-of-bounds access:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffffc90014c80038
  [...]
  Call Trace:
   &amp;lt;TASK&amp;gt;
   bpf_dispatcher_nop_func includ…&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;bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS&lt;/p&gt;
&lt;p&gt;For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off
for validation. However, variable offset ptr alu is not prohibited
for this ptr kind. So the variable offset is not checked.&lt;/p&gt;
&lt;p&gt;The following prog is accepted:&lt;/p&gt;
&lt;p&gt;func#0 @0
  0: R1=ctx() R10=fp0
  0: (bf) r6 = r1                       ; R1=ctx() R6_w=ctx()
  1: (79) r7 = *(u64 *)(r6 +144)        ; R6_w=ctx() R7_w=flow_keys()
  2: (b7) r8 = 1024                     ; R8_w=1024
  3: (37) r8 /= 1                       ; R8_w=scalar()
  4: (57) r8 &amp;amp;= 1024                    ; R8_w=scalar(smin=smin32=0,
  smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400))
  5: (0f) r7 += r8
  mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1
  mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &amp;amp;= 1024
  mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1
  mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024
  6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off
  =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024,
  var_off=(0x0; 0x400))
  6: (79) r0 = *(u64 *)(r7 +0)          ; R0_w=scalar()
  7: (95) exit&lt;/p&gt;
&lt;p&gt;This prog loads flow_keys to r7, and adds the variable offset r8
to r7, and finally causes out-of-bounds access:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffffc90014c80038
  [...]
  Call Trace:
   &amp;lt;TASK&amp;gt;
   bpf_dispatcher_nop_func includ…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-26589</guid>
    </item>
    <item>
      <title>GHSA-rw7c-wqqw-8w6c</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rw7c-wqqw-8w6c</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS&lt;/p&gt;
&lt;p&gt;For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off
for validation. However, variable offset ptr alu is not prohibited
for this ptr kind. So the variable offset is not checked.&lt;/p&gt;
&lt;p&gt;The following prog is accepted:&lt;/p&gt;
&lt;p&gt;func#0 @0
  0: R1=ctx() R10=fp0
  0: (bf) r6 = r1                       ; R1=ctx() R6_w=ctx()
  1: (79) r7 = *(u64 *)(r6 +144)        ; R6_w=ctx() R7_w=flow_keys()
  2: (b7) r8 = 1024                     ; R8_w=1024
  3: (37) r8 /= 1                       ; R8_w=scalar()
  4: (57) r8 &amp;amp;= 1024                    ; R8_w=scalar(smin=smin32=0,
  smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400))
  5: (0f) r7 += r8
  mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1
  mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &amp;amp;= 1024
  mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1
  mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024
  6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off
  =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024,
  var_off=(0x0; 0x400))
  6: (79) r0 = *(u64 *)(r7 +0)          ; R0_w=scalar()
  7: (95) exit&lt;/p&gt;
&lt;p&gt;This prog loads flow_keys to r7, and adds the variable offset r8
to r7, and finally causes out-of-bounds access:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffffc90014c80038
  [...]
  Call Trace:
   &amp;lt;TASK&amp;gt;
   bpf_dispatcher_nop_func includ…&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;bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS&lt;/p&gt;
&lt;p&gt;For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off
for validation. However, variable offset ptr alu is not prohibited
for this ptr kind. So the variable offset is not checked.&lt;/p&gt;
&lt;p&gt;The following prog is accepted:&lt;/p&gt;
&lt;p&gt;func#0 @0
  0: R1=ctx() R10=fp0
  0: (bf) r6 = r1                       ; R1=ctx() R6_w=ctx()
  1: (79) r7 = *(u64 *)(r6 +144)        ; R6_w=ctx() R7_w=flow_keys()
  2: (b7) r8 = 1024                     ; R8_w=1024
  3: (37) r8 /= 1                       ; R8_w=scalar()
  4: (57) r8 &amp;amp;= 1024                    ; R8_w=scalar(smin=smin32=0,
  smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400))
  5: (0f) r7 += r8
  mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1
  mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &amp;amp;= 1024
  mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1
  mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024
  6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off
  =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024,
  var_off=(0x0; 0x400))
  6: (79) r0 = *(u64 *)(r7 +0)          ; R0_w=scalar()
  7: (95) exit&lt;/p&gt;
&lt;p&gt;This prog loads flow_keys to r7, and adds the variable offset r8
to r7, and finally causes out-of-bounds access:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffffc90014c80038
  [...]
  Call Trace:
   &amp;lt;TASK&amp;gt;
   bpf_dispatcher_nop_func includ…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rw7c-wqqw-8w6c</guid>
    </item>
    <item>
      <title>gsd-2024-26589</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-26589</link>
      <description>gsd-2024-26589</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-26589</guid>
    </item>
    <item>
      <title>OESA-2024-1394 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1394</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS: 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;
ALSA: hda: intel-sdw-acpi: harden detection of controller&#13;
&#13;
The existing code currently sets a pointer to an ACPI handle before
checking that it&amp;amp;apos;s actually a SoundWire controller. This can lead to
issues where the graph walk continues and eventually fails, but the
pointer was set already.&#13;
&#13;
This patch changes the logic so that the information provided to
the caller is set when a controller is found.(CVE-2021-46926)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
ASoC: q6afe-clocks: fix reprobing of the driver&#13;
&#13;
Q6afe-clocks driver can get reprobed. For example if the APR services
are restarted after the firmware crash. However currently Q6afe-clocks
driver will oops because hw.init will get cleared during first _probe
call. Rewrite the driver to fill the clock data at runtime rather than
using big static array of clocks.(CVE-2021-47037)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
apparmor: avoid crash when parsed profile name is empty&#13;
&#13;
When processing a packed profile in unpack_profile() described like&#13;
&#13;
 &amp;amp;quot;profile :ns::samba-dcerpcd /usr/lib*/samba/{,samba/}samba-dcerpcd {...}&amp;amp;quot;&#13;
&#13;
a string &amp;amp;quot;:samba-dcerpcd&amp;amp;quot; is unpacked as a fully-qualified name and then
passed to aa_splitn_fqname().&#13;
&#13;
aa_splitn_fqname() treats &amp;amp;quot;:samba-dcerpcd&amp;amp;quot; as only…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS: 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;
ALSA: hda: intel-sdw-acpi: harden detection of controller&#13;
&#13;
The existing code currently sets a pointer to an ACPI handle before
checking that it&amp;amp;apos;s actually a SoundWire controller. This can lead to
issues where the graph walk continues and eventually fails, but the
pointer was set already.&#13;
&#13;
This patch changes the logic so that the information provided to
the caller is set when a controller is found.(CVE-2021-46926)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
ASoC: q6afe-clocks: fix reprobing of the driver&#13;
&#13;
Q6afe-clocks driver can get reprobed. For example if the APR services
are restarted after the firmware crash. However currently Q6afe-clocks
driver will oops because hw.init will get cleared during first _probe
call. Rewrite the driver to fill the clock data at runtime rather than
using big static array of clocks.(CVE-2021-47037)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
apparmor: avoid crash when parsed profile name is empty&#13;
&#13;
When processing a packed profile in unpack_profile() described like&#13;
&#13;
 &amp;amp;quot;profile :ns::samba-dcerpcd /usr/lib*/samba/{,samba/}samba-dcerpcd {...}&amp;amp;quot;&#13;
&#13;
a string &amp;amp;quot;:samba-dcerpcd&amp;amp;quot; is unpacked as a fully-qualified name and then
passed to aa_splitn_fqname().&#13;
&#13;
aa_splitn_fqname() treats &amp;amp;quot;:samba-dcerpcd&amp;amp;quot; as only…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1394</guid>
    </item>
    <item>
      <title>RHSA-2024:9315 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:9315</link>
      <description>&lt;p&gt;kernel: use after free in i2c kernel: bluetooth: BR/EDR Bluetooth Impersonation Attacks (BIAS) kernel: hwmon: (lm90) Prevent integer overflow/underflow in hysteresis calculations kernel: asix: fix uninit-value in asix_mdio_read() kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: powerpc/64s: fix program check interrupt emergency stack path kernel: powerpc/64s: Fix unrecoverable MCE calling async handler from NMI kernel: lib/generic-radix-tree.c: Don&amp;#39;t overflow in peek() kernel: powerpc/smp: do not decrement idle task preempt count in CPU offline kernel: can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible() kernel: usbnet: sanity check for maxpacket kernel: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells kernel: aio: fix use-after-free due to missing POLLFREE handling kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: of: fdt: fix off-by-one error in unflatten_dt_nodes() kernel: thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR kernel: vt_ioctl: fix array_index_nospec in vt_setactivate kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. kernel: lz4: fix LZ4_decompress_safe_partial read out of bound kernel: x86/mce: Work around an erratum on fast string copy instructions…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: use after free in i2c kernel: bluetooth: BR/EDR Bluetooth Impersonation Attacks (BIAS) kernel: hwmon: (lm90) Prevent integer overflow/underflow in hysteresis calculations kernel: asix: fix uninit-value in asix_mdio_read() kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: powerpc/64s: fix program check interrupt emergency stack path kernel: powerpc/64s: Fix unrecoverable MCE calling async handler from NMI kernel: lib/generic-radix-tree.c: Don&amp;#39;t overflow in peek() kernel: powerpc/smp: do not decrement idle task preempt count in CPU offline kernel: can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible() kernel: usbnet: sanity check for maxpacket kernel: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells kernel: aio: fix use-after-free due to missing POLLFREE handling kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: of: fdt: fix off-by-one error in unflatten_dt_nodes() kernel: thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR kernel: vt_ioctl: fix array_index_nospec in vt_setactivate kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. kernel: lz4: fix LZ4_decompress_safe_partial read out of bound kernel: x86/mce: Work around an erratum on fast string copy instructions…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:9315</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:0855-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:0855-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:0855-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26589</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26589</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 132 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off for validation. However, variable offset ptr alu is not prohibited for this ptr kind. So the variable offset is not checked. The following prog is accepted:   func#0 @0   0: R1=ctx() R10=fp0   0: (bf) r6 = r1                       ; R1=ctx() R6_w=ctx()   1: (79) r7 = *(u64 *)(r6 +144)        ; R6_w=ctx() R7_w=flow_keys()   2: (b7) r8 = 1024                     ; R8_w=1024   3: (37) r8 /= 1                       ; R8_w=scalar()   4: (57) r8 &amp;amp;= 1024                    ; R8_w=scalar(smin=smin32=0,   smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400))   5: (0f) r7 += r8   mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1   mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &amp;amp;= 1024   mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1   mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024   6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off   =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024,   var_off=(0x0; 0x400))   6: (79) r0 = *(u64 *)(r7 +0)          ; R0_w=scalar()   7: (95) exit This prog loads flow_keys to r7, and adds the variable offset r8 to r7, and finally causes out-of-bounds access:   BUG: unable to handle page fault for address: ffffc90014c80038   [...]   Call Trace:    &amp;lt;TASK&amp;gt;    bpf_dispatcher_nop_func include/linu…&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 132 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off for validation. However, variable offset ptr alu is not prohibited for this ptr kind. So the variable offset is not checked. The following prog is accepted:   func#0 @0   0: R1=ctx() R10=fp0   0: (bf) r6 = r1                       ; R1=ctx() R6_w=ctx()   1: (79) r7 = *(u64 *)(r6 +144)        ; R6_w=ctx() R7_w=flow_keys()   2: (b7) r8 = 1024                     ; R8_w=1024   3: (37) r8 /= 1                       ; R8_w=scalar()   4: (57) r8 &amp;amp;= 1024                    ; R8_w=scalar(smin=smin32=0,   smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400))   5: (0f) r7 += r8   mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1   mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &amp;amp;= 1024   mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1   mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024   6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off   =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024,   var_off=(0x0; 0x400))   6: (79) r0 = *(u64 *)(r7 +0)          ; R0_w=scalar()   7: (95) exit This prog loads flow_keys to r7, and adds the variable offset r8 to r7, and finally causes out-of-bounds access:   BUG: unable to handle page fault for address: ffffc90014c80038   [...]   Call Trace:    &amp;lt;TASK&amp;gt;    bpf_dispatcher_nop_func include/linu…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26589</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0473 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0473</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0473</guid>
    </item>
  </channel>
</rss>
