<?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 16:50:48 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:68531 — Important: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2026:68531</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.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: ipvlan: Make the addrs_lock be per port (CVE-2026-23103)
  * kernel: xfrm: hold dev ref until after transport_finish NF_HOOK (CVE-2026-31663)
  * kernel: netfilter: nf_conntrack_h323: fix OOB read in decode_choice() (CVE-2026-43233)
  * kernel: ipv6: prevent possible UaF in addrconf_permanent_addr() (CVE-2026-43339)
  * kernel: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP (CVE-2026-46266)
  * kernel: flow_dissector: do not dissect PPPoE PFC frames (CVE-2026-46306)
  * kernel: netfilter: xt_policy: fix strict mode inbound policy matching (CVE-2026-52920)
  * kernel: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (CVE-2026-53075)
  * kernel: ipv6: sit: reload inner IPv6 header after GSO offloads (CVE-2026-53228)
  * kernel: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN (CVE-2026-53176)
  * kernel: netfilter: require Ethernet MAC header before using eth_hdr() (CVE-2026-53131)
  * kernel: netfilter: conntrack_irc: fix possible out-of-bounds read (CVE-2026-53268)
  * kernel: xfrm: policy: fix use-after-free on inexact bin in xfrm_policy_bysel_ctx() (CVE-2026-53239)
  * kernel: ALSA: timer: Fix UAF at snd_timer_user_params() (CVE-2026-53192)
  * kernel: net: guard timestamp cmsgs to real error queue skbs (CVE-2026-53223)
  * kernel: ipv6: mcast: Fix use-after-free when processing MLD queries (CVE-2026-53275)
  * kern…&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.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: ipvlan: Make the addrs_lock be per port (CVE-2026-23103)
  * kernel: xfrm: hold dev ref until after transport_finish NF_HOOK (CVE-2026-31663)
  * kernel: netfilter: nf_conntrack_h323: fix OOB read in decode_choice() (CVE-2026-43233)
  * kernel: ipv6: prevent possible UaF in addrconf_permanent_addr() (CVE-2026-43339)
  * kernel: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP (CVE-2026-46266)
  * kernel: flow_dissector: do not dissect PPPoE PFC frames (CVE-2026-46306)
  * kernel: netfilter: xt_policy: fix strict mode inbound policy matching (CVE-2026-52920)
  * kernel: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (CVE-2026-53075)
  * kernel: ipv6: sit: reload inner IPv6 header after GSO offloads (CVE-2026-53228)
  * kernel: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN (CVE-2026-53176)
  * kernel: netfilter: require Ethernet MAC header before using eth_hdr() (CVE-2026-53131)
  * kernel: netfilter: conntrack_irc: fix possible out-of-bounds read (CVE-2026-53268)
  * kernel: xfrm: policy: fix use-after-free on inexact bin in xfrm_policy_bysel_ctx() (CVE-2026-53239)
  * kernel: ALSA: timer: Fix UAF at snd_timer_user_params() (CVE-2026-53192)
  * kernel: net: guard timestamp cmsgs to real error queue skbs (CVE-2026-53223)
  * kernel: ipv6: mcast: Fix use-after-free when processing MLD queries (CVE-2026-53275)
  * kern…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2026:68531</guid>
    </item>
    <item>
      <title>bdu:2026-11576</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-11576</link>
      <description>bdu:2026-11576</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-11576</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-23103</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-23103</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-2026-23103</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0166 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</link>
      <description>certfr-2026-avi-0166</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</guid>
    </item>
    <item>
      <title>EUVD-2026-364662</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-364662</link>
      <description>EUVD-2026-364662</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-364662</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23103</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23103</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipvlan: Make the addrs_lock be per port&lt;/p&gt;
