CVE-2026-98226
Severity unknownNo known exploitationFix availablemm, swap: fix SWAP_USAGE_OFFLIST_BIT collision with real usage count
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 6% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
In the Linux kernel, the following vulnerability has been resolved: mm, swap: fix SWAP_USAGE_OFFLIST_BIT collision with real usage count SWAP_USAGE_OFFLIST_BIT is embedded in the si->inuse_pages usage counter, and is meant to sit above any value that counter can reach. However, it is defined from BITS_PER_TYPE(atomic_t), so it is bit 30. On a system with 4 KiB pages the flag collides with the usage count once that count reaches 4 TiB. swap_usage_in_pages() masks bit 30 out, so whenever the real count has that bit set, every caller of it reads 4 TiB low: * /proc/swaps understates Used by 4 TiB. * A raw count of exactly 2^30 masks to zero, so try_to_unuse() takes its "if (!swap_usage_in_pages(si)) goto success;" early exit and swapoff tears the device down while pages are still swapped out. Nothing in the rest of swapoff aborts the teardown, so those pages are lost. Independently of swapoff, the collision also corrupts the counter and the plist. On a device in normal use, a free that leaves bit 30 set in the count makes swap_usage_sub() see the flag where there is only count, and call add_to_avail_list(). It clears the bit with fetch_and(~SWAP_USAGE_OFFLIST_BIT), leaving the stored count 4 TiB below the real one, and calls plist_add() on a device that is already listed, tripping the WARN_ON(!plist_node_empty(node)) in plist_add() and linking the node a second time. Change the definition of SWAP_USAGE_OFFLIST_BIT to be based on atomic_long_t instead. Note that the usage counter field itself is of this same type, so it is still a valid bit.
Patching and mitigation
- Patch status
- Fix available (source: Microsoft MSRC)
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- msrc.microsoft.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from b228386cf237e659cdf5d8037a19db0b0a06f6b5 before 0a41a46859df0d2bd7ed127197aac7c7389c00ed | 0a41a46859df0d2bd7ed127197aac7c7389c00ed | CVE Program |
| Linux | Linux | from b228386cf237e659cdf5d8037a19db0b0a06f6b5 before 7c0d0d6de46076b43a2acaf1026b6648f8434c39 | 7c0d0d6de46076b43a2acaf1026b6648f8434c39 | CVE Program |
| Linux | Linux | from b228386cf237e659cdf5d8037a19db0b0a06f6b5 before 12e9ac7bc5b254048f886bf421e3a15491106c1f | 12e9ac7bc5b254048f886bf421e3a15491106c1f | CVE Program |
| Linux | Linux | 6.14 | Not documented | CVE Program |
| Microsoft | azl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0 | Not documented | 0:6.18.57-1.1.azl4 | Microsoft MSRC |
| Linux | Linux (unaffected) | from 6.18.54 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.2.8 up to and including 7.2.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.3 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 6.14 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Advisory
Microsoft advisory published
Advisory change
Microsoft advisory revised (2.0): Information published.
Advisory change
Microsoft advisory revised (3.0): Information published.
Patch
Fix documented by Microsoft MSRC
Vendor guidance and references
- Microsoft Security Update Guide (opens in a new tab)vendor-advisory
- https://git.kernel.org/stable/c/0a41a46859df0d2bd7ed127197aac7c7389c00ed (opens in a new tab)
- https://git.kernel.org/stable/c/12e9ac7bc5b254048f886bf421e3a15491106c1f (opens in a new tab)
- https://git.kernel.org/stable/c/7c0d0d6de46076b43a2acaf1026b6648f8434c39 (opens in a new tab)