<?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 04:11:00 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-03068</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-03068</link>
      <description>bdu:2025-03068</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-03068</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-35986</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-35986</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-35986</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0526 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent une élé…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0526</link>
      <description>certfr-2024-avi-0526</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0526</guid>
    </item>
    <item>
      <title>EUVD-2026-345732</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345732</link>
      <description>EUVD-2026-345732</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345732</guid>
    </item>
    <item>
      <title>fkie_cve-2024-35986</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-35986</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered&lt;/p&gt;
&lt;p&gt;The power_supply frame-work is not really designed for there to be
long living in kernel references to power_supply devices.&lt;/p&gt;
&lt;p&gt;Specifically unregistering a power_supply while some other code has
a reference to it triggers a WARN in power_supply_unregister():&lt;/p&gt;
&lt;p&gt;WARN_ON(atomic_dec_return(&amp;amp;psy-&amp;gt;use_cnt));&lt;/p&gt;
&lt;p&gt;Folllowed by the power_supply still getting removed and the
backing data freed anyway, leaving the tusb1210 charger-detect code
with a dangling reference, resulting in a crash the next time
tusb1210_get_online() is called.&lt;/p&gt;
&lt;p&gt;Fix this by only holding the reference in tusb1210_get_online()
freeing it at the end of the function. Note this still leaves
a theoretical race window, but it avoids the issue when manually
rmmod-ing the charger chip driver during development.&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;phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered&lt;/p&gt;
&lt;p&gt;The power_supply frame-work is not really designed for there to be
long living in kernel references to power_supply devices.&lt;/p&gt;
&lt;p&gt;Specifically unregistering a power_supply while some other code has
a reference to it triggers a WARN in power_supply_unregister():&lt;/p&gt;
&lt;p&gt;WARN_ON(atomic_dec_return(&amp;amp;psy-&amp;gt;use_cnt));&lt;/p&gt;
&lt;p&gt;Folllowed by the power_supply still getting removed and the
backing data freed anyway, leaving the tusb1210 charger-detect code
with a dangling reference, resulting in a crash the next time
tusb1210_get_online() is called.&lt;/p&gt;
&lt;p&gt;Fix this by only holding the reference in tusb1210_get_online()
freeing it at the end of the function. Note this still leaves
a theoretical race window, but it avoids the issue when manually
rmmod-ing the charger chip driver during development.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-35986</guid>
    </item>
    <item>
      <title>GHSA-8xgr-fvrm-f9g3</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8xgr-fvrm-f9g3</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered&lt;/p&gt;
&lt;p&gt;The power_supply frame-work is not really designed for there to be
long living in kernel references to power_supply devices.&lt;/p&gt;
&lt;p&gt;Specifically unregistering a power_supply while some other code has
a reference to it triggers a WARN in power_supply_unregister():&lt;/p&gt;
&lt;p&gt;WARN_ON(atomic_dec_return(&amp;amp;psy-&amp;gt;use_cnt));&lt;/p&gt;
&lt;p&gt;Folllowed by the power_supply still getting removed and the
backing data freed anyway, leaving the tusb1210 charger-detect code
with a dangling reference, resulting in a crash the next time
tusb1210_get_online() is called.&lt;/p&gt;
&lt;p&gt;Fix this by only holding the reference in tusb1210_get_online()
freeing it at the end of the function. Note this still leaves
a theoretical race window, but it avoids the issue when manually
rmmod-ing the charger chip driver during development.&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;phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered&lt;/p&gt;
&lt;p&gt;The power_supply frame-work is not really designed for there to be
long living in kernel references to power_supply devices.&lt;/p&gt;
&lt;p&gt;Specifically unregistering a power_supply while some other code has
a reference to it triggers a WARN in power_supply_unregister():&lt;/p&gt;
&lt;p&gt;WARN_ON(atomic_dec_return(&amp;amp;psy-&amp;gt;use_cnt));&lt;/p&gt;
&lt;p&gt;Folllowed by the power_supply still getting removed and the
backing data freed anyway, leaving the tusb1210 charger-detect code
with a dangling reference, resulting in a crash the next time
tusb1210_get_online() is called.&lt;/p&gt;
&lt;p&gt;Fix this by only holding the reference in tusb1210_get_online()
freeing it at the end of the function. Note this still leaves
a theoretical race window, but it avoids the issue when manually
rmmod-ing the charger chip driver during development.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8xgr-fvrm-f9g3</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2135-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2135-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:2135-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-35986</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-35986</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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered The power_supply frame-work is not really designed for there to be long living in kernel references to power_supply devices. Specifically unregistering a power_supply while some other code has a reference to it triggers a WARN in power_supply_unregister(): 	WARN_ON(atomic_dec_return(&amp;amp;psy-&amp;gt;use_cnt)); Folllowed by the power_supply still getting removed and the backing data freed anyway, leaving the tusb1210 charger-detect code with a dangling reference, resulting in a crash the next time tusb1210_get_online() is called. Fix this by only holding the reference in tusb1210_get_online() freeing it at the end of the function. Note this still leaves a theoretical race window, but it avoids the issue when manually rmmod-ing the charger chip driver during development.&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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered The power_supply frame-work is not really designed for there to be long living in kernel references to power_supply devices. Specifically unregistering a power_supply while some other code has a reference to it triggers a WARN in power_supply_unregister(): 	WARN_ON(atomic_dec_return(&amp;amp;psy-&amp;gt;use_cnt)); Folllowed by the power_supply still getting removed and the backing data freed anyway, leaving the tusb1210 charger-detect code with a dangling reference, resulting in a crash the next time tusb1210_get_online() is called. Fix this by only holding the reference in tusb1210_get_online() freeing it at the end of the function. Note this still leaves a theoretical race window, but it avoids the issue when manually rmmod-ing the charger chip driver during development.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-35986</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1188 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1188</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://cve.radiocsirt.org/vuln/wid-sec-w-2024-1188</guid>
    </item>
  </channel>
</rss>
