<?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>Tue, 17 Nov 2026 09:48:47 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-98418 — CVE-2026-98418 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98418</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-98418</guid>
    </item>
    <item>
      <title>EUVD-2026-388762</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-388762</link>
      <description>EUVD-2026-388762</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-388762</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98418</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98418</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched/core: Avoid false migration warning for proxy donors&lt;/p&gt;
&lt;p&gt;Proxy execution can move a blocked donor&amp;#39;s scheduling context to the
lock owner&amp;#39;s CPU even when the donor is migration-disabled. The donor
does not execute there, and its original execution CPU remains recorded
in wake_cpu.&lt;/p&gt;
&lt;p&gt;set_task_cpu() warns unconditionally for migration-disabled tasks, so a
subsequent proxy migration or the wakeup path returning the donor home
triggers a false positive: moving a blocked scheduling context does not
violate the migration-disabled execution context.&lt;/p&gt;
&lt;p&gt;For example, creating a mutex owner on CPU1 and a migration-disabled
waiter on CPU0 can trigger the following warning:&lt;/p&gt;
&lt;p&gt;proxy_migrate_repro: donor blocking on CPU0 with migration disabled
  proxy_migrate_repro: donor moved from CPU0 to CPU1
  WARNING: kernel/sched/core.c:3389 at set_task_cpu+0x1d3/0x280
  ...
  Call Trace:
   try_to_wake_up+0x43f/0x780
   __mutex_unlock_slowpath+0x330/0x540
   owner_fn+0x9f/0xc0 [proxy_migrate_repro]
  ...
  proxy_migrate_repro: donor woke on CPU0, task_cpu=0
  proxy_migrate_repro: completed&lt;/p&gt;
&lt;p&gt;Exclude blocked proxy donors from the warning. The proxy wakeup path
restores an executable placement before clearing the blocked state.&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;sched/core: Avoid false migration warning for proxy donors&lt;/p&gt;
&lt;p&gt;Proxy execution can move a blocked donor&amp;#39;s scheduling context to the
lock owner&amp;#39;s CPU even when the donor is migration-disabled. The donor
does not execute there, and its original execution CPU remains recorded
in wake_cpu.&lt;/p&gt;
&lt;p&gt;set_task_cpu() warns unconditionally for migration-disabled tasks, so a
subsequent proxy migration or the wakeup path returning the donor home
triggers a false positive: moving a blocked scheduling context does not
violate the migration-disabled execution context.&lt;/p&gt;
&lt;p&gt;For example, creating a mutex owner on CPU1 and a migration-disabled
waiter on CPU0 can trigger the following warning:&lt;/p&gt;
&lt;p&gt;proxy_migrate_repro: donor blocking on CPU0 with migration disabled
  proxy_migrate_repro: donor moved from CPU0 to CPU1
  WARNING: kernel/sched/core.c:3389 at set_task_cpu+0x1d3/0x280
  ...
  Call Trace:
   try_to_wake_up+0x43f/0x780
   __mutex_unlock_slowpath+0x330/0x540
   owner_fn+0x9f/0xc0 [proxy_migrate_repro]
  ...
  proxy_migrate_repro: donor woke on CPU0, task_cpu=0
  proxy_migrate_repro: completed&lt;/p&gt;
&lt;p&gt;Exclude blocked proxy donors from the warning. The proxy wakeup path
restores an executable placement before clearing the blocked state.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98418</guid>
    </item>
    <item>
      <title>GHSA-2pjr-w693-xmqc</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2pjr-w693-xmqc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched/core: Avoid false migration warning for proxy donors&lt;/p&gt;
&lt;p&gt;Proxy execution can move a blocked donor&amp;#39;s scheduling context to the
lock owner&amp;#39;s CPU even when the donor is migration-disabled. The donor
does not execute there, and its original execution CPU remains recorded
in wake_cpu.&lt;/p&gt;
&lt;p&gt;set_task_cpu() warns unconditionally for migration-disabled tasks, so a
subsequent proxy migration or the wakeup path returning the donor home
triggers a false positive: moving a blocked scheduling context does not
violate the migration-disabled execution context.&lt;/p&gt;
&lt;p&gt;For example, creating a mutex owner on CPU1 and a migration-disabled
waiter on CPU0 can trigger the following warning:&lt;/p&gt;
&lt;p&gt;proxy_migrate_repro: donor blocking on CPU0 with migration disabled
  proxy_migrate_repro: donor moved from CPU0 to CPU1
  WARNING: kernel/sched/core.c:3389 at set_task_cpu+0x1d3/0x280
  ...
  Call Trace:
   try_to_wake_up+0x43f/0x780
   __mutex_unlock_slowpath+0x330/0x540
   owner_fn+0x9f/0xc0 [proxy_migrate_repro]
  ...
  proxy_migrate_repro: donor woke on CPU0, task_cpu=0
  proxy_migrate_repro: completed&lt;/p&gt;
