https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 16:54:28 +0000 https://vulnerability.circl.lu/vuln/cve-2026-31400 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>sunrpc: fix cache_request leak in cache_release</p> <p>When a reader&#39;s file descriptor is closed while in the middle of reading a cache_request (rp-&gt;offset != 0), cache_release() decrements the request&#39;s readers count but never checks whether it should free the request.</p> <p>In cache_read(), when readers drops to 0 and CACHE_PENDING is clear, the cache_request is removed from the queue and freed along with its buffer and cache_head reference. cache_release() lacks this cleanup.</p> <p>The only other path that frees requests with readers == 0 is cache_dequeue(), but it runs only when CACHE_PENDING transitions from set to clear. If that transition already happened while readers was still non-zero, cache_dequeue() will have skipped the request, and no subsequent call will clean it up.</p> <p>Add the same cleanup logic from cache_read() to cache_release(): after decrementing readers, check if it reached 0 with CACHE_PENDING clear, and if so, dequeue and free the cache_request.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>sunrpc: fix cache_request leak in cache_release</p> <p>When a reader&#39;s file descriptor is closed while in the middle of reading a cache_request (rp-&gt;offset != 0), cache_release() decrements the request&#39;s readers count but never checks whether it should free the request.</p> <p>In cache_read(), when readers drops to 0 and CACHE_PENDING is clear, the cache_request is removed from the queue and freed along with its buffer and cache_head reference. cache_release() lacks this cleanup.</p> <p>The only other path that frees requests with readers == 0 is cache_dequeue(), but it runs only when CACHE_PENDING transitions from set to clear. If that transition already happened while readers was still non-zero, cache_dequeue() will have skipped the request, and no subsequent call will clean it up.</p> <p>Add the same cleanup logic from cache_read() to cache_release(): after decrementing readers, check if it reached 0 with CACHE_PENDING clear, and if so, dequeue and free the cache_request.</p> https://vulnerability.circl.lu/vuln/cve-2026-31400