<?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-03T12:06:37.938779+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-49605</id>
    <title>CVE-2022-49605 — igc: Reinstate IGC_REMOVED logic and implement it properly</title>
    <updated>2026-10-03T12:06:37.940800+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>igc: Reinstate IGC_REMOVED logic and implement it properly</p>
<p>The initially merged version of the igc driver code (via commit
146740f9abc4, "igc: Add support for PF") contained the following
IGC_REMOVED checks in the igc_rd32/wr32() MMIO accessors:</p>
<p>u32 igc_rd32(struct igc_hw *hw, u32 reg)
	{
		u8 __iomem *hw_addr = READ_ONCE(hw-&gt;hw_addr);
		u32 value = 0;</p>
<p>if (IGC_REMOVED(hw_addr))
			return ~value;</p>
<p>value = readl(&amp;hw_addr[reg]);</p>
<p>/* reads should not return all F's */
		if (!(~value) &amp;&amp; (!reg || !(~readl(hw_addr))))
			hw-&gt;hw_addr = NULL;</p>
<p>return value;
	}</p>
<p>And:</p>
<p>#define wr32(reg, val) \
	do { \
		u8 __iomem *hw_addr = READ_ONCE((hw)-&gt;hw_addr); \
		if (!IGC_REMOVED(hw_addr)) \
			writel((val), &amp;hw_addr[(reg)]); \
	} while (0)</p>
<p>E.g. igb has similar checks in its MMIO accessors, and has a similar
macro E1000_REMOVED, which is implemented as follows:</p>
<p>#define E1000_REMOVED(h) unlikely(!(h))</p>
<p>These checks serve to detect and take note of an 0xffffffff MMIO read
return from the device, which can be caused by a PCIe link flap or some
other kind of PCI bus error, and to avoid performing MMIO reads and
writes from that point onwards.</p>
<p>However, the IGC_REMOVED macro was not originally implemented:</p>
<p>#ifndef IGC_REMOVED
	#define IGC_REMOVED(a) (0)
	#endif /* IGC_REMOVED */</p>
<p>This led to the IGC_REMOVED logic to be removed entirely in a
subsequent commit (commit 3c215fb18e70, "igc: remove IGC_REMOVED
function…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-49605"/>
  </entry>
</feed>
