<?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-04T01:45:26.207422+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-49172</id>
    <title>CVE-2022-49172 — parisc: Fix non-access data TLB cache flush faults</title>
    <updated>2026-10-04T01:45:26.286455+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>parisc: Fix non-access data TLB cache flush faults</p>
<p>When a page is not present, we get non-access data TLB faults from
the fdc and fic instructions in flush_user_dcache_range_asm and
flush_user_icache_range_asm. When these occur, the cache line is
not invalidated and potentially we get memory corruption. The
problem was hidden by the nullification of the flush instructions.</p>
<p>These faults also affect performance. With pa8800/pa8900 processors,
there will be 32 faults per 4 KB page since the cache line is 128
bytes.  There will be more faults with earlier processors.</p>
<p>The problem is fixed by using flush_cache_pages(). It does the flush
using a tmp alias mapping.</p>
<p>The flush_cache_pages() call in flush_cache_range() flushed too
large a range.</p>
<p>V2: Remove unnecessary preempt_disable() and preempt_enable() calls.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-49172"/>
  </entry>
</feed>
