<?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 13:00:11 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-07453</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-07453</link>
      <description>bdu:2024-07453</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-07453</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-52906</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-52906</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-52906</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0779 — 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-0779</link>
      <description>certfr-2024-avi-0779</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0779</guid>
    </item>
    <item>
      <title>EUVD-2026-311753</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311753</link>
      <description>EUVD-2026-311753</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311753</guid>
    </item>
    <item>
      <title>fkie_cve-2023-52906</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-52906</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: act_mpls: Fix warning during failed attribute validation&lt;/p&gt;
&lt;p&gt;The &amp;#39;TCA_MPLS_LABEL&amp;#39; attribute is of &amp;#39;NLA_U32&amp;#39; type, but has a
validation type of &amp;#39;NLA_VALIDATE_FUNCTION&amp;#39;. This is an invalid
combination according to the comment above &amp;#39;struct nla_policy&amp;#39;:&lt;/p&gt;
&lt;p&gt;&amp;#34;
Meaning of `validate&amp;#39; field, use via NLA_POLICY_VALIDATE_FN:
   NLA_BINARY           Validation function called for the attribute.
   All other            Unused - but note that it&amp;#39;s a union
&amp;#34;&lt;/p&gt;
&lt;p&gt;This can trigger the warning [1] in nla_get_range_unsigned() when
validation of the attribute fails. Despite being of &amp;#39;NLA_U32&amp;#39; type, the
associated &amp;#39;min&amp;#39;/&amp;#39;max&amp;#39; fields in the policy are negative as they are
aliased by the &amp;#39;validate&amp;#39; field.&lt;/p&gt;
&lt;p&gt;Fix by changing the attribute type to &amp;#39;NLA_BINARY&amp;#39; which is consistent
with the above comment and all other users of NLA_POLICY_VALIDATE_FN().
As a result, move the length validation to the validation function.&lt;/p&gt;
&lt;p&gt;No regressions in MPLS tests:&lt;/p&gt;
&lt;p&gt;# ./tdc.py -f tc-tests/actions/mpls.json
 [...]
 # echo $?
 0&lt;/p&gt;
&lt;p&gt;[1]
WARNING: CPU: 0 PID: 17743 at lib/nlattr.c:118
nla_get_range_unsigned+0x1d8/0x1e0 lib/nlattr.c:117
Modules linked in:
CPU: 0 PID: 17743 Comm: syz-executor.0 Not tainted 6.1.0-rc8 #3
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org 04/01/2014
RIP: 0010:nla_get_range_unsigned+0x1d8/0x1e0 lib/nlattr.c:117
[...]
Call Trace:
 &amp;lt;TASK&amp;gt;
 __netlink_policy_dump_write_attr+0…&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;net/sched: act_mpls: Fix warning during failed attribute validation&lt;/p&gt;
&lt;p&gt;The &amp;#39;TCA_MPLS_LABEL&amp;#39; attribute is of &amp;#39;NLA_U32&amp;#39; type, but has a
validation type of &amp;#39;NLA_VALIDATE_FUNCTION&amp;#39;. This is an invalid
combination according to the comment above &amp;#39;struct nla_policy&amp;#39;:&lt;/p&gt;
&lt;p&gt;&amp;#34;
Meaning of `validate&amp;#39; field, use via NLA_POLICY_VALIDATE_FN:
   NLA_BINARY           Validation function called for the attribute.
   All other            Unused - but note that it&amp;#39;s a union
&amp;#34;&lt;/p&gt;
&lt;p&gt;This can trigger the warning [1] in nla_get_range_unsigned() when
validation of the attribute fails. Despite being of &amp;#39;NLA_U32&amp;#39; type, the
associated &amp;#39;min&amp;#39;/&amp;#39;max&amp;#39; fields in the policy are negative as they are
aliased by the &amp;#39;validate&amp;#39; field.&lt;/p&gt;
&lt;p&gt;Fix by changing the attribute type to &amp;#39;NLA_BINARY&amp;#39; which is consistent
with the above comment and all other users of NLA_POLICY_VALIDATE_FN().
As a result, move the length validation to the validation function.&lt;/p&gt;
&lt;p&gt;No regressions in MPLS tests:&lt;/p&gt;
&lt;p&gt;# ./tdc.py -f tc-tests/actions/mpls.json
 [...]
 # echo $?
 0&lt;/p&gt;
