CVE-2026-23233: f2fs: fix to avoid mapping wrong physical block for swapfile
Published Mar 4, 2026
·Updated
f2fs: fix to avoid mapping wrong physical block for swapfile
Affected Software
6 affected componentsFixes available
Linux Linux kernel>=6.6
Linux Linux kernel>=6.6.33<6.6.127
Linux Linux kernel>=6.9<6.12.74
Linux Linux kernel>=6.13<6.18.13
Linux Linux kernel>=6.19<6.19.3
Microsoft azl3 kernel 6.6.126.1-1
Remediation
Event History
Mar 4, 2026
CVE Published
via MITRE·02:36 PM
Data Sourced
via MITRE·02:36 PM
Description
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Mar 19, 2026
Data Sourced
via Microsoft·08:03 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:03 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2026-23233?
The severity of CVE-2026-23233 is classified as medium due to the potential risk of incorrect physical block mapping for swapfiles.
2
How do I fix CVE-2026-23233?
To mitigate CVE-2026-23233, users should upgrade their Linux Kernel to version 6.7 or later where the vulnerability has been addressed.
3
What systems are affected by CVE-2026-23233?
CVE-2026-23233 affects the Linux Kernel version 6.6 and earlier deployments.
4
What does CVE-2026-23233 involve?
CVE-2026-23233 involves an issue in the f2fs file system that can lead to mapping the wrong physical block for swapfiles.
5
Who reported CVE-2026-23233?
CVE-2026-23233 was reported by Xiaolong Guo through a bug submission in the kernel bugzilla.