<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T23:31:07.575635+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2022-49192</id>
    <title>CVE-2022-49192 — drivers: ethernet: cpsw: fix panic when interrupt coaleceing is set via ethtool</title>
    <updated>2026-10-06T23:31:07.577198+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drivers: ethernet: cpsw: fix panic when interrupt coaleceing is set via ethtool</p>
<p>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.</p>
<p>The suspended cpsw dev leads to an access violation later on by
different parts of the cpsw driver.</p>
<p>Fix this by calling the return-friendly pm_runtime_resume_and_get
function.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-49192"/>
  </entry>
</feed>
