<?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:28:13 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:7000 — Important: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2024:7000</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 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;CVE-2023-6040  CVE-2024-26595  CVE-2024-26600  CVE-2021-46984  CVE-2023-52478  CVE-2023-52476  CVE-2023-52522  CVE-2021-47101  CVE-2021-47097  CVE-2023-52605  CVE-2024-26638  CVE-2024-26645  CVE-2024-26665  CVE-2024-26720  CVE-2024-26717  CVE-2024-26769  CVE-2024-26846  CVE-2024-26894  CVE-2024-26880  CVE-2024-26855  CVE-2024-26923  CVE-2024-26939  CVE-2024-27013  CVE-2024-27042  CVE-2024-35809  CVE-2023-52683  CVE-2024-35884  CVE-2024-35877  CVE-2024-35944  CVE-2024-35989  CVE-2021-47412  CVE-2021-47393  CVE-2021-47386  CVE-2021-47385  CVE-2021-47384  CVE-2021-47383  CVE-2021-47432  CVE-2021-47352  CVE-2021-47338  CVE-2021-47321  CVE-2021-47289  CVE-2021-47287  CVE-2023-52798  CVE-2023-52809  CVE-2023-52817  CVE-2023-52840  CVE-2023-52800  CVE-2021-47441  CVE-2021-47466  CVE-2021-47455  CVE-2021-47497  CVE-2021-47560  CVE-2021-47527  CVE-2024-36883  CVE-2024-36922  CVE-2024-36920  CVE-2024-36902  CVE-2024-36953  CVE-2024-36939  CVE-2024-36919  CVE-2024-36901  CVE-2021-47582  CVE-2021-47609  CVE-2024-38619  CVE-2022-48754  CVE-2022-48760  CVE-2024-38581  CVE-2024-38579  CVE-2024-38570  CVE-2024-38559  CVE-2024-38558  CVE-2024-37356  CVE-2024-39471  CVE-2024-39499  CVE-2024-39501  CVE-2024-39506  CVE-2024-40904  CVE-2024-40911  CVE-2024-40912  CVE-2024-40929  CVE-2024-40931  CVE-2024-40941  CVE-2024-40954  CVE-2024-40958  CVE-2024-40959  CVE-2024-40960  CVE-2024-40972…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 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;CVE-2023-6040  CVE-2024-26595  CVE-2024-26600  CVE-2021-46984  CVE-2023-52478  CVE-2023-52476  CVE-2023-52522  CVE-2021-47101  CVE-2021-47097  CVE-2023-52605  CVE-2024-26638  CVE-2024-26645  CVE-2024-26665  CVE-2024-26720  CVE-2024-26717  CVE-2024-26769  CVE-2024-26846  CVE-2024-26894  CVE-2024-26880  CVE-2024-26855  CVE-2024-26923  CVE-2024-26939  CVE-2024-27013  CVE-2024-27042  CVE-2024-35809  CVE-2023-52683  CVE-2024-35884  CVE-2024-35877  CVE-2024-35944  CVE-2024-35989  CVE-2021-47412  CVE-2021-47393  CVE-2021-47386  CVE-2021-47385  CVE-2021-47384  CVE-2021-47383  CVE-2021-47432  CVE-2021-47352  CVE-2021-47338  CVE-2021-47321  CVE-2021-47289  CVE-2021-47287  CVE-2023-52798  CVE-2023-52809  CVE-2023-52817  CVE-2023-52840  CVE-2023-52800  CVE-2021-47441  CVE-2021-47466  CVE-2021-47455  CVE-2021-47497  CVE-2021-47560  CVE-2021-47527  CVE-2024-36883  CVE-2024-36922  CVE-2024-36920  CVE-2024-36902  CVE-2024-36953  CVE-2024-36939  CVE-2024-36919  CVE-2024-36901  CVE-2021-47582  CVE-2021-47609  CVE-2024-38619  CVE-2022-48754  CVE-2022-48760  CVE-2024-38581  CVE-2024-38579  CVE-2024-38570  CVE-2024-38559  CVE-2024-38558  CVE-2024-37356  CVE-2024-39471  CVE-2024-39499  CVE-2024-39501  CVE-2024-39506  CVE-2024-40904  CVE-2024-40911  CVE-2024-40912  CVE-2024-40929  CVE-2024-40931  CVE-2024-40941  CVE-2024-40954  CVE-2024-40958  CVE-2024-40959  CVE-2024-40960  CVE-2024-40972…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2024:7000</guid>
    </item>
    <item>
      <title>bdu:2024-08309</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-08309</link>
      <description>bdu:2024-08309</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-08309</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-41014</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-41014</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-41014</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0669 — 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-0669</link>
      <description>certfr-2024-avi-0669</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0669</guid>
    </item>
    <item>
      <title>EUVD-2026-345907</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345907</link>
      <description>EUVD-2026-345907</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345907</guid>
    </item>
    <item>
      <title>fkie_cve-2024-41014</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-41014</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfs: add bounds checking to xlog_recover_process_data&lt;/p&gt;