&lt;p&gt;[1]
WARNING: CPU: 0 PID: 17743 at lib/nlattr.c:118
nla_get_range_unsigned+0x1d8/0x1e0 lib/nlattr.c:117
Modules linked in:
CPU: 0 PID: 17743 Comm: syz-executor.0 Not tainted 6.1.0-rc8 #3
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org 04/01/2014
RIP: 0010:nla_get_range_unsigned+0x1d8/0x1e0 lib/nlattr.c:117
[...]
Call Trace:
 &amp;lt;TASK&amp;gt;
 __netlink_policy_dump_write_attr+0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-52906</guid>
    </item>
    <item>
      <title>GHSA-9w85-68h7-c4c7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9w85-68h7-c4c7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: act_mpls: Fix warning during failed attribute validation&lt;/p&gt;
&lt;p&gt;The &amp;#39;TCA_MPLS_LABEL&amp;#39; attribute is of &amp;#39;NLA_U32&amp;#39; type, but has a
validation type of &amp;#39;NLA_VALIDATE_FUNCTION&amp;#39;. This is an invalid
combination according to the comment above &amp;#39;struct nla_policy&amp;#39;:&lt;/p&gt;
&lt;p&gt;&amp;#34;
Meaning of `validate&amp;#39; field, use via NLA_POLICY_VALIDATE_FN:
   NLA_BINARY           Validation function called for the attribute.
   All other            Unused - but note that it&amp;#39;s a union
&amp;#34;&lt;/p&gt;
&lt;p&gt;This can trigger the warning [1] in nla_get_range_unsigned() when
validation of the attribute fails. Despite being of &amp;#39;NLA_U32&amp;#39; type, the
associated &amp;#39;min&amp;#39;/&amp;#39;max&amp;#39; fields in the policy are negative as they are
aliased by the &amp;#39;validate&amp;#39; field.&lt;/p&gt;
&lt;p&gt;Fix by changing the attribute type to &amp;#39;NLA_BINARY&amp;#39; which is consistent
with the above comment and all other users of NLA_POLICY_VALIDATE_FN().
As a result, move the length validation to the validation function.&lt;/p&gt;
&lt;p&gt;No regressions in MPLS tests:&lt;/p&gt;
&lt;p&gt;# ./tdc.py -f tc-tests/actions/mpls.json
 [...]
 # echo $?
 0&lt;/p&gt;
&lt;p&gt;[1]
WARNING: CPU: 0 PID: 17743 at lib/nlattr.c:118
nla_get_range_unsigned+0x1d8/0x1e0 lib/nlattr.c:117
Modules linked in:
CPU: 0 PID: 17743 Comm: syz-executor.0 Not tainted 6.1.0-rc8 #3
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org 04/01/2014
RIP: 0010:nla_get_range_unsigned+0x1d8/0x1e0 lib/nlattr.c:117
[...]
Call Trace:
 &amp;lt;TASK&amp;gt;
 __netlink_policy_dump_write_attr+0…&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;net/sched: act_mpls: Fix warning during failed attribute validation&lt;/p&gt;
&lt;p&gt;The &amp;#39;TCA_MPLS_LABEL&amp;#39; attribute is of &amp;#39;NLA_U32&amp;#39; type, but has a
validation type of &amp;#39;NLA_VALIDATE_FUNCTION&amp;#39;. This is an invalid
combination according to the comment above &amp;#39;struct nla_policy&amp;#39;:&lt;/p&gt;
&lt;p&gt;&amp;#34;
Meaning of `validate&amp;#39; field, use via NLA_POLICY_VALIDATE_FN:
   NLA_BINARY           Validation function called for the attribute.
   All other            Unused - but note that it&amp;#39;s a union
