<?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 10:27:05 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-07634</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-07634</link>
      <description>bdu:2024-07634</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-07634</guid>
    </item>
    <item>
      <title>EUVD-2026-310186</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310186</link>
      <description>EUVD-2026-310186</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310186</guid>
    </item>
    <item>
      <title>fkie_cve-2022-48845</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-48845</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;MIPS: smp: fill in sibling and core maps earlier&lt;/p&gt;
&lt;p&gt;After enabling CONFIG_SCHED_CORE (landed during 5.14 cycle),
2-core 2-thread-per-core interAptiv (CPS-driven) started emitting
the following:&lt;/p&gt;
&lt;p&gt;[    0.025698] CPU1 revision is: 0001a120 (MIPS interAptiv (multi))
[    0.048183] ------------[ cut here ]------------
[    0.048187] WARNING: CPU: 1 PID: 0 at kernel/sched/core.c:6025 sched_core_cpu_starting+0x198/0x240
[    0.048220] Modules linked in:
[    0.048233] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.17.0-rc3+ #35 b7b319f24073fd9a3c2aa7ad15fb7993eec0b26f
[    0.048247] Stack : 817f0000 00000004 327804c8 810eb050 00000000 00000004 00000000 c314fdd1
[    0.048278]         830cbd64 819c0000 81800000 817f0000 83070bf4 00000001 830cbd08 00000000
[    0.048307]         00000000 00000000 815fcbc4 00000000 00000000 00000000 00000000 00000000
[    0.048334]         00000000 00000000 00000000 00000000 817f0000 00000000 00000000 817f6f34
[    0.048361]         817f0000 818a3c00 817f0000 00000004 00000000 00000000 4dc33260 0018c933
[    0.048389]         ...
[    0.048396] Call Trace:
[    0.048399] [&amp;lt;8105a7bc&amp;gt;] show_stack+0x3c/0x140
[    0.048424] [&amp;lt;8131c2a0&amp;gt;] dump_stack_lvl+0x60/0x80
[    0.048440] [&amp;lt;8108b5c0&amp;gt;] __warn+0xc0/0xf4
[    0.048454] [&amp;lt;8108b658&amp;gt;] warn_slowpath_fmt+0x64/0x10c
[    0.048467] [&amp;lt;810bd418&amp;gt;] sched_core_cpu_starting+0x198/0x240
[    0.048483] [&amp;lt;810c6514&amp;gt;] sched_cpu_starting+0x14/0x80
[    0.04849…&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;MIPS: smp: fill in sibling and core maps earlier&lt;/p&gt;
&lt;p&gt;After enabling CONFIG_SCHED_CORE (landed during 5.14 cycle),
2-core 2-thread-per-core interAptiv (CPS-driven) started emitting
the following:&lt;/p&gt;
&lt;p&gt;[    0.025698] CPU1 revision is: 0001a120 (MIPS interAptiv (multi))
[    0.048183] ------------[ cut here ]------------
[    0.048187] WARNING: CPU: 1 PID: 0 at kernel/sched/core.c:6025 sched_core_cpu_starting+0x198/0x240
[    0.048220] Modules linked in:
[    0.048233] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.17.0-rc3+ #35 b7b319f24073fd9a3c2aa7ad15fb7993eec0b26f
[    0.048247] Stack : 817f0000 00000004 327804c8 810eb050 00000000 00000004 00000000 c314fdd1
[    0.048278]         830cbd64 819c0000 81800000 817f0000 83070bf4 00000001 830cbd08 00000000
[    0.048307]         00000000 00000000 815fcbc4 00000000 00000000 00000000 00000000 00000000
[    0.048334]         00000000 00000000 00000000 00000000 817f0000 00000000 00000000 817f6f34
[    0.048361]         817f0000 818a3c00 817f0000 00000004 00000000 00000000 4dc33260 0018c933
[    0.048389]         ...
[    0.048396] Call Trace:
[    0.048399] [&amp;lt;8105a7bc&amp;gt;] show_stack+0x3c/0x140
[    0.048424] [&amp;lt;8131c2a0&amp;gt;] dump_stack_lvl+0x60/0x80
[    0.048440] [&amp;lt;8108b5c0&amp;gt;] __warn+0xc0/0xf4
[    0.048454] [&amp;lt;8108b658&amp;gt;] warn_slowpath_fmt+0x64/0x10c
[    0.048467] [&amp;lt;810bd418&amp;gt;] sched_core_cpu_starting+0x198/0x240
[    0.048483] [&amp;lt;810c6514&amp;gt;] sched_cpu_starting+0x14/0x80
[    0.04849…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-48845</guid>
    </item>
    <item>
      <title>GHSA-r7cx-6c4p-88r8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r7cx-6c4p-88r8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;MIPS: smp: fill in sibling and core maps earlier&lt;/p&gt;
&lt;p&gt;After enabling CONFIG_SCHED_CORE (landed during 5.14 cycle),
2-core 2-thread-per-core interAptiv (CPS-driven) started emitting
the following:&lt;/p&gt;
&lt;p&gt;[    0.025698] CPU1 revision is: 0001a120 (MIPS interAptiv (multi))
[    0.048183] ------------[ cut here ]------------
[    0.048187] WARNING: CPU: 1 PID: 0 at kernel/sched/core.c:6025 sched_core_cpu_starting+0x198/0x240
[    0.048220] Modules linked in:
[    0.048233] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.17.0-rc3+ #35 b7b319f24073fd9a3c2aa7ad15fb7993eec0b26f
[    0.048247] Stack : 817f0000 00000004 327804c8 810eb050 00000000 00000004 00000000 c314fdd1
[    0.048278]         830cbd64 819c0000 81800000 817f0000 83070bf4 00000001 830cbd08 00000000
[    0.048307]         00000000 00000000 815fcbc4 00000000 00000000 00000000 00000000 00000000
[    0.048334]         00000000 00000000 00000000 00000000 817f0000 00000000 00000000 817f6f34
[    0.048361]         817f0000 818a3c00 817f0000 00000004 00000000 00000000 4dc33260 0018c933
[    0.048389]         ...
[    0.048396] Call Trace:
[    0.048399] [&amp;lt;8105a7bc&amp;gt;] show_stack+0x3c/0x140
[    0.048424] [&amp;lt;8131c2a0&amp;gt;] dump_stack_lvl+0x60/0x80
[    0.048440] [&amp;lt;8108b5c0&amp;gt;] __warn+0xc0/0xf4
[    0.048454] [&amp;lt;8108b658&amp;gt;] warn_slowpath_fmt+0x64/0x10c
[    0.048467] [&amp;lt;810bd418&amp;gt;] sched_core_cpu_starting+0x198/0x240
[    0.048483] [&amp;lt;810c6514&amp;gt;] sched_cpu_starting+0x14/0x80
[    0.04849…&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;MIPS: smp: fill in sibling and core maps earlier&lt;/p&gt;
&lt;p&gt;After enabling CONFIG_SCHED_CORE (landed during 5.14 cycle),
2-core 2-thread-per-core interAptiv (CPS-driven) started emitting
the following:&lt;/p&gt;
&lt;p&gt;[    0.025698] CPU1 revision is: 0001a120 (MIPS interAptiv (multi))
[    0.048183] ------------[ cut here ]------------
[    0.048187] WARNING: CPU: 1 PID: 0 at kernel/sched/core.c:6025 sched_core_cpu_starting+0x198/0x240
[    0.048220] Modules linked in:
[    0.048233] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.17.0-rc3+ #35 b7b319f24073fd9a3c2aa7ad15fb7993eec0b26f
[    0.048247] Stack : 817f0000 00000004 327804c8 810eb050 00000000 00000004 00000000 c314fdd1
[    0.048278]         830cbd64 819c0000 81800000 817f0000 83070bf4 00000001 830cbd08 00000000
[    0.048307]         00000000 00000000 815fcbc4 00000000 00000000 00000000 00000000 00000000
[    0.048334]         00000000 00000000 00000000 00000000 817f0000 00000000 00000000 817f6f34
[    0.048361]         817f0000 818a3c00 817f0000 00000004 00000000 00000000 4dc33260 0018c933
[    0.048389]         ...
[    0.048396] Call Trace:
[    0.048399] [&amp;lt;8105a7bc&amp;gt;] show_stack+0x3c/0x140
[    0.048424] [&amp;lt;8131c2a0&amp;gt;] dump_stack_lvl+0x60/0x80
[    0.048440] [&amp;lt;8108b5c0&amp;gt;] __warn+0xc0/0xf4
[    0.048454] [&amp;lt;8108b658&amp;gt;] warn_slowpath_fmt+0x64/0x10c
[    0.048467] [&amp;lt;810bd418&amp;gt;] sched_core_cpu_starting+0x198/0x240
[    0.048483] [&amp;lt;810c6514&amp;gt;] sched_cpu_starting+0x14/0x80
[    0.04849…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r7cx-6c4p-88r8</guid>
    </item>
    <item>
      <title>OESA-2024-1944 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1944</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: 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;
usb: musb: tusb6010: check return value after calling platform_get_resource()&#13;
&#13;
It will cause null-ptr-deref if platform_get_resource() returns NULL,
we need check the return value.(CVE-2021-47181)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: fix memory ordering between normal and ordered work functions&#13;
&#13;
Ordered work functions aren&amp;amp;apos;t guaranteed to be handled by the same thread
which executed the normal work functions. The only way execution between
normal/ordered functions is synchronized is via the WORK_DONE_BIT,
unfortunately the used bitops don&amp;amp;apos;t guarantee any ordering whatsoever.&#13;
&#13;
This manifested as seemingly inexplicable crashes on ARM64, where
async_chunk::inode is seen as non-null in async_cow_submit which causes
submit_compressed_extents to be called and crash occurs because
async_chunk::inode suddenly became NULL. The call trace was similar to:&#13;
&#13;
    pc : submit_compressed_extents+0x38/0x3d0
    lr : async_cow_submit+0x50/0xd0
    sp : ffff800015d4bc20&#13;
&#13;
    &amp;amp;lt;registers omitted for brevity&amp;amp;gt;&#13;
&#13;
    Call trace:
     submit_compressed_extents+0x38/0x3d0
     async_cow_submit+0x50/0xd0
     run_ordered_work+0xc8/0x280
     btrfs_work_helper+0x98/0x250
     process_one_work+0x1f0/0x4ac
     worker_thread+0x188/0x504
     kthread+0x110/0x114
     ret_from_fork+0x10/0x18…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: 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;
usb: musb: tusb6010: check return value after calling platform_get_resource()&#13;
&#13;
It will cause null-ptr-deref if platform_get_resource() returns NULL,
we need check the return value.(CVE-2021-47181)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: fix memory ordering between normal and ordered work functions&#13;
&#13;
Ordered work functions aren&amp;amp;apos;t guaranteed to be handled by the same thread
which executed the normal work functions. The only way execution between
normal/ordered functions is synchronized is via the WORK_DONE_BIT,
unfortunately the used bitops don&amp;amp;apos;t guarantee any ordering whatsoever.&#13;
&#13;
This manifested as seemingly inexplicable crashes on ARM64, where
async_chunk::inode is seen as non-null in async_cow_submit which causes
submit_compressed_extents to be called and crash occurs because
async_chunk::inode suddenly became NULL. The call trace was similar to:&#13;
&#13;
    pc : submit_compressed_extents+0x38/0x3d0
    lr : async_cow_submit+0x50/0xd0
    sp : ffff800015d4bc20&#13;
&#13;
    &amp;amp;lt;registers omitted for brevity&amp;amp;gt;&#13;
&#13;
    Call trace:
     submit_compressed_extents+0x38/0x3d0
     async_cow_submit+0x50/0xd0
     run_ordered_work+0xc8/0x280
     btrfs_work_helper+0x98/0x250
     process_one_work+0x1f0/0x4ac
     worker_thread+0x188/0x504
     kthread+0x110/0x114
     ret_from_fork+0x10/0x18…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1944</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-48845</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48845</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:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 109 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: MIPS: smp: fill in sibling and core maps earlier After enabling CONFIG_SCHED_CORE (landed during 5.14 cycle), 2-core 2-thread-per-core interAptiv (CPS-driven) started emitting the following: [    0.025698] CPU1 revision is: 0001a120 (MIPS interAptiv (multi)) [    0.048183] ------------[ cut here ]------------ [    0.048187] WARNING: CPU: 1 PID: 0 at kernel/sched/core.c:6025 sched_core_cpu_starting+0x198/0x240 [    0.048220] Modules linked in: [    0.048233] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.17.0-rc3+ #35 b7b319f24073fd9a3c2aa7ad15fb7993eec0b26f [    0.048247] Stack : 817f0000 00000004 327804c8 810eb050 00000000 00000004 00000000 c314fdd1 [    0.048278]         830cbd64 819c0000 81800000 817f0000 83070bf4 00000001 830cbd08 00000000 [    0.048307]         00000000 00000000 815fcbc4 00000000 00000000 00000000 00000000 00000000 [    0.048334]         00000000 00000000 00000000 00000000 817f0000 00000000 00000000 817f6f34 [    0.048361]         817f0000 818a3c00 817f0000 00000004 00000000 00000000 4dc33260 0018c933 [    0.048389]         ... [    0.048396] Call Trace: [    0.048399] [&amp;lt;8105a7bc&amp;gt;] show_stack+0x3c/0x140 [    0.048424] [&amp;lt;8131c2a0&amp;gt;] dump_stack_lvl+0x60/0x80 [    0.048440] [&amp;lt;8108b5c0&amp;gt;] __warn+0xc0/0xf4 [    0.048454] [&amp;lt;8108b658&amp;gt;] warn_slowpath_fmt+0x64/0x10c [    0.048467] [&amp;lt;810bd418&amp;gt;] sched_core_cpu_starting+0x198/0x240 [    0.048483] [&amp;lt;810c6514&amp;gt;] sched_cpu_starting+0x14/0x80 [    0.048497]…&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:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 109 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: MIPS: smp: fill in sibling and core maps earlier After enabling CONFIG_SCHED_CORE (landed during 5.14 cycle), 2-core 2-thread-per-core interAptiv (CPS-driven) started emitting the following: [    0.025698] CPU1 revision is: 0001a120 (MIPS interAptiv (multi)) [    0.048183] ------------[ cut here ]------------ [    0.048187] WARNING: CPU: 1 PID: 0 at kernel/sched/core.c:6025 sched_core_cpu_starting+0x198/0x240 [    0.048220] Modules linked in: [    0.048233] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.17.0-rc3+ #35 b7b319f24073fd9a3c2aa7ad15fb7993eec0b26f [    0.048247] Stack : 817f0000 00000004 327804c8 810eb050 00000000 00000004 00000000 c314fdd1 [    0.048278]         830cbd64 819c0000 81800000 817f0000 83070bf4 00000001 830cbd08 00000000 [    0.048307]         00000000 00000000 815fcbc4 00000000 00000000 00000000 00000000 00000000 [    0.048334]         00000000 00000000 00000000 00000000 817f0000 00000000 00000000 817f6f34 [    0.048361]         817f0000 818a3c00 817f0000 00000004 00000000 00000000 4dc33260 0018c933 [    0.048389]         ... [    0.048396] Call Trace: [    0.048399] [&amp;lt;8105a7bc&amp;gt;] show_stack+0x3c/0x140 [    0.048424] [&amp;lt;8131c2a0&amp;gt;] dump_stack_lvl+0x60/0x80 [    0.048440] [&amp;lt;8108b5c0&amp;gt;] __warn+0xc0/0xf4 [    0.048454] [&amp;lt;8108b658&amp;gt;] warn_slowpath_fmt+0x64/0x10c [    0.048467] [&amp;lt;810bd418&amp;gt;] sched_core_cpu_starting+0x198/0x240 [    0.048483] [&amp;lt;810c6514&amp;gt;] sched_cpu_starting+0x14/0x80 [    0.048497]…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48845</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1625 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1625</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1625</guid>
    </item>
  </channel>
</rss>
