<?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>Sat, 03 Oct 2026 05:33:13 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03791</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03791</link>
      <description>bdu:2026-03791</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03791</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53700</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-53700</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-53700</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1032 — 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-2025-avi-1032</link>
      <description>certfr-2025-avi-1032</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1032</guid>
    </item>
    <item>
      <title>EUVD-2026-312213</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312213</link>
      <description>EUVD-2026-312213</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312213</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53700</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-53700</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: max9286: Fix memleak in max9286_v4l2_register()&lt;/p&gt;
&lt;p&gt;There is a kmemleak when testing the media/i2c/max9286.c with bpf mock
device:&lt;/p&gt;
&lt;p&gt;kmemleak: 5 new suspected memory leaks (see /sys/kernel/debug/kmemleak)&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88810defc400 (size 256):
  comm &amp;#34;python3&amp;#34;, pid 278, jiffies 4294737563 (age 31.978s)
  hex dump (first 32 bytes):
    28 06 a7 0a 81 88 ff ff 00 fe 22 12 81 88 ff ff  (.........&amp;#34;.....
    10 c4 ef 0d 81 88 ff ff 10 c4 ef 0d 81 88 ff ff  ................
  backtrace:
    [&amp;lt;00000000191de6a7&amp;gt;] __kmalloc_node+0x44/0x1b0
    [&amp;lt;000000002f4912b7&amp;gt;] kvmalloc_node+0x34/0x180
    [&amp;lt;0000000057dc4cae&amp;gt;] v4l2_ctrl_new+0x325/0x10f0 [videodev]
    [&amp;lt;0000000026030272&amp;gt;] v4l2_ctrl_new_std+0x16f/0x210 [videodev]
    [&amp;lt;00000000f0d9ea2f&amp;gt;] max9286_probe+0x76e/0xbff [max9286]
    [&amp;lt;00000000ea8f6455&amp;gt;] i2c_device_probe+0x28d/0x680
    [&amp;lt;0000000087529af3&amp;gt;] really_probe+0x17c/0x3f0
    [&amp;lt;00000000b08be526&amp;gt;] __driver_probe_device+0xe3/0x170
    [&amp;lt;000000004382edea&amp;gt;] driver_probe_device+0x49/0x120
    [&amp;lt;000000007bde528a&amp;gt;] __device_attach_driver+0xf7/0x150
    [&amp;lt;000000009f9c6ab4&amp;gt;] bus_for_each_drv+0x114/0x180
    [&amp;lt;00000000c8aaf588&amp;gt;] __device_attach+0x1e5/0x2d0
    [&amp;lt;0000000041cc06b9&amp;gt;] bus_probe_device+0x126/0x140
    [&amp;lt;000000002309860d&amp;gt;] device_add+0x810/0x1130
    [&amp;lt;000000002827bf98&amp;gt;] i2c_new_client_device+0x359/0x4f0
    [&amp;lt;00000000593bdc85&amp;gt;] of_i2c_register_device+0xf1/0x110&lt;/p&gt;
&lt;p&gt;max9286_v4l2_register() calls v…&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;media: max9286: Fix memleak in max9286_v4l2_register()&lt;/p&gt;
&lt;p&gt;There is a kmemleak when testing the media/i2c/max9286.c with bpf mock
device:&lt;/p&gt;
&lt;p&gt;kmemleak: 5 new suspected memory leaks (see /sys/kernel/debug/kmemleak)&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88810defc400 (size 256):
  comm &amp;#34;python3&amp;#34;, pid 278, jiffies 4294737563 (age 31.978s)
  hex dump (first 32 bytes):
    28 06 a7 0a 81 88 ff ff 00 fe 22 12 81 88 ff ff  (.........&amp;#34;.....
    10 c4 ef 0d 81 88 ff ff 10 c4 ef 0d 81 88 ff ff  ................
  backtrace:
    [&amp;lt;00000000191de6a7&amp;gt;] __kmalloc_node+0x44/0x1b0
    [&amp;lt;000000002f4912b7&amp;gt;] kvmalloc_node+0x34/0x180
    [&amp;lt;0000000057dc4cae&amp;gt;] v4l2_ctrl_new+0x325/0x10f0 [videodev]
    [&amp;lt;0000000026030272&amp;gt;] v4l2_ctrl_new_std+0x16f/0x210 [videodev]
    [&amp;lt;00000000f0d9ea2f&amp;gt;] max9286_probe+0x76e/0xbff [max9286]
    [&amp;lt;00000000ea8f6455&amp;gt;] i2c_device_probe+0x28d/0x680
    [&amp;lt;0000000087529af3&amp;gt;] really_probe+0x17c/0x3f0
    [&amp;lt;00000000b08be526&amp;gt;] __driver_probe_device+0xe3/0x170
    [&amp;lt;000000004382edea&amp;gt;] driver_probe_device+0x49/0x120
    [&amp;lt;000000007bde528a&amp;gt;] __device_attach_driver+0xf7/0x150
    [&amp;lt;000000009f9c6ab4&amp;gt;] bus_for_each_drv+0x114/0x180
    [&amp;lt;00000000c8aaf588&amp;gt;] __device_attach+0x1e5/0x2d0
    [&amp;lt;0000000041cc06b9&amp;gt;] bus_probe_device+0x126/0x140
    [&amp;lt;000000002309860d&amp;gt;] device_add+0x810/0x1130
    [&amp;lt;000000002827bf98&amp;gt;] i2c_new_client_device+0x359/0x4f0
    [&amp;lt;00000000593bdc85&amp;gt;] of_i2c_register_device+0xf1/0x110&lt;/p&gt;
&lt;p&gt;max9286_v4l2_register() calls v…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-53700</guid>
    </item>
    <item>
      <title>GHSA-9vc2-g7hx-x44h</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9vc2-g7hx-x44h</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: max9286: Fix memleak in max9286_v4l2_register()&lt;/p&gt;
&lt;p&gt;There is a kmemleak when testing the media/i2c/max9286.c with bpf mock
device:&lt;/p&gt;
&lt;p&gt;kmemleak: 5 new suspected memory leaks (see /sys/kernel/debug/kmemleak)&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88810defc400 (size 256):
  comm &amp;#34;python3&amp;#34;, pid 278, jiffies 4294737563 (age 31.978s)
  hex dump (first 32 bytes):
    28 06 a7 0a 81 88 ff ff 00 fe 22 12 81 88 ff ff  (.........&amp;#34;.....
    10 c4 ef 0d 81 88 ff ff 10 c4 ef 0d 81 88 ff ff  ................
  backtrace:
    [&amp;lt;00000000191de6a7&amp;gt;] __kmalloc_node+0x44/0x1b0
    [&amp;lt;000000002f4912b7&amp;gt;] kvmalloc_node+0x34/0x180
    [&amp;lt;0000000057dc4cae&amp;gt;] v4l2_ctrl_new+0x325/0x10f0 [videodev]
    [&amp;lt;0000000026030272&amp;gt;] v4l2_ctrl_new_std+0x16f/0x210 [videodev]
    [&amp;lt;00000000f0d9ea2f&amp;gt;] max9286_probe+0x76e/0xbff [max9286]
    [&amp;lt;00000000ea8f6455&amp;gt;] i2c_device_probe+0x28d/0x680
    [&amp;lt;0000000087529af3&amp;gt;] really_probe+0x17c/0x3f0
    [&amp;lt;00000000b08be526&amp;gt;] __driver_probe_device+0xe3/0x170
    [&amp;lt;000000004382edea&amp;gt;] driver_probe_device+0x49/0x120
    [&amp;lt;000000007bde528a&amp;gt;] __device_attach_driver+0xf7/0x150
    [&amp;lt;000000009f9c6ab4&amp;gt;] bus_for_each_drv+0x114/0x180
    [&amp;lt;00000000c8aaf588&amp;gt;] __device_attach+0x1e5/0x2d0
    [&amp;lt;0000000041cc06b9&amp;gt;] bus_probe_device+0x126/0x140
    [&amp;lt;000000002309860d&amp;gt;] device_add+0x810/0x1130
    [&amp;lt;000000002827bf98&amp;gt;] i2c_new_client_device+0x359/0x4f0
    [&amp;lt;00000000593bdc85&amp;gt;] of_i2c_register_device+0xf1/0x110&lt;/p&gt;
&lt;p&gt;max9286_v4l2_register() calls v…&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;media: max9286: Fix memleak in max9286_v4l2_register()&lt;/p&gt;
&lt;p&gt;There is a kmemleak when testing the media/i2c/max9286.c with bpf mock
device:&lt;/p&gt;
&lt;p&gt;kmemleak: 5 new suspected memory leaks (see /sys/kernel/debug/kmemleak)&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88810defc400 (size 256):
  comm &amp;#34;python3&amp;#34;, pid 278, jiffies 4294737563 (age 31.978s)
  hex dump (first 32 bytes):
    28 06 a7 0a 81 88 ff ff 00 fe 22 12 81 88 ff ff  (.........&amp;#34;.....
    10 c4 ef 0d 81 88 ff ff 10 c4 ef 0d 81 88 ff ff  ................
  backtrace:
    [&amp;lt;00000000191de6a7&amp;gt;] __kmalloc_node+0x44/0x1b0
    [&amp;lt;000000002f4912b7&amp;gt;] kvmalloc_node+0x34/0x180
    [&amp;lt;0000000057dc4cae&amp;gt;] v4l2_ctrl_new+0x325/0x10f0 [videodev]
    [&amp;lt;0000000026030272&amp;gt;] v4l2_ctrl_new_std+0x16f/0x210 [videodev]
    [&amp;lt;00000000f0d9ea2f&amp;gt;] max9286_probe+0x76e/0xbff [max9286]
    [&amp;lt;00000000ea8f6455&amp;gt;] i2c_device_probe+0x28d/0x680
    [&amp;lt;0000000087529af3&amp;gt;] really_probe+0x17c/0x3f0
    [&amp;lt;00000000b08be526&amp;gt;] __driver_probe_device+0xe3/0x170
    [&amp;lt;000000004382edea&amp;gt;] driver_probe_device+0x49/0x120
    [&amp;lt;000000007bde528a&amp;gt;] __device_attach_driver+0xf7/0x150
    [&amp;lt;000000009f9c6ab4&amp;gt;] bus_for_each_drv+0x114/0x180
    [&amp;lt;00000000c8aaf588&amp;gt;] __device_attach+0x1e5/0x2d0
    [&amp;lt;0000000041cc06b9&amp;gt;] bus_probe_device+0x126/0x140
    [&amp;lt;000000002309860d&amp;gt;] device_add+0x810/0x1130
    [&amp;lt;000000002827bf98&amp;gt;] i2c_new_client_device+0x359/0x4f0
    [&amp;lt;00000000593bdc85&amp;gt;] of_i2c_register_device+0xf1/0x110&lt;/p&gt;
&lt;p&gt;max9286_v4l2_register() calls v…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9vc2-g7hx-x44h</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:4139-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:4139-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-2025:4139-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53700</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53700</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 105 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: max9286: Fix memleak in max9286_v4l2_register() There is a kmemleak when testing the media/i2c/max9286.c with bpf mock device: kmemleak: 5 new suspected memory leaks (see /sys/kernel/debug/kmemleak) unreferenced object 0xffff88810defc400 (size 256):   comm &amp;#34;python3&amp;#34;, pid 278, jiffies 4294737563 (age 31.978s)   hex dump (first 32 bytes):     28 06 a7 0a 81 88 ff ff 00 fe 22 12 81 88 ff ff  (.........&amp;#34;.....     10 c4 ef 0d 81 88 ff ff 10 c4 ef 0d 81 88 ff ff  ................   backtrace:     [&amp;lt;00000000191de6a7&amp;gt;] __kmalloc_node+0x44/0x1b0     [&amp;lt;000000002f4912b7&amp;gt;] kvmalloc_node+0x34/0x180     [&amp;lt;0000000057dc4cae&amp;gt;] v4l2_ctrl_new+0x325/0x10f0 [videodev]     [&amp;lt;0000000026030272&amp;gt;] v4l2_ctrl_new_std+0x16f/0x210 [videodev]     [&amp;lt;00000000f0d9ea2f&amp;gt;] max9286_probe+0x76e/0xbff [max9286]     [&amp;lt;00000000ea8f6455&amp;gt;] i2c_device_probe+0x28d/0x680     [&amp;lt;0000000087529af3&amp;gt;] really_probe+0x17c/0x3f0     [&amp;lt;00000000b08be526&amp;gt;] __driver_probe_device+0xe3/0x170     [&amp;lt;000000004382edea&amp;gt;] driver_probe_device+0x49/0x120     [&amp;lt;000000007bde528a&amp;gt;] __device_attach_driver+0xf7/0x150     [&amp;lt;000000009f9c6ab4&amp;gt;] bus_for_each_drv+0x114/0x180     [&amp;lt;00000000c8aaf588&amp;gt;] __device_attach+0x1e5/0x2d0     [&amp;lt;0000000041cc06b9&amp;gt;] bus_probe_device+0x126/0x140     [&amp;lt;000000002309860d&amp;gt;] device_add+0x810/0x1130     [&amp;lt;000000002827bf98&amp;gt;] i2c_new_client_device+0x359/0x4f0     [&amp;lt;00000000593bdc85&amp;gt;] of_i2c_register_device+0xf1/0x110 max9286_v4l2_register() calls v4l2_c…&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 105 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: max9286: Fix memleak in max9286_v4l2_register() There is a kmemleak when testing the media/i2c/max9286.c with bpf mock device: kmemleak: 5 new suspected memory leaks (see /sys/kernel/debug/kmemleak) unreferenced object 0xffff88810defc400 (size 256):   comm &amp;#34;python3&amp;#34;, pid 278, jiffies 4294737563 (age 31.978s)   hex dump (first 32 bytes):     28 06 a7 0a 81 88 ff ff 00 fe 22 12 81 88 ff ff  (.........&amp;#34;.....     10 c4 ef 0d 81 88 ff ff 10 c4 ef 0d 81 88 ff ff  ................   backtrace:     [&amp;lt;00000000191de6a7&amp;gt;] __kmalloc_node+0x44/0x1b0     [&amp;lt;000000002f4912b7&amp;gt;] kvmalloc_node+0x34/0x180     [&amp;lt;0000000057dc4cae&amp;gt;] v4l2_ctrl_new+0x325/0x10f0 [videodev]     [&amp;lt;0000000026030272&amp;gt;] v4l2_ctrl_new_std+0x16f/0x210 [videodev]     [&amp;lt;00000000f0d9ea2f&amp;gt;] max9286_probe+0x76e/0xbff [max9286]     [&amp;lt;00000000ea8f6455&amp;gt;] i2c_device_probe+0x28d/0x680     [&amp;lt;0000000087529af3&amp;gt;] really_probe+0x17c/0x3f0     [&amp;lt;00000000b08be526&amp;gt;] __driver_probe_device+0xe3/0x170     [&amp;lt;000000004382edea&amp;gt;] driver_probe_device+0x49/0x120     [&amp;lt;000000007bde528a&amp;gt;] __device_attach_driver+0xf7/0x150     [&amp;lt;000000009f9c6ab4&amp;gt;] bus_for_each_drv+0x114/0x180     [&amp;lt;00000000c8aaf588&amp;gt;] __device_attach+0x1e5/0x2d0     [&amp;lt;0000000041cc06b9&amp;gt;] bus_probe_device+0x126/0x140     [&amp;lt;000000002309860d&amp;gt;] device_add+0x810/0x1130     [&amp;lt;000000002827bf98&amp;gt;] i2c_new_client_device+0x359/0x4f0     [&amp;lt;00000000593bdc85&amp;gt;] of_i2c_register_device+0xf1/0x110 max9286_v4l2_register() calls v4l2_c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53700</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2394 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2394</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2394</guid>
    </item>
  </channel>
</rss>