&amp;#34;&lt;/p&gt;
&lt;p&gt;This can trigger the warning [1] in nla_get_range_unsigned() when
validation of the attribute fails. Despite being of &amp;#39;NLA_U32&amp;#39; type, the
associated &amp;#39;min&amp;#39;/&amp;#39;max&amp;#39; fields in the policy are negative as they are
aliased by the &amp;#39;validate&amp;#39; field.&lt;/p&gt;
&lt;p&gt;Fix by changing the attribute type to &amp;#39;NLA_BINARY&amp;#39; which is consistent
with the above comment and all other users of NLA_POLICY_VALIDATE_FN().
As a result, move the length validation to the validation function.&lt;/p&gt;
&lt;p&gt;No regressions in MPLS tests:&lt;/p&gt;
&lt;p&gt;# ./tdc.py -f tc-tests/actions/mpls.json
 [...]
 # echo $?
 0&lt;/p&gt;
&lt;p&gt;[1]
WARNING: CPU: 0 PID: 17743 at lib/nlattr.c:118
nla_get_range_unsigned+0x1d8/0x1e0 lib/nlattr.c:117
Modules linked in:
CPU: 0 PID: 17743 Comm: syz-executor.0 Not tainted 6.1.0-rc8 #3
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org 04/01/2014
RIP: 0010:nla_get_range_unsigned+0x1d8/0x1e0 lib/nlattr.c:117
[...]
Call Trace:
 &amp;lt;TASK&amp;gt;
 __netlink_policy_dump_write_attr+0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9w85-68h7-c4c7</guid>
    </item>
    <item>
      <title>OESA-2024-2106 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2106</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: 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;