&lt;p&gt;There is a lack of verification of the space occupied by fixed members
of xlog_op_header in the xlog_recover_process_data.&lt;/p&gt;
&lt;p&gt;We can create a crafted image to trigger an out of bounds read by
following these steps:
    1) Mount an image of xfs, and do some file operations to leave records
    2) Before umounting, copy the image for subsequent steps to simulate
       abnormal exit. Because umount will ensure that tail_blk and
       head_blk are the same, which will result in the inability to enter
       xlog_recover_process_data
    3) Write a tool to parse and modify the copied image in step 2
    4) Make the end of the xlog_op_header entries only 1 byte away from
       xlog_rec_header-&amp;gt;h_size
    5) xlog_rec_header-&amp;gt;h_num_logops++
    6) Modify xlog_rec_header-&amp;gt;h_crc&lt;/p&gt;
&lt;p&gt;Fix:
Add a check to make sure there is sufficient space to access fixed members
of xlog_op_header.&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;xfs: add bounds checking to xlog_recover_process_data&lt;/p&gt;
&lt;p&gt;There is a lack of verification of the space occupied by fixed members
of xlog_op_header in the xlog_recover_process_data.&lt;/p&gt;
&lt;p&gt;We can create a crafted image to trigger an out of bounds read by
following these steps:
    1) Mount an image of xfs, and do some file operations to leave records
    2) Before umounting, copy the image for subsequent steps to simulate
       abnormal exit. Because umount will ensure that tail_blk and
       head_blk are the same, which will result in the inability to enter
       xlog_recover_process_data
    3) Write a tool to parse and modify the copied image in step 2
    4) Make the end of the xlog_op_header entries only 1 byte away from
       xlog_rec_header-&amp;gt;h_size
    5) xlog_rec_header-&amp;gt;h_num_logops++
    6) Modify xlog_rec_header-&amp;gt;h_crc&lt;/p&gt;
&lt;p&gt;Fix:
Add a check to make sure there is sufficient space to access fixed members
of xlog_op_header.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-41014</guid>
    </item>
    <item>
      <title>GHSA-jfpf-jvq3-6jwv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jfpf-jvq3-6jwv</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfs: add bounds checking to xlog_recover_process_data&lt;/p&gt;
&lt;p&gt;There is a lack of verification of the space occupied by fixed members
of xlog_op_header in the xlog_recover_process_data.&lt;/p&gt;
&lt;p&gt;We can create a crafted image to trigger an out of bounds read by
following these steps:
    1) Mount an image of xfs, and do some file operations to leave records
    2) Before umounting, copy the image for subsequent steps to simulate
       abnormal exit. Because umount will ensure that tail_blk and
       head_blk are the same, which will result in the inability to enter
       xlog_recover_process_data
    3) Write a tool to parse and modify the copied image in step 2
    4) Make the end of the xlog_op_header entries only 1 byte away from
       xlog_rec_header-&amp;gt;h_size
    5) xlog_rec_header-&amp;gt;h_num_logops++
    6) Modify xlog_rec_header-&amp;gt;h_crc&lt;/p&gt;
&lt;p&gt;Fix:
Add a check to make sure there is sufficient space to access fixed members
of xlog_op_header.&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;xfs: add bounds checking to xlog_recover_process_data&lt;/p&gt;
&lt;p&gt;There is a lack of verification of the space occupied by fixed members
of xlog_op_header in the xlog_recover_process_data.&lt;/p&gt;
&lt;p&gt;We can create a crafted image to trigger an out of bounds read by
following these steps:
    1) Mount an image of xfs, and do some file operations to leave records
    2) Before umounting, copy the image for subsequent steps to simulate
       abnormal exit. Because umount will ensure that tail_blk and
       head_blk are the same, which will result in the inability to enter
       xlog_recover_process_data
    3) Write a tool to parse and modify the copied image in step 2
    4) Make the end of the xlog_op_header entries only 1 byte away from
       xlog_rec_header-&amp;gt;h_size
    5) xlog_rec_header-&amp;gt;h_num_logops++
    6) Modify xlog_rec_header-&amp;gt;h_crc&lt;/p&gt;
