Vulnerability · Published Dec 16, 2025 · Assigned by Linux

CVE-2025-68248vmw_balloon: indicate success when effectively deflating during migration

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 7% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 93.3% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: vmw_balloon: indicate success when effectively deflating during migration When migrating a balloon page, we first deflate the old page to then inflate the new page. However, if inflating the new page succeeded, we effectively deflated the old page, reducing the balloon size. In that case, the migration actually worked: similar to migrating+ immediately deflating the new page. The old page will be freed back to the buddy. Right now, the core will leave the page be marked as isolated (as we returned an error). When later trying to putback that page, we will run into the WARN_ON_ONCE() in balloon_page_putback(). That handling was changed in commit 3544c4faccb8 ("mm/balloon_compaction: stop using __ClearPageMovable()"); before that change, we would have tolerated that way of handling it. To fix it, let's just return 0 in that case, making the core effectively just clear the "isolated" flag + freeing it back to the buddy as if the migration succeeded. Note that the new page will also get freed when the core puts the last reference. Note that this also makes it all be more consistent: we will no longer unisolate the page in the balloon driver while keeping it marked as being isolated in migration core. This was found by code inspection.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Ubuntu:25.10linux6.17.0-14.14UBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-68248
Ubuntu:25.10linux-aws6.17.0-1007.7UBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-aws-6.176.17.0-1007.7~24.04.1UBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-68248
Ubuntu:25.10linux-azure6.17.0-1008.8UBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-68248
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-68248
Ubuntu:25.10linux-gcp6.17.0-1007.7UBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1008.8~24.04.1UBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-nvidia-6.176.17.0-1008.8UBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1011.11UBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-68248
Ubuntu:25.10linux-oracle6.17.0-1007.7UBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1007.7~24.04.1UBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-68248
Ubuntu:25.10linux-raspi6.17.0-1008.8UBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-68248
Ubuntu:25.10linux-realtime6.17.0-1006.7UBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-68248
Ubuntu:25.10linux-riscv6.17.0-14.14.1UBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-68248
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-68248
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-68248

Affected products (as reported)

VendorProductVersions
Linux Linux 3544c4faccb8f0867bc65f8007ee70bfb5054305 – before aa05a044c5c2e147d726ac2fae1a97e0775eac113544c4faccb8f0867bc65f8007ee70bfb5054305 – before 4ba5a8a7faa647ada8eae61a36517cf369f5bbe4
Linux Linux 6.17

References