&lt;p&gt;Make the addrs_lock be per port, not per ipvlan dev.&lt;/p&gt;
&lt;p&gt;Initial code seems to be written in the assumption,
that any address change must occur under RTNL.
But it is not so for the case of IPv6. So&lt;/p&gt;
&lt;p&gt;1) Introduce per-port addrs_lock.&lt;/p&gt;
&lt;p&gt;2) It was needed to fix places where it was forgotten
to take lock (ipvlan_open/ipvlan_close)&lt;/p&gt;
&lt;p&gt;This appears to be a very minor problem though.
Since it&amp;#39;s highly unlikely that ipvlan_add_addr() will
be called on 2 CPU simultaneously. But nevertheless,
this could cause:&lt;/p&gt;
&lt;p&gt;1) False-negative of ipvlan_addr_busy(): one interface
iterated through all port-&amp;gt;ipvlans + ipvlan-&amp;gt;addrs
under some ipvlan spinlock, and another added IP
under its own lock. Though this is only possible
for IPv6, since looks like only ipvlan_addr6_event() can be
called without rtnl_lock.&lt;/p&gt;
&lt;p&gt;2) Race since ipvlan_ht_addr_add(port) is called under
different ipvlan-&amp;gt;addrs_lock locks&lt;/p&gt;
&lt;p&gt;This should not affect performance, since add/remove IP
is a rare situation and spinlock is not taken on fast
paths.&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;ipvlan: Make the addrs_lock be per port&lt;/p&gt;
&lt;p&gt;Make the addrs_lock be per port, not per ipvlan dev.&lt;/p&gt;
&lt;p&gt;Initial code seems to be written in the assumption,
that any address change must occur under RTNL.
But it is not so for the case of IPv6. So&lt;/p&gt;
&lt;p&gt;1) Introduce per-port addrs_lock.&lt;/p&gt;
&lt;p&gt;2) It was needed to fix places where it was forgotten
to take lock (ipvlan_open/ipvlan_close)&lt;/p&gt;
&lt;p&gt;This appears to be a very minor problem though.
Since it&amp;#39;s highly unlikely that ipvlan_add_addr() will
be called on 2 CPU simultaneously. But nevertheless,
this could cause:&lt;/p&gt;
&lt;p&gt;1) False-negative of ipvlan_addr_busy(): one interface
iterated through all port-&amp;gt;ipvlans + ipvlan-&amp;gt;addrs
under some ipvlan spinlock, and another added IP
under its own lock. Though this is only possible
for IPv6, since looks like only ipvlan_addr6_event() can be
called without rtnl_lock.&lt;/p&gt;
&lt;p&gt;2) Race since ipvlan_ht_addr_add(port) is called under
different ipvlan-&amp;gt;addrs_lock locks&lt;/p&gt;
&lt;p&gt;This should not affect performance, since add/remove IP
is a rare situation and spinlock is not taken on fast
paths.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23103</guid>
    </item>
    <item>
      <title>GHSA-ghmm-m363-9645</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ghmm-m363-9645</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipvlan: Make the addrs_lock be per port&lt;/p&gt;
&lt;p&gt;Make the addrs_lock be per port, not per ipvlan dev.&lt;/p&gt;
&lt;p&gt;Initial code seems to be written in the assumption,
that any address change must occur under RTNL.
But it is not so for the case of IPv6. So&lt;/p&gt;
&lt;p&gt;1) Introduce per-port addrs_lock.&lt;/p&gt;
&lt;p&gt;2) It was needed to fix places where it was forgotten
to take lock (ipvlan_open/ipvlan_close)&lt;/p&gt;
&lt;p&gt;This appears to be a very minor problem though.
Since it&amp;#39;s highly unlikely that ipvlan_add_addr() will
be called on 2 CPU simultaneously. But nevertheless,
this could cause:&lt;/p&gt;
&lt;p&gt;1) False-negative of ipvlan_addr_busy(): one interface
iterated through all port-&amp;gt;ipvlans + ipvlan-&amp;gt;addrs
under some ipvlan spinlock, and another added IP
under its own lock. Though this is only possible
for IPv6, since looks like only ipvlan_addr6_event() can be
called without rtnl_lock.&lt;/p&gt;
&lt;p&gt;2) Race since ipvlan_ht_addr_add(port) is called under
different ipvlan-&amp;gt;addrs_lock locks&lt;/p&gt;
&lt;p&gt;This should not affect performance, since add/remove IP
is a rare situation and spinlock is not taken on fast
paths.&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;ipvlan: Make the addrs_lock be per port&lt;/p&gt;
&lt;p&gt;Make the addrs_lock be per port, not per ipvlan dev.&lt;/p&gt;
&lt;p&gt;Initial code seems to be written in the assumption,
that any address change must occur under RTNL.
But it is not so for the case of IPv6. So&lt;/p&gt;
&lt;p&gt;1) Introduce per-port addrs_lock.&lt;/p&gt;
&lt;p&gt;2) It was needed to fix places where it was forgotten
to take lock (ipvlan_open/ipvlan_close)&lt;/p&gt;
&lt;p&gt;This appears to be a very minor problem though.
Since it&amp;#39;s highly unlikely that ipvlan_add_addr() will
be called on 2 CPU simultaneously. But nevertheless,
this could cause:&lt;/p&gt;
&lt;p&gt;1) False-negative of ipvlan_addr_busy(): one interface
iterated through all port-&amp;gt;ipvlans + ipvlan-&amp;gt;addrs
under some ipvlan spinlock, and another added IP
under its own lock. Though this is only possible
for IPv6, since looks like only ipvlan_addr6_event() can be
called without rtnl_lock.&lt;/p&gt;
&lt;p&gt;2) Race since ipvlan_ht_addr_add(port) is called under
different ipvlan-&amp;gt;addrs_lock locks&lt;/p&gt;
&lt;p&gt;This should not affect performance, since add/remove IP
is a rare situation and spinlock is not taken on fast
paths.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ghmm-m363-9645</guid>
    </item>
    <item>
      <title>ICSA-26-209-04 — Siemens SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-26-209-04</link>
      <description>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens is preparing fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens is preparing fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-26-209-04</guid>
    </item>
    <item>
      <title>OESA-2026-1760 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-1760</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;iommu/s390: Implement blocking domain&lt;/p&gt;
