In the Linux kernel, the following vulnerability has been resolved: mm:
cachestat: fix folio read-after-free in cache walk In cachestat, we access
the folio from the page cache’s xarray to compute its page offset, and
check for its dirty and writeback flags. However, we do not hold a
reference to the folio before performing these actions, which means the
folio can concurrently be released and reused as another folio/page/slab.
Get around this altogether by just using xarray’s existing machinery for
the folio page offsets and dirty/writeback states. This changes behavior
for tmpfs files to now always report zeroes in their dirty and writeback
counters. This is okay as tmpfs doesn’t follow conventional writeback cache
behavior: its pages get “cleaned” during swapout, after which they’re no
longer resident etc.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 22.04 | noarch | linux-aws-6.5 | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-azure-6.5 | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-gcp-6.5 | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-nvidia-6.5 | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-oem-6.5 | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-oracle-6.5 | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-starfive-6.5 | < any | UNKNOWN |
git.kernel.org/linus/3a75cb05d53f4a6823a32deb078de1366954a804 (6.8-rc7)
git.kernel.org/stable/c/3a75cb05d53f4a6823a32deb078de1366954a804
git.kernel.org/stable/c/ba60fdf75e89ea762bb617be578dc47f27655117
git.kernel.org/stable/c/fe7e008e0ce728252e4ec652cceebcc62211657c
launchpad.net/bugs/cve/CVE-2024-26630
nvd.nist.gov/vuln/detail/CVE-2024-26630
security-tracker.debian.org/tracker/CVE-2024-26630
www.cve.org/CVERecord?id=CVE-2024-26630