&lt;p&gt;Exclude blocked proxy donors from the warning. The proxy wakeup path
restores an executable placement before clearing the blocked state.&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;sched/core: Avoid false migration warning for proxy donors&lt;/p&gt;
&lt;p&gt;Proxy execution can move a blocked donor&amp;#39;s scheduling context to the
lock owner&amp;#39;s CPU even when the donor is migration-disabled. The donor
does not execute there, and its original execution CPU remains recorded
in wake_cpu.&lt;/p&gt;
&lt;p&gt;set_task_cpu() warns unconditionally for migration-disabled tasks, so a
subsequent proxy migration or the wakeup path returning the donor home
triggers a false positive: moving a blocked scheduling context does not
violate the migration-disabled execution context.&lt;/p&gt;
&lt;p&gt;For example, creating a mutex owner on CPU1 and a migration-disabled
waiter on CPU0 can trigger the following warning:&lt;/p&gt;
&lt;p&gt;proxy_migrate_repro: donor blocking on CPU0 with migration disabled
  proxy_migrate_repro: donor moved from CPU0 to CPU1
  WARNING: kernel/sched/core.c:3389 at set_task_cpu+0x1d3/0x280
  ...
  Call Trace:
   try_to_wake_up+0x43f/0x780
   __mutex_unlock_slowpath+0x330/0x540
   owner_fn+0x9f/0xc0 [proxy_migrate_repro]
  ...
  proxy_migrate_repro: donor woke on CPU0, task_cpu=0
  proxy_migrate_repro: completed&lt;/p&gt;
&lt;p&gt;Exclude blocked proxy donors from the warning. The proxy wakeup path
restores an executable placement before clearing the blocked state.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2pjr-w693-xmqc</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98418</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98418</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 96 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/core: Avoid false migration warning for proxy donors Proxy execution can move a blocked donor&amp;#39;s scheduling context to the lock owner&amp;#39;s CPU even when the donor is migration-disabled. The donor does not execute there, and its original execution CPU remains recorded in wake_cpu. set_task_cpu() warns unconditionally for migration-disabled tasks, so a subsequent proxy migration or the wakeup path returning the donor home triggers a false positive: moving a blocked scheduling context does not violate the migration-disabled execution context. For example, creating a mutex owner on CPU1 and a migration-disabled waiter on CPU0 can trigger the following warning:   proxy_migrate_repro: donor blocking on CPU0 with migration disabled   proxy_migrate_repro: donor moved from CPU0 to CPU1   WARNING: kernel/sched/core.c:3389 at set_task_cpu+0x1d3/0x280   ...   Call Trace:    try_to_wake_up+0x43f/0x780    __mutex_unlock_slowpath+0x330/0x540    owner_fn+0x9f/0xc0 [proxy_migrate_repro]   ...   proxy_migrate_repro: donor woke on CPU0, task_cpu=0   proxy_migrate_repro: completed Exclude blocked proxy donors from the warning. The proxy wakeup path restores an executable placement before clearing the blocked state.&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 96 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/core: Avoid false migration warning for proxy donors Proxy execution can move a blocked donor&amp;#39;s scheduling context to the lock owner&amp;#39;s CPU even when the donor is migration-disabled. The donor does not execute there, and its original execution CPU remains recorded in wake_cpu. set_task_cpu() warns unconditionally for migration-disabled tasks, so a subsequent proxy migration or the wakeup path returning the donor home triggers a false positive: moving a blocked scheduling context does not violate the migration-disabled execution context. For example, creating a mutex owner on CPU1 and a migration-disabled waiter on CPU0 can trigger the following warning:   proxy_migrate_repro: donor blocking on CPU0 with migration disabled   proxy_migrate_repro: donor moved from CPU0 to CPU1   WARNING: kernel/sched/core.c:3389 at set_task_cpu+0x1d3/0x280   ...   Call Trace:    try_to_wake_up+0x43f/0x780    __mutex_unlock_slowpath+0x330/0x540    owner_fn+0x9f/0xc0 [proxy_migrate_repro]   ...   proxy_migrate_repro: donor woke on CPU0, task_cpu=0   proxy_migrate_repro: completed Exclude blocked proxy donors from the warning. The proxy wakeup path restores an executable placement before clearing the blocked state.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98418</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3951 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3951</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&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, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3951</guid>
    </item>
  </channel>
</rss>