&lt;p&gt;Fix:
Add a check to make sure there is sufficient space to access fixed members
of xlog_op_header.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jfpf-jvq3-6jwv</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-41014 — xfs: add bounds checking to xlog_recover_process_data</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-41014</link>
      <description>msrc_CVE-2024-41014</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-41014</guid>
    </item>
    <item>
      <title>OESA-2024-1960 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1960</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.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;
efi: libstub: only free priv.runtime_map when allocated&#13;
&#13;
priv.runtime_map is only allocated when efi_novamap is not set.
Otherwise, it is an uninitialized value.  In the error path, it is freed
unconditionally.  Avoid passing an uninitialized value to free_pool.
Free priv.runtime_map only when it was allocated.&#13;
&#13;
This bug was discovered and resolved using Coverity Static Analysis
Security Testing (SAST) by Synopsys, Inc.(CVE-2024-33619)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
fpga: region: add owner module and take its refcount&#13;
&#13;
The current implementation of the fpga region assumes that the low-level
module registers a driver for the parent device and uses its owner pointer
to take the module&amp;amp;apos;s refcount. This approach is problematic since it can
lead to a null pointer dereference while attempting to get the region
during programming if the parent device does not have a driver.&#13;
&#13;
To address this problem, add a module owner pointer to the fpga_region
struct and use it to take the module&amp;amp;apos;s refcount. Modify the functions for
registering a region to take an additional owner module parameter and
rename them to avoid conflicts. Use the old function names for helper
macros that automatically set the module that registers the region as the
owner. This ensures compatibility with existing low…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.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;
efi: libstub: only free priv.runtime_map when allocated&#13;
&#13;
priv.runtime_map is only allocated when efi_novamap is not set.
Otherwise, it is an uninitialized value.  In the error path, it is freed
unconditionally.  Avoid passing an uninitialized value to free_pool.
Free priv.runtime_map only when it was allocated.&#13;
&#13;
This bug was discovered and resolved using Coverity Static Analysis
Security Testing (SAST) by Synopsys, Inc.(CVE-2024-33619)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
fpga: region: add owner module and take its refcount&#13;
&#13;
The current implementation of the fpga region assumes that the low-level
module registers a driver for the parent device and uses its owner pointer
to take the module&amp;amp;apos;s refcount. This approach is problematic since it can
lead to a null pointer dereference while attempting to get the region
during programming if the parent device does not have a driver.&#13;
&#13;
To address this problem, add a module owner pointer to the fpga_region
struct and use it to take the module&amp;amp;apos;s refcount. Modify the functions for
registering a region to take an additional owner module parameter and
rename them to avoid conflicts. Use the old function names for helper
macros that automatically set the module that registers the region as the
owner. This ensures compatibility with existing low…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1960</guid>
    </item>
    <item>
      <title>RHSA-2024:10262 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:10262</link>
      <description>&lt;p&gt;kernel: improper input validation may lead to privilege escalation kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: userfaultfd: fix a race between writeprotect and exit_mmap() kernel: Linux ebpf logic vulnerability leads to critical memory read and write gaining root privileges kernel: local privileges escalation in kernel/bpf/verifier.c kernel: nvme-tcp: fix UAF when detecting digest errors kernel: xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. kernel: x86/mm: Randomize per-cpu entry area kernel: mm/sparsemem: fix race in accessing memory_section-&amp;gt;usage kernel: blk-mq: fix IO hang from sbitmap wakeup race kernel: mac802154: fix llsec key resources release in mac802154_llsec_key_del kernel: genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline kernel: vt: fix unicode buffer corruption when deleting characters kernel: mptcp: ensure snd_nxt is properly initialized on connect kernel: scsi: mpi3mr: Avoid memcpy field-spanning write WARNING kernel: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE kernel: drm/radeon: fix UBSAN warning in kv_dpm.c kernel: bpf: Fix overrunning reservations in ringbuf kernel: xfs: add bounds checking to xlog_recover_process_data kernel: sched/deadline: Fix task_struct reference leak kernel: mptcp: pm: Fix uaf in __timer_delete_sync&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: improper input validation may lead to privilege escalation kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: userfaultfd: fix a race between writeprotect and exit_mmap() kernel: Linux ebpf logic vulnerability leads to critical memory read and write gaining root privileges kernel: local privileges escalation in kernel/bpf/verifier.c kernel: nvme-tcp: fix UAF when detecting digest errors kernel: xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. kernel: x86/mm: Randomize per-cpu entry area kernel: mm/sparsemem: fix race in accessing memory_section-&amp;gt;usage kernel: blk-mq: fix IO hang from sbitmap wakeup race kernel: mac802154: fix llsec key resources release in mac802154_llsec_key_del kernel: genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline kernel: vt: fix unicode buffer corruption when deleting characters kernel: mptcp: ensure snd_nxt is properly initialized on connect kernel: scsi: mpi3mr: Avoid memcpy field-spanning write WARNING kernel: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE kernel: drm/radeon: fix UBSAN warning in kv_dpm.c kernel: bpf: Fix overrunning reservations in ringbuf kernel: xfs: add bounds checking to xlog_recover_process_data kernel: sched/deadline: Fix task_struct reference leak kernel: mptcp: pm: Fix uaf in __timer_delete_sync&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:10262</guid>
    </item>
    <item>
      <title>RHSA-2024:7000 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:7000</link>
      <description>&lt;p&gt;kernel: kyber: fix out of bounds access when preempted kernel: Input: elantech - fix stack out of bound access in elantech_change_report_id() kernel: asix: fix uninit-value in asix_mdio_read() kernel: driver core: auxiliary bus: Fix memory leak when driver_register() fail kernel: ACPI: fix NULL pointer dereference kernel: watchdog: Fix possible use-after-free by calling del_timer_sync() kernel: fbmem: Do not delete the mode that is still in use kernel: virtio-net: Add validation for used length kernel: tty: Fix out-of-bound vmalloc access in imageblit kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83792d) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: block: don&amp;#39;t call rq_qos_ops-&amp;gt;done_bio if the bio isn&amp;#39;t tracked kernel: lib/generic-radix-tree.c: Don&amp;#39;t overflow in peek() kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: ptp: Fix possible memory leak in ptp_clock_register() kernel: mm, slub: fix potential memoryleak in kmem_cache_open() kernel: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells kernel: serial: core: fix transmit-buffer reset and memleak kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: USB: core: Make do_proc_control() and do_proc_bulk() k…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: kyber: fix out of bounds access when preempted kernel: Input: elantech - fix stack out of bound access in elantech_change_report_id() kernel: asix: fix uninit-value in asix_mdio_read() kernel: driver core: auxiliary bus: Fix memory leak when driver_register() fail kernel: ACPI: fix NULL pointer dereference kernel: watchdog: Fix possible use-after-free by calling del_timer_sync() kernel: fbmem: Do not delete the mode that is still in use kernel: virtio-net: Add validation for used length kernel: tty: Fix out-of-bound vmalloc access in imageblit kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83792d) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: block: don&amp;#39;t call rq_qos_ops-&amp;gt;done_bio if the bio isn&amp;#39;t tracked kernel: lib/generic-radix-tree.c: Don&amp;#39;t overflow in peek() kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: ptp: Fix possible memory leak in ptp_clock_register() kernel: mm, slub: fix potential memoryleak in kmem_cache_open() kernel: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells kernel: serial: core: fix transmit-buffer reset and memleak kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: USB: core: Make do_proc_control() and do_proc_bulk() k…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:7000</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2802-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2802-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:2802-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-41014</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-41014</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 192 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfs: add bounds checking to xlog_recover_process_data There is a lack of verification of the space occupied by fixed members of xlog_op_header in the xlog_recover_process_data. We can create a crafted image to trigger an out of bounds read by following these steps:     1) Mount an image of xfs, and do some file operations to leave records     2) Before umounting, copy the image for subsequent steps to simulate        abnormal exit. Because umount will ensure that tail_blk and        head_blk are the same, which will result in the inability to enter        xlog_recover_process_data     3) Write a tool to parse and modify the copied image in step 2     4) Make the end of the xlog_op_header entries only 1 byte away from        xlog_rec_header-&amp;gt;h_size     5) xlog_rec_header-&amp;gt;h_num_logops++     6) Modify xlog_rec_header-&amp;gt;h_crc Fix: Add a check to make sure there is sufficient space to access fixed members of xlog_op_header.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 192 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfs: add bounds checking to xlog_recover_process_data There is a lack of verification of the space occupied by fixed members of xlog_op_header in the xlog_recover_process_data. We can create a crafted image to trigger an out of bounds read by following these steps:     1) Mount an image of xfs, and do some file operations to leave records     2) Before umounting, copy the image for subsequent steps to simulate        abnormal exit. Because umount will ensure that tail_blk and        head_blk are the same, which will result in the inability to enter        xlog_recover_process_data     3) Write a tool to parse and modify the copied image in step 2     4) Make the end of the xlog_op_header entries only 1 byte away from        xlog_rec_header-&amp;gt;h_size     5) xlog_rec_header-&amp;gt;h_num_logops++     6) Modify xlog_rec_header-&amp;gt;h_crc Fix: Add a check to make sure there is sufficient space to access fixed members of xlog_op_header.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-41014</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1721 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1721</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1721</guid>
    </item>
  </channel>
</rss>
