https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 20:18:23 +0000 https://vulnerability.circl.lu/vuln/cve-2024-35797 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm: cachestat: fix two shmem bugs</p> <p>When cachestat on shmem races with swapping and invalidation, there are two possible bugs:</p> <p>1) A swapin error can have resulted in a poisoned swap entry in the shmem inode&#39;s xarray. Calling get_shadow_from_swap_cache() on it will result in an out-of-bounds access to swapper_spaces[].</p> <p>Validate the entry with non_swap_entry() before going further.</p> <p>2) When we find a valid swap entry in the shmem&#39;s inode, the shadow entry in the swapcache might not exist yet: swap IO is still in progress and we&#39;re before __remove_mapping; swapin, invalidation, or swapoff have removed the shadow from swapcache after we saw the shmem swap entry.</p> <p>This will send a NULL to workingset_test_recent(). The latter purely operates on pointer bits, so it won&#39;t crash - node 0, memcg ID 0, eviction timestamp 0, etc. are all valid inputs - but it&#39;s a bogus test. In theory that could result in a false &#34;recently evicted&#34; count.</p> <p>Such a false positive wouldn&#39;t be the end of the world. But for code clarity and (future) robustness, be explicit about this case.</p> <p>Bail on get_shadow_from_swap_cache() returning NULL.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm: cachestat: fix two shmem bugs</p> <p>When cachestat on shmem races with swapping and invalidation, there are two possible bugs:</p> <p>1) A swapin error can have resulted in a poisoned swap entry in the shmem inode&#39;s xarray. Calling get_shadow_from_swap_cache() on it will result in an out-of-bounds access to swapper_spaces[].</p> <p>Validate the entry with non_swap_entry() before going further.</p> <p>2) When we find a valid swap entry in the shmem&#39;s inode, the shadow entry in the swapcache might not exist yet: swap IO is still in progress and we&#39;re before __remove_mapping; swapin, invalidation, or swapoff have removed the shadow from swapcache after we saw the shmem swap entry.</p> <p>This will send a NULL to workingset_test_recent(). The latter purely operates on pointer bits, so it won&#39;t crash - node 0, memcg ID 0, eviction timestamp 0, etc. are all valid inputs - but it&#39;s a bogus test. In theory that could result in a false &#34;recently evicted&#34; count.</p> <p>Such a false positive wouldn&#39;t be the end of the world. But for code clarity and (future) robustness, be explicit about this case.</p> <p>Bail on get_shadow_from_swap_cache() returning NULL.</p> https://vulnerability.circl.lu/vuln/cve-2024-35797