How to Fix CVE-2026-23233: Security vulnerability in Linux

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-23233 is a security vulnerability in Linux Linux. The fix is to upgrade to Linux 0; Linux 6.12.74; Linux 6.18.13; Linux 6.19.3; Linux 6.6.127; Linux 7.0.

What is CVE-2026-23233?

In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix to avoid mapping wrong physical block for swapfile

Xiaolong Guo reported a f2fs bug in bugzilla [1]

[1] https://bugzilla.kernel.org/show_bug.cgi?id=220951

Quoted:

"When using stress-ng's swap stress test on F2FS filesystem with kernel 6.6+,

the system experiences data corruption leading to either:

1 dm-verity corruption errors and device reboot

2 F2FS node corruption errors and boot hangs

The issue occurs specifically when:

1 Using F2FS filesystem (ext4 is unaffected)

2 Swapfile size is less than F2FS section size (2MB)

3 Swapfile has fragmented physical layout (multiple non-contiguous extents)

4 Kernel version is 6.6+ (6.1 is unaffected)

The root cause is in check_swap_activate() function in fs/f2fs/data.c. When the

first extent of a small swapfile (< 2MB) is not aligned to section boundaries,

the function incorrectly treats it as the last extent, failing to map

subsequent extents. This results in incorrect swap_extent creation where only

the first extent is mapped, causing subsequent swap writes to overwrite wrong

physical locations (other files' data).

Steps to Reproduce

1 Setup a device with F2FS-formatted userdata partition

2 Compile stress-ng from https://github.com/ColinIanKing/stress-ng

3 Run swap stress test: (Android devices)

adb shell "cd /data/stressng; ./stress-ng-64 --metrics-brief --timeout 60

--swap 0"

Log:

1 Ftrace shows in kernel 6.6, only first extent is mapped during second

f2fs_map_blocks call in check_swap_activate():

stress-ng-swap-8990: f2fs_map_blocks: ino=11002, file offset=0, start

blkaddr=0x43143, len=0x1

(Only 4KB mapped, not the full swapfile)

2 in kernel 6.1, both extents are correctly mapped:

stress-ng-swap-5966: f2fs_map_blocks: ino=28011, file offset=0, start

blkaddr=0x13cd4, len=0x1

stress-ng-swap-5966: f2fs_map_blocks: ino=28011, file offset=1, start

blkaddr=0x60c84b, len=0xff

The problematic code is in check_swap_activate():

if ((pblock - SM_I(sbi)->main_blkaddr) % blks_per_sec ||

nr_pblocks % blks_per_sec ||

!f2fs_valid_pinned_area(sbi, pblock)) {

bool last_extent = false;

not_aligned++;

nr_pblocks = roundup(nr_pblocks, blks_per_sec);

if (cur_lblock + nr_pblocks > sis->max)

nr_pblocks -= blks_per_sec;

/* this extent is last one */

if (!nr_pblocks) {

nr_pblocks = last_lblock - cur_lblock;

last_extent = true;

}

ret = f2fs_migrate_blocks(inode, cur_lblock, nr_pblocks);

if (ret) {

if (ret == -ENOENT)

ret = -EINVAL;

goto out;

}

if (!last_extent)

goto retry;

}

When the first extent is unaligned and roundup(nr_pblocks, blks_per_sec)

exceeds sis->max, we subtract blks_per_sec resulting in nr_pblocks = 0. The

code then incorrectly assumes this is the last extent, sets nr_pblocks =

last_lblock - cur_lblock (entire swapfile), and performs migration. After

migration, it doesn't retry mapping, so subsequent extents are never processed.

"

to fix this issue, we need to lookup block mapping info after

we migrate all blocks in the tail of swapfile. The official advisory is at https://git.kernel.org/stable/c/d4534a7f6c92baaf7e12a45fc6e37332cafafc33.

Am I affected?

Check the version of Linux you are running and compare it against the Affected row above (Linux 40d76c393cca83938b11eb7ca8983aa3cd0ed69b to <d4534a7f6c92baaf7e12a45fc6e37332cafafc33; Linux 9703d69d9d153bb230711d0d577454552aeb13d4 to <1ff415eef513bf12deb058fc50d57788c46c48e6; Linux 9703d69d9d153bb230711d0d577454552aeb13d4 to <fee27b69dde1a05908b350eea42937af2387c4fe; Linux 9703d69d9d153bb230711d0d577454552aeb13d4 to <607cb9d83838d2cd9f0406c2403ed61aadf0edff; Linux 9703d69d9d153bb230711d0d577454552aeb13d4 to <5c145c03188bc9ba1c29e0bc4d527a5978fc47f9; Linux 6.9). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:

# Linux package check
dpkg -s linux 2>/dev/null | grep -i ^Version
rpm -q linux 2>/dev/null
command -v linux >/dev/null && linux --version 2>/dev/null

# Windows (PowerShell)
Get-Package -Name "*Linux*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "Linux" 2>$null

How to fix CVE-2026-23233

Upgrade Linux to a patched build: Linux 0; Linux 6.12.74; Linux 6.18.13; Linux 6.19.3; Linux 6.6.127; Linux 7.0. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade linux
dpkg -s linux | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux

sudo dnf upgrade --refresh linux -y
# or for older releases:
sudo yum update linux -y
rpm -q linux

SUSE / openSUSE

sudo zypper refresh
sudo zypper update linux
rpm -q linux

Node.js / npm

# Update the affected package in your project
npm install Linux@latest
npm ls Linux
npm audit fix

Complete PowerShell remediation script (Windows)

# Fix script for CVE-2026-23233 affecting Linux
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-23233-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*Linux*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\linux-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Linux" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to Linux 0; Linux 6.12.74; Linux 6.18.13; Linux 6.19.3; Linux 6.6.127; Linux 7.0"
    winget upgrade --name "Linux" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "Linux"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)

