<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 18:46:08 +0000</lastBuildDate>
    <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://vulnerability.circl.lu/vuln/CERTFR-2026-AVI-0108</link>
      <description>CERTFR-2026-AVI-0108</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/CERTFR-2026-AVI-0108</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53843</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2023-53843</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: 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:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2023-53843</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53843</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2023-53843</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: openvswitch: reject negative ifindex&lt;/p&gt;
&lt;p&gt;Recent changes in net-next (commit 759ab1edb56c (&amp;#34;net: store netdevs
in an xarray&amp;#34;)) refactored the handling of pre-assigned ifindexes
and let syzbot surface a latent problem in ovs. ovs does not validate
ifindex, making it possible to create netdev ports with negative
ifindex values. It&amp;#39;s easy to repro with YNL:&lt;/p&gt;
&lt;p&gt;$ ./cli.py --spec netlink/specs/ovs_datapath.yaml \
         --do new \
	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: 1, &amp;#34;name&amp;#34;:&amp;#34;my-dp&amp;#34;}&amp;#39;
$ ./cli.py --spec netlink/specs/ovs_vport.yaml \
	 --do new \
	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: &amp;#34;00000001&amp;#34;, &amp;#34;name&amp;#34;: &amp;#34;some-port0&amp;#34;, &amp;#34;dp-ifindex&amp;#34;:3,&amp;#34;ifindex&amp;#34;:4294901760,&amp;#34;type&amp;#34;:2}&amp;#39;&lt;/p&gt;
&lt;p&gt;$ ip link show
-65536: some-port0: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 7a:48:21:ad:0b:fb brd ff:ff:ff:ff:ff:ff
...&lt;/p&gt;
&lt;p&gt;Validate the inputs. Now the second command correctly returns:&lt;/p&gt;
&lt;p&gt;$ ./cli.py --spec netlink/specs/ovs_vport.yaml \
	 --do new \
	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: &amp;#34;00000001&amp;#34;, &amp;#34;name&amp;#34;: &amp;#34;some-port0&amp;#34;, &amp;#34;dp-ifindex&amp;#34;:3,&amp;#34;ifindex&amp;#34;:4294901760,&amp;#34;type&amp;#34;:2}&amp;#39;&lt;/p&gt;
&lt;p&gt;lib.ynl.NlError: Netlink error: Numerical result out of range
nl_len = 108 (92) nl_flags = 0x300 nl_type = 2
	error: -34	extack: {&amp;#39;msg&amp;#39;: &amp;#39;integer out of range&amp;#39;, &amp;#39;unknown&amp;#39;: [[type:4 len:36] b&amp;#39;\x0c\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x0c\x00\x03\x00\xff\xff\xff\x7f\x00\x00\x00\x00\x08\x00\x01\x00\x08\x00\x00\x00&amp;#39;], &amp;#39;bad-attr&amp;#39;: &amp;#39;.ifindex&amp;#39;}&lt;/p&gt;
&lt;p&gt;Accept 0 since it u…&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: openvswitch: reject negative ifindex&lt;/p&gt;
&lt;p&gt;Recent changes in net-next (commit 759ab1edb56c (&amp;#34;net: store netdevs
in an xarray&amp;#34;)) refactored the handling of pre-assigned ifindexes
and let syzbot surface a latent problem in ovs. ovs does not validate
ifindex, making it possible to create netdev ports with negative
ifindex values. It&amp;#39;s easy to repro with YNL:&lt;/p&gt;
&lt;p&gt;$ ./cli.py --spec netlink/specs/ovs_datapath.yaml \
         --do new \
	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: 1, &amp;#34;name&amp;#34;:&amp;#34;my-dp&amp;#34;}&amp;#39;
$ ./cli.py --spec netlink/specs/ovs_vport.yaml \
	 --do new \
	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: &amp;#34;00000001&amp;#34;, &amp;#34;name&amp;#34;: &amp;#34;some-port0&amp;#34;, &amp;#34;dp-ifindex&amp;#34;:3,&amp;#34;ifindex&amp;#34;:4294901760,&amp;#34;type&amp;#34;:2}&amp;#39;&lt;/p&gt;
&lt;p&gt;$ ip link show
-65536: some-port0: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 7a:48:21:ad:0b:fb brd ff:ff:ff:ff:ff:ff
...&lt;/p&gt;
&lt;p&gt;Validate the inputs. Now the second command correctly returns:&lt;/p&gt;
&lt;p&gt;$ ./cli.py --spec netlink/specs/ovs_vport.yaml \
	 --do new \
	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: &amp;#34;00000001&amp;#34;, &amp;#34;name&amp;#34;: &amp;#34;some-port0&amp;#34;, &amp;#34;dp-ifindex&amp;#34;:3,&amp;#34;ifindex&amp;#34;:4294901760,&amp;#34;type&amp;#34;:2}&amp;#39;&lt;/p&gt;
&lt;p&gt;lib.ynl.NlError: Netlink error: Numerical result out of range
nl_len = 108 (92) nl_flags = 0x300 nl_type = 2
	error: -34	extack: {&amp;#39;msg&amp;#39;: &amp;#39;integer out of range&amp;#39;, &amp;#39;unknown&amp;#39;: [[type:4 len:36] b&amp;#39;\x0c\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x0c\x00\x03\x00\xff\xff\xff\x7f\x00\x00\x00\x00\x08\x00\x01\x00\x08\x00\x00\x00&amp;#39;], &amp;#39;bad-attr&amp;#39;: &amp;#39;.ifindex&amp;#39;}&lt;/p&gt;
&lt;p&gt;Accept 0 since it u…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2023-53843</guid>
    </item>
    <item>
      <title>GHSA-26x8-4cm5-whjx</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-26x8-4cm5-whjx</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: openvswitch: reject negative ifindex&lt;/p&gt;
&lt;p&gt;Recent changes in net-next (commit 759ab1edb56c (&amp;#34;net: store netdevs
in an xarray&amp;#34;)) refactored the handling of pre-assigned ifindexes
and let syzbot surface a latent problem in ovs. ovs does not validate
ifindex, making it possible to create netdev ports with negative
ifindex values. It&amp;#39;s easy to repro with YNL:&lt;/p&gt;
&lt;p&gt;$ ./cli.py --spec netlink/specs/ovs_datapath.yaml \
         --do new \
	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: 1, &amp;#34;name&amp;#34;:&amp;#34;my-dp&amp;#34;}&amp;#39;
$ ./cli.py --spec netlink/specs/ovs_vport.yaml \
	 --do new \
	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: &amp;#34;00000001&amp;#34;, &amp;#34;name&amp;#34;: &amp;#34;some-port0&amp;#34;, &amp;#34;dp-ifindex&amp;#34;:3,&amp;#34;ifindex&amp;#34;:4294901760,&amp;#34;type&amp;#34;:2}&amp;#39;&lt;/p&gt;
&lt;p&gt;$ ip link show
-65536: some-port0: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 7a:48:21:ad:0b:fb brd ff:ff:ff:ff:ff:ff
...&lt;/p&gt;
&lt;p&gt;Validate the inputs. Now the second command correctly returns:&lt;/p&gt;
&lt;p&gt;$ ./cli.py --spec netlink/specs/ovs_vport.yaml \
	 --do new \
	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: &amp;#34;00000001&amp;#34;, &amp;#34;name&amp;#34;: &amp;#34;some-port0&amp;#34;, &amp;#34;dp-ifindex&amp;#34;:3,&amp;#34;ifindex&amp;#34;:4294901760,&amp;#34;type&amp;#34;:2}&amp;#39;&lt;/p&gt;
&lt;p&gt;lib.ynl.NlError: Netlink error: Numerical result out of range
nl_len = 108 (92) nl_flags = 0x300 nl_type = 2
	error: -34	extack: {&amp;#39;msg&amp;#39;: &amp;#39;integer out of range&amp;#39;, &amp;#39;unknown&amp;#39;: [[type:4 len:36] b&amp;#39;\x0c\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x0c\x00\x03\x00\xff\xff\xff\x7f\x00\x00\x00\x00\x08\x00\x01\x00\x08\x00\x00\x00&amp;#39;], &amp;#39;bad-attr&amp;#39;: &amp;#39;.ifindex&amp;#39;}&lt;/p&gt;
&lt;p&gt;Accept 0 since it u…&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: openvswitch: reject negative ifindex&lt;/p&gt;
&lt;p&gt;Recent changes in net-next (commit 759ab1edb56c (&amp;#34;net: store netdevs
in an xarray&amp;#34;)) refactored the handling of pre-assigned ifindexes
and let syzbot surface a latent problem in ovs. ovs does not validate
ifindex, making it possible to create netdev ports with negative
ifindex values. It&amp;#39;s easy to repro with YNL:&lt;/p&gt;
&lt;p&gt;$ ./cli.py --spec netlink/specs/ovs_datapath.yaml \
         --do new \
	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: 1, &amp;#34;name&amp;#34;:&amp;#34;my-dp&amp;#34;}&amp;#39;
$ ./cli.py --spec netlink/specs/ovs_vport.yaml \
	 --do new \
	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: &amp;#34;00000001&amp;#34;, &amp;#34;name&amp;#34;: &amp;#34;some-port0&amp;#34;, &amp;#34;dp-ifindex&amp;#34;:3,&amp;#34;ifindex&amp;#34;:4294901760,&amp;#34;type&amp;#34;:2}&amp;#39;&lt;/p&gt;
&lt;p&gt;$ ip link show
-65536: some-port0: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 7a:48:21:ad:0b:fb brd ff:ff:ff:ff:ff:ff
...&lt;/p&gt;
&lt;p&gt;Validate the inputs. Now the second command correctly returns:&lt;/p&gt;
&lt;p&gt;$ ./cli.py --spec netlink/specs/ovs_vport.yaml \
	 --do new \
	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: &amp;#34;00000001&amp;#34;, &amp;#34;name&amp;#34;: &amp;#34;some-port0&amp;#34;, &amp;#34;dp-ifindex&amp;#34;:3,&amp;#34;ifindex&amp;#34;:4294901760,&amp;#34;type&amp;#34;:2}&amp;#39;&lt;/p&gt;
&lt;p&gt;lib.ynl.NlError: Netlink error: Numerical result out of range
nl_len = 108 (92) nl_flags = 0x300 nl_type = 2
	error: -34	extack: {&amp;#39;msg&amp;#39;: &amp;#39;integer out of range&amp;#39;, &amp;#39;unknown&amp;#39;: [[type:4 len:36] b&amp;#39;\x0c\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x0c\x00\x03\x00\xff\xff\xff\x7f\x00\x00\x00\x00\x08\x00\x01\x00\x08\x00\x00\x00&amp;#39;], &amp;#39;bad-attr&amp;#39;: &amp;#39;.ifindex&amp;#39;}&lt;/p&gt;
&lt;p&gt;Accept 0 since it u…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-26x8-4cm5-whjx</guid>
    </item>
    <item>
      <title>RHSA-2024:2394 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2024:2394</link>
      <description>&lt;p&gt;kernel: Bluetooth BR/EDR PIN Pairing procedure is vulnerable to an impersonation attack kernel: ovl: fix warning in ovl_create_real() kernel: memcg does not limit the number of POSIX file locks allowing memory exhaustion kernel: vmwgfx: NULL pointer dereference in vmw_cmd_dx_define_query kernel: integer overflow in l2cap_config_req() in net/bluetooth/l2cap_core.c kernel: i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() kernel: Bluetooth: L2CAP: Fix u8 overflow kernel: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() kernel: tracing: Fix sleeping function called from invalid context on RT kernel kernel: net: mdio: unexport __init-annotated mdio_bus_init() kernel: arm64: ftrace: consistently handle PLTs. kernel: mm/uffd: fix pte marker when fork() without fork event kernel: Bluetooth: Fix a buffer overflow in mgmt_mesh_add() kernel: tty: n_gsm: add sanity check for gsm-&amp;gt;receive in gsm_receive_buf() kernel: ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead kernel: tee: add overflow check in register_shm_helper() kernel: tty: n_gsm: fix deadlock and link starvation in outgoing data path kernel: PM: hibernate: defer device probing when resuming from hibernation kernel: ext4: don&amp;#39;t allow journal inode to have encrypt flag kernel: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline kernel: erofs: fix order &amp;gt;= MAX_ORDER warning due to crafted negative i_size kernel: perf/x86/intel/uncore: F…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: Bluetooth BR/EDR PIN Pairing procedure is vulnerable to an impersonation attack kernel: ovl: fix warning in ovl_create_real() kernel: memcg does not limit the number of POSIX file locks allowing memory exhaustion kernel: vmwgfx: NULL pointer dereference in vmw_cmd_dx_define_query kernel: integer overflow in l2cap_config_req() in net/bluetooth/l2cap_core.c kernel: i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() kernel: Bluetooth: L2CAP: Fix u8 overflow kernel: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() kernel: tracing: Fix sleeping function called from invalid context on RT kernel kernel: net: mdio: unexport __init-annotated mdio_bus_init() kernel: arm64: ftrace: consistently handle PLTs. kernel: mm/uffd: fix pte marker when fork() without fork event kernel: Bluetooth: Fix a buffer overflow in mgmt_mesh_add() kernel: tty: n_gsm: add sanity check for gsm-&amp;gt;receive in gsm_receive_buf() kernel: ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead kernel: tee: add overflow check in register_shm_helper() kernel: tty: n_gsm: fix deadlock and link starvation in outgoing data path kernel: PM: hibernate: defer device probing when resuming from hibernation kernel: ext4: don&amp;#39;t allow journal inode to have encrypt flag kernel: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline kernel: erofs: fix order &amp;gt;= MAX_ORDER warning due to crafted negative i_size kernel: perf/x86/intel/uncore: F…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2024:2394</guid>
    </item>
    <item>
      <title>RXSA-2024:3138 — Moderate: kernel security, bug fix, and enhancement update</title>
      <link>https://vulnerability.circl.lu/vuln/rxsa-2024:3138</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;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;
&lt;p&gt;Additional Changes:&lt;/p&gt;
&lt;p&gt;For detailed information on changes in this release, see the Rocky Linux SIG Cloud 8.10 Release Notes linked from the References section.&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;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;
&lt;p&gt;Additional Changes:&lt;/p&gt;
&lt;p&gt;For detailed information on changes in this release, see the Rocky Linux SIG Cloud 8.10 Release Notes linked from the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rxsa-2024:3138</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0278-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/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://vulnerability.circl.lu/vuln/suse-su-2026:0278-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53843</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53843</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 79 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: reject negative ifindex Recent changes in net-next (commit 759ab1edb56c (&amp;#34;net: store netdevs in an xarray&amp;#34;)) refactored the handling of pre-assigned ifindexes and let syzbot surface a latent problem in ovs. ovs does not validate ifindex, making it possible to create netdev ports with negative ifindex values. It&amp;#39;s easy to repro with YNL: $ ./cli.py --spec netlink/specs/ovs_datapath.yaml \          --do new \ 	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: 1, &amp;#34;name&amp;#34;:&amp;#34;my-dp&amp;#34;}&amp;#39; $ ./cli.py --spec netlink/specs/ovs_vport.yaml \ 	 --do new \ 	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: &amp;#34;00000001&amp;#34;, &amp;#34;name&amp;#34;: &amp;#34;some-port0&amp;#34;, &amp;#34;dp-ifindex&amp;#34;:3,&amp;#34;ifindex&amp;#34;:4294901760,&amp;#34;type&amp;#34;:2}&amp;#39; $ ip link show -65536: some-port0: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000     link/ether 7a:48:21:ad:0b:fb brd ff:ff:ff:ff:ff:ff ... Validate the inputs. Now the second command correctly returns: $ ./cli.py --spec netlink/specs/ovs_vport.yaml \ 	 --do new \ 	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: &amp;#34;00000001&amp;#34;, &amp;#34;name&amp;#34;: &amp;#34;some-port0&amp;#34;, &amp;#34;dp-ifindex&amp;#34;:3,&amp;#34;ifindex&amp;#34;:4294901760,&amp;#34;type&amp;#34;:2}&amp;#39; lib.ynl.NlError: Netlink error: Numerical result out of range nl_len = 108 (92) nl_flags = 0x300 nl_type = 2 	error: -34	extack: {&amp;#39;msg&amp;#39;: &amp;#39;integer out of range&amp;#39;, &amp;#39;unknown&amp;#39;: [[type:4 len:36] b&amp;#39;\x0c\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x0c\x00\x03\x00\xff\xff\xff\x7f\x00\x00\x00\x00\x08\x00\x01\x00\x08\x00\x00\x00&amp;#39;], &amp;#39;bad-attr&amp;#39;: &amp;#39;.ifindex&amp;#39;} Accept 0 since it used to b…&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 79 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: reject negative ifindex Recent changes in net-next (commit 759ab1edb56c (&amp;#34;net: store netdevs in an xarray&amp;#34;)) refactored the handling of pre-assigned ifindexes and let syzbot surface a latent problem in ovs. ovs does not validate ifindex, making it possible to create netdev ports with negative ifindex values. It&amp;#39;s easy to repro with YNL: $ ./cli.py --spec netlink/specs/ovs_datapath.yaml \          --do new \ 	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: 1, &amp;#34;name&amp;#34;:&amp;#34;my-dp&amp;#34;}&amp;#39; $ ./cli.py --spec netlink/specs/ovs_vport.yaml \ 	 --do new \ 	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: &amp;#34;00000001&amp;#34;, &amp;#34;name&amp;#34;: &amp;#34;some-port0&amp;#34;, &amp;#34;dp-ifindex&amp;#34;:3,&amp;#34;ifindex&amp;#34;:4294901760,&amp;#34;type&amp;#34;:2}&amp;#39; $ ip link show -65536: some-port0: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000     link/ether 7a:48:21:ad:0b:fb brd ff:ff:ff:ff:ff:ff ... Validate the inputs. Now the second command correctly returns: $ ./cli.py --spec netlink/specs/ovs_vport.yaml \ 	 --do new \ 	 --json &amp;#39;{&amp;#34;upcall-pid&amp;#34;: &amp;#34;00000001&amp;#34;, &amp;#34;name&amp;#34;: &amp;#34;some-port0&amp;#34;, &amp;#34;dp-ifindex&amp;#34;:3,&amp;#34;ifindex&amp;#34;:4294901760,&amp;#34;type&amp;#34;:2}&amp;#39; lib.ynl.NlError: Netlink error: Numerical result out of range nl_len = 108 (92) nl_flags = 0x300 nl_type = 2 	error: -34	extack: {&amp;#39;msg&amp;#39;: &amp;#39;integer out of range&amp;#39;, &amp;#39;unknown&amp;#39;: [[type:4 len:36] b&amp;#39;\x0c\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x0c\x00\x03\x00\xff\xff\xff\x7f\x00\x00\x00\x00\x08\x00\x01\x00\x08\x00\x00\x00&amp;#39;], &amp;#39;bad-attr&amp;#39;: &amp;#39;.ifindex&amp;#39;} Accept 0 since it used to b…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53843</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2765 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2765</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2765</guid>
    </item>
  </channel>
</rss>