&lt;p&gt;This fixes a crash when surprise hot-unplugging a PCI device. This crash
happens because during hot-unplug __iommu_group_set_domain_nofail()
attaching the default domain fails when the platform no longer
recognizes the device as it has already been removed and we end up with
a NULL domain pointer and UAF. This is exactly the case referred to in
the second comment in __iommu_device_set_domain() and just as stated
there if we can instead attach the blocking domain the UAF is prevented
as this can handle the already removed device. Implement the blocking
domain to use this handling.  With this change, the crash is fixed but
we still hit a warning attempting to change DMA ownership on a blocked
device.(CVE-2024-53232)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu: Fix two issues in iommu_copy_struct_from_user()&lt;/p&gt;
&lt;p&gt;In the review for iommu_copy_struct_to_user() helper, Matt pointed out that
a NULL pointer should be rejected prior to dereferencing it:
https://lore.kernel.org/all/(CVE-2025-37900)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: client: Avoid race in open_cached_dir with lease breaks&lt;/p&gt;
&lt;p&gt;A pre-existing valid cfid returned from find_or_create_cached_dir might
race with a lease break, meaning open_cached_dir doesn&amp;amp;apos;t consider it
valid,…&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;iommu/s390: Implement blocking domain&lt;/p&gt;
&lt;p&gt;This fixes a crash when surprise hot-unplugging a PCI device. This crash
happens because during hot-unplug __iommu_group_set_domain_nofail()
attaching the default domain fails when the platform no longer
recognizes the device as it has already been removed and we end up with
a NULL domain pointer and UAF. This is exactly the case referred to in
the second comment in __iommu_device_set_domain() and just as stated
there if we can instead attach the blocking domain the UAF is prevented
as this can handle the already removed device. Implement the blocking
domain to use this handling.  With this change, the crash is fixed but
we still hit a warning attempting to change DMA ownership on a blocked
device.(CVE-2024-53232)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu: Fix two issues in iommu_copy_struct_from_user()&lt;/p&gt;
&lt;p&gt;In the review for iommu_copy_struct_to_user() helper, Matt pointed out that
a NULL pointer should be rejected prior to dereferencing it:
https://lore.kernel.org/all/(CVE-2025-37900)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: client: Avoid race in open_cached_dir with lease breaks&lt;/p&gt;
&lt;p&gt;A pre-existing valid cfid returned from find_or_create_cached_dir might
race with a lease break, meaning open_cached_dir doesn&amp;amp;apos;t consider it
valid,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-1760</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20572-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20572-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/opensuse-su-2026:20572-1</guid>
    </item>
    <item>
      <title>RHSA-2026:68532 — Red Hat Security Advisory: kernel-rt security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:68532</link>
      <description>&lt;p&gt;kernel: ipvlan: Make the addrs_lock be per port kernel: xfrm: hold dev ref until after transport_finish NF_HOOK kernel: netfilter: nf_conntrack_h323: fix OOB read in decode_choice() kernel: ipv6: prevent possible UaF in addrconf_permanent_addr() kernel: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP kernel: flow_dissector: do not dissect PPPoE PFC frames kernel: netfilter: xt_policy: fix strict mode inbound policy matching kernel: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls kernel: netfilter: require Ethernet MAC header before using eth_hdr() kernel: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN kernel: ALSA: timer: Fix UAF at snd_timer_user_params() kernel: net: guard timestamp cmsgs to real error queue skbs kernel: ipv6: sit: reload inner IPv6 header after GSO offloads kernel: xfrm: policy: fix use-after-free on inexact bin in xfrm_policy_bysel_ctx() kernel: netfilter: conntrack_irc: fix possible out-of-bounds read kernel: ipv6: mcast: Fix use-after-free when processing MLD queries kernel: ip6: vti: Use ip6_tnl.net in vti6_changelink() kernel: xfrm: input: hold netns during deferred transport reinjection kernel: ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate() kernel: ipv4: free net-&amp;gt;ipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table() kernel: Linux kernel SLIP: Out-of-bounds write due to race condition during MTU change kernel: xfrm: fix stale skb-&amp;gt;prev after async crypto steals a GSO segment kernel: net: qrt…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: ipvlan: Make the addrs_lock be per port kernel: xfrm: hold dev ref until after transport_finish NF_HOOK kernel: netfilter: nf_conntrack_h323: fix OOB read in decode_choice() kernel: ipv6: prevent possible UaF in addrconf_permanent_addr() kernel: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP kernel: flow_dissector: do not dissect PPPoE PFC frames kernel: netfilter: xt_policy: fix strict mode inbound policy matching kernel: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls kernel: netfilter: require Ethernet MAC header before using eth_hdr() kernel: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN kernel: ALSA: timer: Fix UAF at snd_timer_user_params() kernel: net: guard timestamp cmsgs to real error queue skbs kernel: ipv6: sit: reload inner IPv6 header after GSO offloads kernel: xfrm: policy: fix use-after-free on inexact bin in xfrm_policy_bysel_ctx() kernel: netfilter: conntrack_irc: fix possible out-of-bounds read kernel: ipv6: mcast: Fix use-after-free when processing MLD queries kernel: ip6: vti: Use ip6_tnl.net in vti6_changelink() kernel: xfrm: input: hold netns during deferred transport reinjection kernel: ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate() kernel: ipv4: free net-&amp;gt;ipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table() kernel: Linux kernel SLIP: Out-of-bounds write due to race condition during MTU change kernel: xfrm: fix stale skb-&amp;gt;prev after async crypto steals a GSO segment kernel: net: qrt…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:68532</guid>
    </item>
    <item>
      <title>RLSA-2026:68531 — Important: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rlsa-2026:68531</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: 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: ipvlan: Make the addrs_lock be per port (CVE-2026-23103)&lt;/p&gt;
