<?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>Wed, 30 Sep 2026 11:42:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-48989 — fscache: Fix oops due to race with cookie_lru and use_cookie</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-48989</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 oops due to race with cookie_lru and use_cookie&lt;/p&gt;
&lt;p&gt;If a cookie expires from the LRU and the LRU_DISCARD flag is set, but
the state machine has not run yet, it&amp;#39;s possible another thread can call
fscache_use_cookie and begin to use it.&lt;/p&gt;
&lt;p&gt;When the cookie_worker finally runs, it will see the LRU_DISCARD flag
set, transition the cookie-&amp;gt;state to LRU_DISCARDING, which will then
withdraw the cookie.  Once the cookie is withdrawn the object is removed
the below oops will occur because the object associated with the cookie
is now NULL.&lt;/p&gt;
&lt;p&gt;Fix the oops by clearing the LRU_DISCARD bit if another thread uses the
cookie before the cookie_worker runs.&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000008
  ...
  CPU: 31 PID: 44773 Comm: kworker/u130:1 Tainted: G     E    6.0.0-5.dneg.x86_64 #1
  Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
  Workqueue: events_unbound netfs_rreq_write_to_cache_work [netfs]
  RIP: 0010:cachefiles_prepare_write+0x28/0x90 [cachefiles]
  ...
  Call Trace:
    netfs_rreq_write_to_cache_work+0x11c/0x320 [netfs]
    process_one_work+0x217/0x3e0
    worker_thread+0x4a/0x3b0
    kthread+0xd6/0x100&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 oops due to race with cookie_lru and use_cookie&lt;/p&gt;
&lt;p&gt;If a cookie expires from the LRU and the LRU_DISCARD flag is set, but
the state machine has not run yet, it&amp;#39;s possible another thread can call
fscache_use_cookie and begin to use it.&lt;/p&gt;
&lt;p&gt;When the cookie_worker finally runs, it will see the LRU_DISCARD flag
set, transition the cookie-&amp;gt;state to LRU_DISCARDING, which will then
withdraw the cookie.  Once the cookie is withdrawn the object is removed
the below oops will occur because the object associated with the cookie
is now NULL.&lt;/p&gt;
&lt;p&gt;Fix the oops by clearing the LRU_DISCARD bit if another thread uses the
cookie before the cookie_worker runs.&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000008
  ...
  CPU: 31 PID: 44773 Comm: kworker/u130:1 Tainted: G     E    6.0.0-5.dneg.x86_64 #1
  Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
  Workqueue: events_unbound netfs_rreq_write_to_cache_work [netfs]
  RIP: 0010:cachefiles_prepare_write+0x28/0x90 [cachefiles]
  ...
  Call Trace:
    netfs_rreq_write_to_cache_work+0x11c/0x320 [netfs]
    process_one_work+0x217/0x3e0
    worker_thread+0x4a/0x3b0
    kthread+0xd6/0x100&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-48989</guid>
    </item>
  </channel>
</rss>
