<?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://db.gcve.eu</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, 29 Sep 2026 01:49:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49655 — fscache: Fix invalidation/lookup race</title>
      <link>https://db.gcve.eu/vuln/cve-2022-49655</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;fscache: Fix invalidation/lookup race&lt;/p&gt;
&lt;p&gt;If an NFS file is opened for writing and closed, fscache_invalidate() will
be asked to invalidate the file - however, if the cookie is in the
LOOKING_UP state (or the CREATING state), then request to invalidate
doesn&amp;#39;t get recorded for fscache_cookie_state_machine() to do something
with.&lt;/p&gt;
&lt;p&gt;Fix this by making __fscache_invalidate() set a flag if it sees the cookie
is in the LOOKING_UP state to indicate that we need to go to invalidation.
Note that this requires a count on the n_accesses counter for the state
machine, which that will release when it&amp;#39;s done.&lt;/p&gt;
&lt;p&gt;fscache_cookie_state_machine() then shifts to the INVALIDATING state if it
sees the flag.&lt;/p&gt;
&lt;p&gt;Without this, an nfs file can get corrupted if it gets modified locally and
then read locally as the cache contents may not get updated.&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;fscache: Fix invalidation/lookup race&lt;/p&gt;
&lt;p&gt;If an NFS file is opened for writing and closed, fscache_invalidate() will
be asked to invalidate the file - however, if the cookie is in the
LOOKING_UP state (or the CREATING state), then request to invalidate
doesn&amp;#39;t get recorded for fscache_cookie_state_machine() to do something
with.&lt;/p&gt;
&lt;p&gt;Fix this by making __fscache_invalidate() set a flag if it sees the cookie
is in the LOOKING_UP state to indicate that we need to go to invalidation.
Note that this requires a count on the n_accesses counter for the state
machine, which that will release when it&amp;#39;s done.&lt;/p&gt;
&lt;p&gt;fscache_cookie_state_machine() then shifts to the INVALIDATING state if it
sees the flag.&lt;/p&gt;
&lt;p&gt;Without this, an nfs file can get corrupted if it gets modified locally and
then read locally as the cache contents may not get updated.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2022-49655</guid>
    </item>
  </channel>
</rss>
