<?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 18:44:11 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:21556 — Important: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2026:21556</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, AlmaLinux:9: kernel-64k-debug-modules-extra and 64 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;* kernel: proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al (CVE-2025-38653)
  * kernel: ima: don&amp;#39;t clear IMA_DIGSIG flag when setting or removing non-IMA xattr (CVE-2025-68183)
  * kernel: nbd: defer config unlock in nbd_genl_connect (CVE-2025-68366)
  * kernel: crypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id (CVE-2025-68724)
  * kernel: iommu: disable SVA when CONFIG_X86 is set (CVE-2025-71089)
  * kernel: netfilter: nf_tables: release flowtable after rcu grace period on error (CVE-2026-23392)
  * kernel: netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() (CVE-2026-23455)
  * kernel: Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (CVE-2026-31408)
  * kernel: net: sched: act_csum: validate nested VLAN headers (CVE-2026-31684)
  * kernel: netfilter: ip6t_eui64: reject invalid MAC header for all packets (CVE-2026-31685)
  * kernel: netfilter: nf_conntrack_helper: pass helper to expect cleanup (CVE-2026-43027)
  * kernel: Bluetooth: MGMT: validate LTK enc_size on load (CVE-2026-43020)
  * kernel: HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq (CVE-2026-43051)
  * kernel: smb: client: validate the whole DACL before rewriting it in cifsacl (CVE-2026-31709)
  * kernel: Bluetooth: SCO: fix race conditions in sco_sock_connect() (CVE-2026-43023)
  * kernel:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, AlmaLinux:9: kernel-64k-debug-modules-extra and 64 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;* kernel: proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al (CVE-2025-38653)
  * kernel: ima: don&amp;#39;t clear IMA_DIGSIG flag when setting or removing non-IMA xattr (CVE-2025-68183)
  * kernel: nbd: defer config unlock in nbd_genl_connect (CVE-2025-68366)
  * kernel: crypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id (CVE-2025-68724)
  * kernel: iommu: disable SVA when CONFIG_X86 is set (CVE-2025-71089)
  * kernel: netfilter: nf_tables: release flowtable after rcu grace period on error (CVE-2026-23392)
  * kernel: netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() (CVE-2026-23455)
  * kernel: Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (CVE-2026-31408)
  * kernel: net: sched: act_csum: validate nested VLAN headers (CVE-2026-31684)
  * kernel: netfilter: ip6t_eui64: reject invalid MAC header for all packets (CVE-2026-31685)
  * kernel: netfilter: nf_conntrack_helper: pass helper to expect cleanup (CVE-2026-43027)
  * kernel: Bluetooth: MGMT: validate LTK enc_size on load (CVE-2026-43020)
  * kernel: HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq (CVE-2026-43051)
  * kernel: smb: client: validate the whole DACL before rewriting it in cifsacl (CVE-2026-31709)
  * kernel: Bluetooth: SCO: fix race conditions in sco_sock_connect() (CVE-2026-43023)
  * kernel:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2026:21556</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-68183</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-68183</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-2025-68183</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0108 — 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-2026-avi-0108</link>
      <description>certfr-2026-avi-0108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</guid>
    </item>
    <item>
      <title>ESSA-2026:0165 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/essa-2026:0165</link>
      <description>&lt;p&gt;Important: kernel security, bug fix, and enhancement update&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Important: kernel security, bug fix, and enhancement update&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/essa-2026:0165</guid>
    </item>
    <item>
      <title>EUVD-2026-347455</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347455</link>
      <description>EUVD-2026-347455</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347455</guid>
    </item>
    <item>
      <title>fkie_cve-2025-68183</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-68183</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ima: don&amp;#39;t clear IMA_DIGSIG flag when setting or removing non-IMA xattr&lt;/p&gt;
&lt;p&gt;Currently when both IMA and EVM are in fix mode, the IMA signature will
be reset to IMA hash if a program first stores IMA signature in
security.ima and then writes/removes some other security xattr for the
file.&lt;/p&gt;
&lt;p&gt;For example, on Fedora, after booting the kernel with &amp;#34;ima_appraise=fix
evm=fix ima_policy=appraise_tcb&amp;#34; and installing rpm-plugin-ima,
installing/reinstalling a package will not make good reference IMA
signature generated. Instead IMA hash is generated,&lt;/p&gt;
&lt;p&gt;# getfattr -m - -d -e hex /usr/bin/bash
    # file: usr/bin/bash
    security.ima=0x0404...&lt;/p&gt;