ibmvnic: don&amp;amp;apos;t release napi in __ibmvnic_open()&#13;
&#13;
If __ibmvnic_open() encounters an error such as when setting link state,
it calls release_resources() which frees the napi structures needlessly.
Instead, have __ibmvnic_open() only clean up the work it did so far (i.e.
disable napi and irqs) and leave the rest to the callers.&#13;
&#13;
If caller of __ibmvnic_open() is ibmvnic_open(), it should release the
resources immediately. If the caller is do_reset() or do_hard_reset(),
they will release the resources on the next reset.&#13;
&#13;
This fixes following crash that occurred when running the drmgr command
several times to add/remove a vnic interface:&#13;
&#13;
	[102056] ibmvnic 30000003 env3: Disabling rx_scrq[6] irq
	[102056] ibmvnic 30000003 env3: Disabling rx_scrq[7] irq
	[102056] ibmvnic 30000003 env3: Replenished 8 pools
	Kernel attempted to read user page (10) - exploit attempt? (uid: 0)
	BUG: Kernel NULL pointer dereference on read at 0x00000010
	Faulting instruction address: 0xc000000000a3c840
	Oops: Kernel access of bad area, sig: 11 [#1]
	LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA pSeries
	...
	CPU: 9 PID: 102056 Comm: kworker/9:2 Kdump: loaded Not tainted 5.16.0-rc5-autotest-g6441998e2e37 #1
	Workqueue: events_long __ibmvnic_reset [ibmvnic]
	NIP:  c000000000a3c840 LR: c0080000029b5378 CTR: c000000000a3c820
	REGS: c0000000548e37e…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: 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;
ibmvnic: don&amp;amp;apos;t release napi in __ibmvnic_open()&#13;
&#13;
If __ibmvnic_open() encounters an error such as when setting link state,
it calls release_resources() which frees the napi structures needlessly.
Instead, have __ibmvnic_open() only clean up the work it did so far (i.e.
disable napi and irqs) and leave the rest to the callers.&#13;
&#13;
If caller of __ibmvnic_open() is ibmvnic_open(), it should release the
resources immediately. If the caller is do_reset() or do_hard_reset(),
they will release the resources on the next reset.&#13;
&#13;
This fixes following crash that occurred when running the drmgr command
several times to add/remove a vnic interface:&#13;
&#13;
	[102056] ibmvnic 30000003 env3: Disabling rx_scrq[6] irq
	[102056] ibmvnic 30000003 env3: Disabling rx_scrq[7] irq
	[102056] ibmvnic 30000003 env3: Replenished 8 pools
	Kernel attempted to read user page (10) - exploit attempt? (uid: 0)
	BUG: Kernel NULL pointer dereference on read at 0x00000010
	Faulting instruction address: 0xc000000000a3c840
	Oops: Kernel access of bad area, sig: 11 [#1]
	LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA pSeries
	...
	CPU: 9 PID: 102056 Comm: kworker/9:2 Kdump: loaded Not tainted 5.16.0-rc5-autotest-g6441998e2e37 #1
	Workqueue: events_long __ibmvnic_reset [ibmvnic]
	NIP:  c000000000a3c840 LR: c0080000029b5378 CTR: c000000000a3c820
	REGS: c0000000548e37e…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2106</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3190-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3190-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:3190-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-52906</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52906</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.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-ibm-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 119 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/sched: act_mpls: Fix warning during failed attribute validation The &amp;#39;TCA_MPLS_LABEL&amp;#39; attribute is of &amp;#39;NLA_U32&amp;#39; type, but has a validation type of &amp;#39;NLA_VALIDATE_FUNCTION&amp;#39;. This is an invalid combination according to the comment above &amp;#39;struct nla_policy&amp;#39;: &amp;#34; Meaning of `validate&amp;#39; field, use via NLA_POLICY_VALIDATE_FN:    NLA_BINARY           Validation function called for the attribute.    All other            Unused - but note that it&amp;#39;s a union &amp;#34; This can trigger the warning [1] in nla_get_range_unsigned() when validation of the attribute fails. Despite being of &amp;#39;NLA_U32&amp;#39; type, the associated &amp;#39;min&amp;#39;/&amp;#39;max&amp;#39; fields in the policy are negative as they are aliased by the &amp;#39;validate&amp;#39; field. Fix by changing the attribute type to &amp;#39;NLA_BINARY&amp;#39; which is consistent with the above comment and all other users of NLA_POLICY_VALIDATE_FN(). As a result, move the length validation to the validation function. No regressions in MPLS tests:  # ./tdc.py -f tc-tests/actions/mpls.json  [...]  # echo $?  0 [1] WARNING: CPU: 0 PID: 17743 at lib/nlattr.c:118 nla_get_range_unsigned+0x1d8/0x1e0 lib/nlattr.c:117 Modules linked in: CPU: 0 PID: 17743 Comm: syz-executor.0 Not tainted 6.1.0-rc8 #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org 04/01/2014 RIP: 0010:nla_get_range_unsigned+0x1d8/0x1e0 lib/nlattr.c:117 [...] Call Trace:  &amp;lt;TASK&amp;gt;  __netlink_policy_dump_write_attr+0x23d/0x9…&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.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-ibm-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 119 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/sched: act_mpls: Fix warning during failed attribute validation The &amp;#39;TCA_MPLS_LABEL&amp;#39; attribute is of &amp;#39;NLA_U32&amp;#39; type, but has a validation type of &amp;#39;NLA_VALIDATE_FUNCTION&amp;#39;. This is an invalid combination according to the comment above &amp;#39;struct nla_policy&amp;#39;: &amp;#34; Meaning of `validate&amp;#39; field, use via NLA_POLICY_VALIDATE_FN:    NLA_BINARY           Validation function called for the attribute.    All other            Unused - but note that it&amp;#39;s a union &amp;#34; This can trigger the warning [1] in nla_get_range_unsigned() when validation of the attribute fails. Despite being of &amp;#39;NLA_U32&amp;#39; type, the associated &amp;#39;min&amp;#39;/&amp;#39;max&amp;#39; fields in the policy are negative as they are aliased by the &amp;#39;validate&amp;#39; field. Fix by changing the attribute type to &amp;#39;NLA_BINARY&amp;#39; which is consistent with the above comment and all other users of NLA_POLICY_VALIDATE_FN(). As a result, move the length validation to the validation function. No regressions in MPLS tests:  # ./tdc.py -f tc-tests/actions/mpls.json  [...]  # echo $?  0 [1] WARNING: CPU: 0 PID: 17743 at lib/nlattr.c:118 nla_get_range_unsigned+0x1d8/0x1e0 lib/nlattr.c:117 Modules linked in: CPU: 0 PID: 17743 Comm: syz-executor.0 Not tainted 6.1.0-rc8 #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org 04/01/2014 RIP: 0010:nla_get_range_unsigned+0x1d8/0x1e0 lib/nlattr.c:117 [...] Call Trace:  &amp;lt;TASK&amp;gt;  __netlink_policy_dump_write_attr+0x23d/0x9…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52906</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1888 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1888</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder einen unspezifischen 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 zu erzeugen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1888</guid>
    </item>
  </channel>
</rss>