&lt;p&gt;* kernel: xfrm: hold dev ref until after transport_finish NF_HOOK (CVE-2026-31663)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: nf_conntrack_h323: fix OOB read in decode_choice() (CVE-2026-43233)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: prevent possible UaF in addrconf_permanent_addr() (CVE-2026-43339)&lt;/p&gt;
&lt;p&gt;* kernel: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP (CVE-2026-46266)&lt;/p&gt;
&lt;p&gt;* kernel: flow_dissector: do not dissect PPPoE PFC frames (CVE-2026-46306)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: xt_policy: fix strict mode inbound policy matching (CVE-2026-52920)&lt;/p&gt;
&lt;p&gt;* kernel: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (CVE-2026-53075)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: sit: reload inner IPv6 header after GSO offloads (CVE-2026-53228)&lt;/p&gt;
&lt;p&gt;* kernel: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN (CVE-2026-53176)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: require Ethernet MAC header before using eth_hdr() (CVE-2026-53131)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: conntrack_irc: fix possible out-of-bounds read (CVE-2026-53268)&lt;/p&gt;
&lt;p&gt;* kernel: xfrm: policy: fix use-after-free on inexact bin in xfrm_policy_bysel_ctx() (CVE-2026-53239)&lt;/p&gt;
&lt;p&gt;* kernel: ALSA: timer: Fix UAF at snd_timer_user_params() (CVE-2026-53192)&lt;/p&gt;
&lt;p&gt;* kernel: net: guard timestamp cmsgs to real error queue skbs (CVE-2026-53223)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: mcast: Fix use-after-free when processing MLD queries (CVE-2026-53275)&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: free net-&amp;gt;ip…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: 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: ipvlan: Make the addrs_lock be per port (CVE-2026-23103)&lt;/p&gt;
&lt;p&gt;* kernel: xfrm: hold dev ref until after transport_finish NF_HOOK (CVE-2026-31663)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: nf_conntrack_h323: fix OOB read in decode_choice() (CVE-2026-43233)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: prevent possible UaF in addrconf_permanent_addr() (CVE-2026-43339)&lt;/p&gt;
&lt;p&gt;* kernel: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP (CVE-2026-46266)&lt;/p&gt;
&lt;p&gt;* kernel: flow_dissector: do not dissect PPPoE PFC frames (CVE-2026-46306)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: xt_policy: fix strict mode inbound policy matching (CVE-2026-52920)&lt;/p&gt;
&lt;p&gt;* kernel: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (CVE-2026-53075)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: sit: reload inner IPv6 header after GSO offloads (CVE-2026-53228)&lt;/p&gt;
&lt;p&gt;* kernel: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN (CVE-2026-53176)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: require Ethernet MAC header before using eth_hdr() (CVE-2026-53131)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: conntrack_irc: fix possible out-of-bounds read (CVE-2026-53268)&lt;/p&gt;
&lt;p&gt;* kernel: xfrm: policy: fix use-after-free on inexact bin in xfrm_policy_bysel_ctx() (CVE-2026-53239)&lt;/p&gt;
&lt;p&gt;* kernel: ALSA: timer: Fix UAF at snd_timer_user_params() (CVE-2026-53192)&lt;/p&gt;
&lt;p&gt;* kernel: net: guard timestamp cmsgs to real error queue skbs (CVE-2026-53223)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: mcast: Fix use-after-free when processing MLD queries (CVE-2026-53275)&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: free net-&amp;gt;ip…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rlsa-2026:68531</guid>
    </item>
    <item>
      <title>SSA-019113 — SSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6</title>
      <link>https://cve.radiocsirt.org/vuln/ssa-019113</link>
      <description>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ssa-019113</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:1342-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:1342-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:1342-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23103</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23103</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 224 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipvlan: Make the addrs_lock be per port Make the addrs_lock be per port, not per ipvlan dev. Initial code seems to be written in the assumption, that any address change must occur under RTNL. But it is not so for the case of IPv6. So 1) Introduce per-port addrs_lock. 2) It was needed to fix places where it was forgotten to take lock (ipvlan_open/ipvlan_close) This appears to be a very minor problem though. Since it&amp;#39;s highly unlikely that ipvlan_add_addr() will be called on 2 CPU simultaneously. But nevertheless, this could cause: 1) False-negative of ipvlan_addr_busy(): one interface iterated through all port-&amp;gt;ipvlans + ipvlan-&amp;gt;addrs under some ipvlan spinlock, and another added IP under its own lock. Though this is only possible for IPv6, since looks like only ipvlan_addr6_event() can be called without rtnl_lock. 2) Race since ipvlan_ht_addr_add(port) is called under different ipvlan-&amp;gt;addrs_lock locks This should not affect performance, since add/remove IP is a rare situation and spinlock is not taken on fast paths.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 224 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipvlan: Make the addrs_lock be per port Make the addrs_lock be per port, not per ipvlan dev. Initial code seems to be written in the assumption, that any address change must occur under RTNL. But it is not so for the case of IPv6. So 1) Introduce per-port addrs_lock. 2) It was needed to fix places where it was forgotten to take lock (ipvlan_open/ipvlan_close) This appears to be a very minor problem though. Since it&amp;#39;s highly unlikely that ipvlan_add_addr() will be called on 2 CPU simultaneously. But nevertheless, this could cause: 1) False-negative of ipvlan_addr_busy(): one interface iterated through all port-&amp;gt;ipvlans + ipvlan-&amp;gt;addrs under some ipvlan spinlock, and another added IP under its own lock. Though this is only possible for IPv6, since looks like only ipvlan_addr6_event() can be called without rtnl_lock. 2) Race since ipvlan_ht_addr_add(port) is called under different ipvlan-&amp;gt;addrs_lock locks This should not affect performance, since add/remove IP is a rare situation and spinlock is not taken on fast paths.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23103</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0324 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0324</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-2026-0324</guid>
    </item>
  </channel>
</rss>
