<?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, 06 Oct 2026 23:31:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49192 — drivers: ethernet: cpsw: fix panic when interrupt coaleceing is set via ethtool</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49192</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drivers: ethernet: cpsw: fix panic when interrupt coaleceing is set via ethtool&lt;/p&gt;
&lt;p&gt;cpsw_ethtool_begin directly returns the result of pm_runtime_get_sync
when successful.
pm_runtime_get_sync returns -error code on failure and 0 on successful
resume but also 1 when the device is already active. So the common case
for cpsw_ethtool_begin is to return 1. That leads to inconsistent calls
to pm_runtime_put in the call-chain so that pm_runtime_put is called
one too many times and as result leaving the cpsw dev behind suspended.&lt;/p&gt;
&lt;p&gt;The suspended cpsw dev leads to an access violation later on by
different parts of the cpsw driver.&lt;/p&gt;
&lt;p&gt;Fix this by calling the return-friendly pm_runtime_resume_and_get
function.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drivers: ethernet: cpsw: fix panic when interrupt coaleceing is set via ethtool&lt;/p&gt;
&lt;p&gt;cpsw_ethtool_begin directly returns the result of pm_runtime_get_sync
when successful.
pm_runtime_get_sync returns -error code on failure and 0 on successful
resume but also 1 when the device is already active. So the common case
for cpsw_ethtool_begin is to return 1. That leads to inconsistent calls
to pm_runtime_put in the call-chain so that pm_runtime_put is called
one too many times and as result leaving the cpsw dev behind suspended.&lt;/p&gt;
&lt;p&gt;The suspended cpsw dev leads to an access violation later on by
different parts of the cpsw driver.&lt;/p&gt;
&lt;p&gt;Fix this by calling the return-friendly pm_runtime_resume_and_get
function.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49192</guid>
    </item>
  </channel>
</rss>
