Vulnerability in Linux kernel (CVE-2023-53178)
Summary
Vulnerability in Linux kernel (CVE-2023-53178). Successful exploitation can lead to full system takeover. Exploitable via stress.
Original description
The description as published by the source.
In the Linux kernel, the following vulnerability has been resolved:
mm: fix zswap writeback race condition
The zswap writeback mechanism can cause a race condition resulting in
memory corruption, where a swapped out page gets swapped in with data that
was written to a different page.
The race unfolds like this:
- a page with data A and swap offset X is stored in zswap
- page A is removed off the LRU by zpool driver for writeback in
zswap-shrink work, data for A is mapped by zpool driver - user space program faults and invalidates page entry A, offset X is
considered free - kswapd stores page B at offset X in zswap (zswap could also be
full, if so, page B would then be IOed to X, then skip step 5.) - entry A is replaced by B in tree->rbroot, this doesn't affect the
local reference held by zswap-shrink work - zswap-shrink work writes back A at X, and frees zswap entry A
- swapin of slot X brings A in memory instead of B
The fix:
Once the swap page cache has been allocated (case ZSWAP_SWAPCACHE_NEW),
zswap-shrink work just checks that the local zswap_entry reference is
still the same as the one in the tree. If it's not the same it means that
it's either been invalidated or replaced, in both cases the writeback is
aborted because the local entry contains stale data.
Reproducer:
I originally found this by running stress overnight to validate my work
on the zswap writeback mechanism, it manifested after hours on my test
machine. The key to make it happen…
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2023-53178 has been found in Linux kernel.
Attackers can target a specific entry point like stress over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2023-53178" on the vendor's site.
CVE-2023-53178 (Linux kernel) — CWE-362 / CVSS v3 7.8
Attack vector: local / no user interaction
Attack surface: stress
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-362) exists in Linux kernel. Attackers reach the vulnerable code path via stress.
Check the vendor advisory for the affected versions of Linux kernel. Attack surface: stress.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Linux kernel を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2023-53178 linux
- Ubuntu UBUNTU-CVE-2023-53178 linux
References
- advisory github.com
- advisory nvd.nist.gov
- package git.kernel.org
- web git.kernel.org
- web git.kernel.org
- web git.kernel.org