&lt;p&gt;This happens because when setting security.selinux, the IMA_DIGSIG flag
that had been set early was cleared. As a result, IMA hash is generated
when the file is closed.&lt;/p&gt;
&lt;p&gt;Similarly, IMA signature can be cleared on file close after removing
security xattr like security.evm or setting/removing ACL.&lt;/p&gt;
&lt;p&gt;Prevent replacing the IMA file signature with a file hash, by preventing
the IMA_DIGSIG flag from being reset.&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s a minimal C reproducer which sets security.selinux as the last
step which can also replaced by removing security.evm or setting ACL,&lt;/p&gt;
&lt;p&gt;#include &amp;lt;stdio.h&amp;gt;
    #include &amp;lt;sys/xattr.h&amp;gt;
    #include &amp;lt;fcntl.h&amp;gt;
    #include &amp;lt;unistd.h&amp;gt;
    #include &amp;lt;string.h&amp;gt;
    #include &amp;lt;stdlib.h&amp;gt;&lt;/p&gt;
&lt;p&gt;int main() {
        const char* file_path = &amp;#34;/usr/sbin/test_binary&amp;#34;;
        const char*…&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;ima: don&amp;#39;t clear IMA_DIGSIG flag when setting or removing non-IMA xattr&lt;/p&gt;
&lt;p&gt;Currently when both IMA and EVM are in fix mode, the IMA signature will
be reset to IMA hash if a program first stores IMA signature in
security.ima and then writes/removes some other security xattr for the
file.&lt;/p&gt;
&lt;p&gt;For example, on Fedora, after booting the kernel with &amp;#34;ima_appraise=fix
evm=fix ima_policy=appraise_tcb&amp;#34; and installing rpm-plugin-ima,
installing/reinstalling a package will not make good reference IMA
signature generated. Instead IMA hash is generated,&lt;/p&gt;
&lt;p&gt;# getfattr -m - -d -e hex /usr/bin/bash
    # file: usr/bin/bash
    security.ima=0x0404...&lt;/p&gt;
&lt;p&gt;This happens because when setting security.selinux, the IMA_DIGSIG flag
that had been set early was cleared. As a result, IMA hash is generated
when the file is closed.&lt;/p&gt;
&lt;p&gt;Similarly, IMA signature can be cleared on file close after removing
security xattr like security.evm or setting/removing ACL.&lt;/p&gt;
&lt;p&gt;Prevent replacing the IMA file signature with a file hash, by preventing
the IMA_DIGSIG flag from being reset.&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s a minimal C reproducer which sets security.selinux as the last
step which can also replaced by removing security.evm or setting ACL,&lt;/p&gt;
&lt;p&gt;#include &amp;lt;stdio.h&amp;gt;
    #include &amp;lt;sys/xattr.h&amp;gt;
    #include &amp;lt;fcntl.h&amp;gt;
    #include &amp;lt;unistd.h&amp;gt;
    #include &amp;lt;string.h&amp;gt;
    #include &amp;lt;stdlib.h&amp;gt;&lt;/p&gt;
&lt;p&gt;int main() {
        const char* file_path = &amp;#34;/usr/sbin/test_binary&amp;#34;;
        const char*…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-68183</guid>
    </item>
    <item>
      <title>GHSA-w26q-x7h4-9gc5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w26q-x7h4-9gc5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ima: don&amp;#39;t clear IMA_DIGSIG flag when setting or removing non-IMA xattr&lt;/p&gt;
&lt;p&gt;Currently when both IMA and EVM are in fix mode, the IMA signature will
be reset to IMA hash if a program first stores IMA signature in
security.ima and then writes/removes some other security xattr for the
file.&lt;/p&gt;
&lt;p&gt;For example, on Fedora, after booting the kernel with &amp;#34;ima_appraise=fix
evm=fix ima_policy=appraise_tcb&amp;#34; and installing rpm-plugin-ima,
installing/reinstalling a package will not make good reference IMA
signature generated. Instead IMA hash is generated,&lt;/p&gt;
&lt;p&gt;# getfattr -m - -d -e hex /usr/bin/bash
    # file: usr/bin/bash
    security.ima=0x0404...&lt;/p&gt;
&lt;p&gt;This happens because when setting security.selinux, the IMA_DIGSIG flag
that had been set early was cleared. As a result, IMA hash is generated
when the file is closed.&lt;/p&gt;
&lt;p&gt;Similarly, IMA signature can be cleared on file close after removing
security xattr like security.evm or setting/removing ACL.&lt;/p&gt;
&lt;p&gt;Prevent replacing the IMA file signature with a file hash, by preventing
the IMA_DIGSIG flag from being reset.&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s a minimal C reproducer which sets security.selinux as the last
step which can also replaced by removing security.evm or setting ACL,&lt;/p&gt;
&lt;p&gt;#include &amp;lt;stdio.h&amp;gt;
    #include &amp;lt;sys/xattr.h&amp;gt;
    #include &amp;lt;fcntl.h&amp;gt;
    #include &amp;lt;unistd.h&amp;gt;
    #include &amp;lt;string.h&amp;gt;
    #include &amp;lt;stdlib.h&amp;gt;&lt;/p&gt;
&lt;p&gt;int main() {
        const char* file_path = &amp;#34;/usr/sbin/test_binary&amp;#34;;
        const char*…&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;ima: don&amp;#39;t clear IMA_DIGSIG flag when setting or removing non-IMA xattr&lt;/p&gt;
&lt;p&gt;Currently when both IMA and EVM are in fix mode, the IMA signature will
be reset to IMA hash if a program first stores IMA signature in
security.ima and then writes/removes some other security xattr for the
file.&lt;/p&gt;
&lt;p&gt;For example, on Fedora, after booting the kernel with &amp;#34;ima_appraise=fix
evm=fix ima_policy=appraise_tcb&amp;#34; and installing rpm-plugin-ima,
installing/reinstalling a package will not make good reference IMA
signature generated. Instead IMA hash is generated,&lt;/p&gt;
&lt;p&gt;# getfattr -m - -d -e hex /usr/bin/bash
    # file: usr/bin/bash
    security.ima=0x0404...&lt;/p&gt;
&lt;p&gt;This happens because when setting security.selinux, the IMA_DIGSIG flag
that had been set early was cleared. As a result, IMA hash is generated
when the file is closed.&lt;/p&gt;
&lt;p&gt;Similarly, IMA signature can be cleared on file close after removing
security xattr like security.evm or setting/removing ACL.&lt;/p&gt;
&lt;p&gt;Prevent replacing the IMA file signature with a file hash, by preventing
the IMA_DIGSIG flag from being reset.&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s a minimal C reproducer which sets security.selinux as the last
step which can also replaced by removing security.evm or setting ACL,&lt;/p&gt;
&lt;p&gt;#include &amp;lt;stdio.h&amp;gt;
    #include &amp;lt;sys/xattr.h&amp;gt;
    #include &amp;lt;fcntl.h&amp;gt;
    #include &amp;lt;unistd.h&amp;gt;
    #include &amp;lt;string.h&amp;gt;
    #include &amp;lt;stdlib.h&amp;gt;&lt;/p&gt;
&lt;p&gt;int main() {
        const char* file_path = &amp;#34;/usr/sbin/test_binary&amp;#34;;
        const char*…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w26q-x7h4-9gc5</guid>
    </item>
    <item>
      <title>OESA-2026-2675 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-2675</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/i915/gt: Fix timeline left held on VMA alloc error&lt;/p&gt;
&lt;p&gt;The following error has been reported sporadically by CI when a test
unbinds the i915 driver on a ring submission platform:&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;4&amp;amp;gt; [239.330153] ------------[ cut here ]------------
&amp;amp;lt;4&amp;amp;gt; [239.330166] i915 0000:00:02.0: [drm] drm_WARN_ON(dev_priv-&amp;amp;gt;mm.shrink_count)
&amp;amp;lt;4&amp;amp;gt; [239.330196] WARNING: CPU: 1 PID: 18570 at drivers/gpu/drm/i915/i915_gem.c:1309 i915_gem_cleanup_early+0x13e/0x150 [i915]
...
&amp;amp;lt;4&amp;amp;gt; [239.330640] RIP: 0010:i915_gem_cleanup_early+0x13e/0x150 [i915]
...
&amp;amp;lt;4&amp;amp;gt; [239.330942] Call Trace:
&amp;amp;lt;4&amp;amp;gt; [239.330944]  &amp;amp;lt;TASK&amp;amp;gt;
&amp;amp;lt;4&amp;amp;gt; [239.330949]  i915_driver_late_release+0x2b/0xa0 [i915]
&amp;amp;lt;4&amp;amp;gt; [239.331202]  i915_driver_release+0x86/0xa0 [i915]
&amp;amp;lt;4&amp;amp;gt; [239.331482]  devm_drm_dev_init_release+0x61/0x90
&amp;amp;lt;4&amp;amp;gt; [239.331494]  devm_action_release+0x15/0x30
&amp;amp;lt;4&amp;amp;gt; [239.331504]  release_nodes+0x3d/0x120
&amp;amp;lt;4&amp;amp;gt; [239.331517]  devres_release_all+0x96/0xd0
&amp;amp;lt;4&amp;amp;gt; [239.331533]  device_unbind_cleanup+0x12/0x80
&amp;amp;lt;4&amp;amp;gt; [239.331543]  device_release_driver_internal+0x23a/0x280
&amp;amp;lt;4&amp;amp;gt; [239.331550]  ? bus_find_device+0xa5/0xe0
&amp;amp;lt;4&amp;amp;gt; [239.331563]  device_driver_detach+0x14/0x20
...
&amp;amp;lt;4&amp;amp;gt; [357.719679] ---[ end trace 0000000000000000 ]---&lt;/p&gt;
&lt;p&gt;If the test also unloads the i915 module then that&amp;amp;apos;s followed with:&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;3&amp;amp;gt; [357.787478] ===…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/i915/gt: Fix timeline left held on VMA alloc error&lt;/p&gt;
&lt;p&gt;The following error has been reported sporadically by CI when a test
unbinds the i915 driver on a ring submission platform:&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;4&amp;amp;gt; [239.330153] ------------[ cut here ]------------
&amp;amp;lt;4&amp;amp;gt; [239.330166] i915 0000:00:02.0: [drm] drm_WARN_ON(dev_priv-&amp;amp;gt;mm.shrink_count)
&amp;amp;lt;4&amp;amp;gt; [239.330196] WARNING: CPU: 1 PID: 18570 at drivers/gpu/drm/i915/i915_gem.c:1309 i915_gem_cleanup_early+0x13e/0x150 [i915]
...
&amp;amp;lt;4&amp;amp;gt; [239.330640] RIP: 0010:i915_gem_cleanup_early+0x13e/0x150 [i915]
...
&amp;amp;lt;4&amp;amp;gt; [239.330942] Call Trace:
&amp;amp;lt;4&amp;amp;gt; [239.330944]  &amp;amp;lt;TASK&amp;amp;gt;
&amp;amp;lt;4&amp;amp;gt; [239.330949]  i915_driver_late_release+0x2b/0xa0 [i915]
&amp;amp;lt;4&amp;amp;gt; [239.331202]  i915_driver_release+0x86/0xa0 [i915]
&amp;amp;lt;4&amp;amp;gt; [239.331482]  devm_drm_dev_init_release+0x61/0x90
&amp;amp;lt;4&amp;amp;gt; [239.331494]  devm_action_release+0x15/0x30
&amp;amp;lt;4&amp;amp;gt; [239.331504]  release_nodes+0x3d/0x120
&amp;amp;lt;4&amp;amp;gt; [239.331517]  devres_release_all+0x96/0xd0
&amp;amp;lt;4&amp;amp;gt; [239.331533]  device_unbind_cleanup+0x12/0x80
&amp;amp;lt;4&amp;amp;gt; [239.331543]  device_release_driver_internal+0x23a/0x280
&amp;amp;lt;4&amp;amp;gt; [239.331550]  ? bus_find_device+0xa5/0xe0
&amp;amp;lt;4&amp;amp;gt; [239.331563]  device_driver_detach+0x14/0x20
...
&amp;amp;lt;4&amp;amp;gt; [357.719679] ---[ end trace 0000000000000000 ]---&lt;/p&gt;
&lt;p&gt;If the test also unloads the i915 module then that&amp;amp;apos;s followed with:&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;3&amp;amp;gt; [357.787478] ===…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-2675</guid>
    </item>
    <item>
      <title>RHSA-2026:21745 — Red Hat Security Advisory: kernel-rt security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:21745</link>
      <description>&lt;p&gt;kernel: Bluetooth: MGMT: Fix possible UAFs kernel: ima: don&amp;#39;t clear IMA_DIGSIG flag when setting or removing non-IMA xattr kernel: ALSA: firewire-motu: fix buffer overflow in hwdep read for DSP events kernel: libceph: make decode_pool() more resilient against corrupted osdmaps kernel: Linux kernel: Denial of service and memory corruption in RDMA umad kernel: Linux kernel: Use-after-free in traffic control (act_ct) may lead to denial of service or privilege escalation kernel: netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() kernel: Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold kernel: can: raw: fix ro-&amp;gt;uniq use-after-free in raw_rcv() kernel: net: sched: act_csum: validate nested VLAN headers kernel: netfilter: ip6t_eui64: reject invalid MAC header for all packets kernel: smb: client: validate the whole DACL before rewriting it in cifsacl kernel: Bluetooth: MGMT: validate LTK enc_size on load kernel: netfilter: nf_conntrack_helper: pass helper to expect cleanup kernel: HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq kernel: xfs: fix freemap adjustments when adding xattrs to leaf blocks kernel: md/bitmap: fix GPF in write_page caused by resize race kernel: netfilter: xt_tcpmss: check remaining length before reading optlen kernel: smb: client: validate dacloffset before building DACL pointers&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: Bluetooth: MGMT: Fix possible UAFs kernel: ima: don&amp;#39;t clear IMA_DIGSIG flag when setting or removing non-IMA xattr kernel: ALSA: firewire-motu: fix buffer overflow in hwdep read for DSP events kernel: libceph: make decode_pool() more resilient against corrupted osdmaps kernel: Linux kernel: Denial of service and memory corruption in RDMA umad kernel: Linux kernel: Use-after-free in traffic control (act_ct) may lead to denial of service or privilege escalation kernel: netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() kernel: Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold kernel: can: raw: fix ro-&amp;gt;uniq use-after-free in raw_rcv() kernel: net: sched: act_csum: validate nested VLAN headers kernel: netfilter: ip6t_eui64: reject invalid MAC header for all packets kernel: smb: client: validate the whole DACL before rewriting it in cifsacl kernel: Bluetooth: MGMT: validate LTK enc_size on load kernel: netfilter: nf_conntrack_helper: pass helper to expect cleanup kernel: HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq kernel: xfs: fix freemap adjustments when adding xattrs to leaf blocks kernel: md/bitmap: fix GPF in write_page caused by resize race kernel: netfilter: xt_tcpmss: check remaining length before reading optlen kernel: smb: client: validate dacloffset before building DACL pointers&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:21745</guid>
    </item>
    <item>
      <title>RLSA-2026:21556 — Important: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rlsa-2026:21556</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:9: kernel&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;* kernel: proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al (CVE-2025-38653)&lt;/p&gt;
&lt;p&gt;* kernel: ima: don&amp;#39;t clear IMA_DIGSIG flag when setting or removing non-IMA xattr (CVE-2025-68183)&lt;/p&gt;
&lt;p&gt;* kernel: nbd: defer config unlock in nbd_genl_connect (CVE-2025-68366)&lt;/p&gt;
&lt;p&gt;* kernel: crypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id (CVE-2025-68724)&lt;/p&gt;
&lt;p&gt;* kernel: iommu: disable SVA when CONFIG_X86 is set (CVE-2025-71089)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: nf_tables: release flowtable after rcu grace period on error (CVE-2026-23392)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() (CVE-2026-23455)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (CVE-2026-31408)&lt;/p&gt;
&lt;p&gt;* kernel: net: sched: act_csum: validate nested VLAN headers (CVE-2026-31684)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: ip6t_eui64: reject invalid MAC header for all packets (CVE-2026-31685)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: nf_conntrack_helper: pass helper to expect cleanup (CVE-2026-43027)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: MGMT: validate LTK enc_size on load (CVE-2026-43020)&lt;/p&gt;
&lt;p&gt;* kernel: HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq (CVE-2026-43051)&lt;/p&gt;
&lt;p&gt;* kernel: smb: client: validate the whole DACL before rewriting it in cifsacl (CVE-2026-31709)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: SCO: fix race conditions in sco_sock_connect() (CVE-2026-43023)&lt;/p&gt;
&lt;p&gt;* kernel: wifi: brcmfmac: vali…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:9: kernel&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;* kernel: proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al (CVE-2025-38653)&lt;/p&gt;
&lt;p&gt;* kernel: ima: don&amp;#39;t clear IMA_DIGSIG flag when setting or removing non-IMA xattr (CVE-2025-68183)&lt;/p&gt;
&lt;p&gt;* kernel: nbd: defer config unlock in nbd_genl_connect (CVE-2025-68366)&lt;/p&gt;
&lt;p&gt;* kernel: crypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id (CVE-2025-68724)&lt;/p&gt;
&lt;p&gt;* kernel: iommu: disable SVA when CONFIG_X86 is set (CVE-2025-71089)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: nf_tables: release flowtable after rcu grace period on error (CVE-2026-23392)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() (CVE-2026-23455)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (CVE-2026-31408)&lt;/p&gt;
&lt;p&gt;* kernel: net: sched: act_csum: validate nested VLAN headers (CVE-2026-31684)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: ip6t_eui64: reject invalid MAC header for all packets (CVE-2026-31685)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: nf_conntrack_helper: pass helper to expect cleanup (CVE-2026-43027)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: MGMT: validate LTK enc_size on load (CVE-2026-43020)&lt;/p&gt;
&lt;p&gt;* kernel: HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq (CVE-2026-43051)&lt;/p&gt;
&lt;p&gt;* kernel: smb: client: validate the whole DACL before rewriting it in cifsacl (CVE-2026-31709)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: SCO: fix race conditions in sco_sock_connect() (CVE-2026-43023)&lt;/p&gt;
&lt;p&gt;* kernel: wifi: brcmfmac: vali…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rlsa-2026:21556</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0278-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0278-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-2026:0278-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-68183</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68183</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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 176 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ima: don&amp;#39;t clear IMA_DIGSIG flag when setting or removing non-IMA xattr Currently when both IMA and EVM are in fix mode, the IMA signature will be reset to IMA hash if a program first stores IMA signature in security.ima and then writes/removes some other security xattr for the file. For example, on Fedora, after booting the kernel with &amp;#34;ima_appraise=fix evm=fix ima_policy=appraise_tcb&amp;#34; and installing rpm-plugin-ima, installing/reinstalling a package will not make good reference IMA signature generated. Instead IMA hash is generated,     # getfattr -m - -d -e hex /usr/bin/bash     # file: usr/bin/bash     security.ima=0x0404... This happens because when setting security.selinux, the IMA_DIGSIG flag that had been set early was cleared. As a result, IMA hash is generated when the file is closed. Similarly, IMA signature can be cleared on file close after removing security xattr like security.evm or setting/removing ACL. Prevent replacing the IMA file signature with a file hash, by preventing the IMA_DIGSIG flag from being reset. Here&amp;#39;s a minimal C reproducer which sets security.selinux as the last step which can also replaced by removing security.evm or setting ACL,     #include &amp;lt;stdio.h&amp;gt;     #include &amp;lt;sys/xattr.h&amp;gt;     #include &amp;lt;fcntl.h&amp;gt;     #include &amp;lt;unistd.h&amp;gt;     #include &amp;lt;string.h&amp;gt;     #include &amp;lt;stdlib.h&amp;gt;     int main() {         const char* file_path = &amp;#34;/usr/sbin/test_binary&amp;#34;;         const char* hex_strin…&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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 176 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ima: don&amp;#39;t clear IMA_DIGSIG flag when setting or removing non-IMA xattr Currently when both IMA and EVM are in fix mode, the IMA signature will be reset to IMA hash if a program first stores IMA signature in security.ima and then writes/removes some other security xattr for the file. For example, on Fedora, after booting the kernel with &amp;#34;ima_appraise=fix evm=fix ima_policy=appraise_tcb&amp;#34; and installing rpm-plugin-ima, installing/reinstalling a package will not make good reference IMA signature generated. Instead IMA hash is generated,     # getfattr -m - -d -e hex /usr/bin/bash     # file: usr/bin/bash     security.ima=0x0404... This happens because when setting security.selinux, the IMA_DIGSIG flag that had been set early was cleared. As a result, IMA hash is generated when the file is closed. Similarly, IMA signature can be cleared on file close after removing security xattr like security.evm or setting/removing ACL. Prevent replacing the IMA file signature with a file hash, by preventing the IMA_DIGSIG flag from being reset. Here&amp;#39;s a minimal C reproducer which sets security.selinux as the last step which can also replaced by removing security.evm or setting ACL,     #include &amp;lt;stdio.h&amp;gt;     #include &amp;lt;sys/xattr.h&amp;gt;     #include &amp;lt;fcntl.h&amp;gt;     #include &amp;lt;unistd.h&amp;gt;     #include &amp;lt;string.h&amp;gt;     #include &amp;lt;stdlib.h&amp;gt;     int main() {         const char* file_path = &amp;#34;/usr/sbin/test_binary&amp;#34;;         const char* hex_strin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68183</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2868 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2868</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2868</guid>
    </item>
  </channel>
</rss>