#!/usr/bin/env bash
# Fix script for CVE-2026-23233 affecting Linux
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-23233-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s linux 2>/dev/null | grep -i ^Version || echo "linux not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q linux || echo "linux not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-23233-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/linux /etc/linux.d /etc/linux.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: Linux 0; Linux 6.12.74; Linux 6.18.13; Linux 6.19.3; Linux 6.6.127; Linux 7.0)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y linux
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y linux
elif command -v yum >/dev/null; then
    yum update -y linux
elif command -v zypper >/dev/null; then
    zypper --non-interactive update linux
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s linux 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q linux
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)

# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)

New-NetFirewallRule -DisplayName "Block-CVE-2026-23233" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-23233"

Disable the affected service (Linux)

sudo systemctl stop linux 2>/dev/null || true
sudo systemctl disable linux 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.

# Linux
dpkg -s linux 2>/dev/null | grep -i ^Version
rpm -q linux 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true

# Windows
Get-Package -Name "*Linux*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above Linux 0; Linux 6.12.74; Linux 6.18.13; Linux 6.19.3; Linux 6.6.127; Linux 7.0. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2026-23346: Critical Vulnerability in Linux — Critical Vulnerability in Linux
• How to Fix CVE-2026-31780: wifi: wilc1000: fix u8 overflow in Linux — wifi: wilc1000: fix u8 overflow in Linux
• How to Fix CVE-2026-23127: Critical Vulnerability in Linux , Critical Vulnerability in Linux
• How to Fix CVE-2026-23167: Critical Vulnerability in Linux , Critical Vulnerability in Linux
• How to Fix CVE-2026-43271: Race Condition in Linux , Race Condition in Linux

Is CVE-2026-23233 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-23233?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-23233?

Not published in the verified data we ingested. Check the NVD entry linked in the References section for the latest score.

Where is the official advisory for CVE-2026-23233?

The vendor advisory is at https://git.kernel.org/stable/c/d4534a7f6c92baaf7e12a45fc6e37332cafafc33. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-23233.

References

• Official vendor advisory: https://git.kernel.org/stable/c/d4534a7f6c92baaf7e12a45fc6e37332cafafc33
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23233
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Additional reference: https://git.kernel.org/stable/c/1ff415eef513bf12deb058fc50d57788c46c48e6
• Additional reference: https://git.kernel.org/stable/c/fee27b69dde1a05908b350eea42937af2387c4fe
• Additional reference: https://git.kernel.org/stable/c/607cb9d83838d2cd9f0406c2403ed61aadf0edff

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*