CVE-2026-80718

mm/percpu-km: fix bitmap overflow and accounting in pcpu_create_chunk()

HIGH
7.8
CVSS Score
Published: August 28, 2026 at 06:53 AM UTC
Updated: August 29, 2026 at 07:16 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: mm/percpu-km: fix bitmap overflow and accounting in pcpu_create_chunk() In pcpu_create_chunk(), nr_pages is the total contiguous backing allocation, i.e., nr_units * pcpu_unit_pages, but pcpu_chunk_populated() uses it to set chunk->populated, whose size is pcpu_unit_pages, bitmap. Since bit N in chunk->populated means page offset N inside every unit is backed. When nr_units > 1, the function writes beyond chunk->populated. Fix it by using chunk->nr_pages. It also fixes the global pcpu_nr_empty_pop_pages accounting, since pcpu_balance_free() only iterates up to chunk->nr_pages. Commit a63d4ac4ab609 ("percpu: make percpu-km set chunk->populated bitmap properly") introduced the bitmap overflow issue. Later, commit b539b87fed37f ("percpu: implmeent pcpu_nr_empty_pop_pages and chunk->nr_populated") added pcpu_nr_empty_pop_pages and caused the accounting issue.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.18 ≤ v < 5.10.2653.18 ≤ v < 5.15.2163.18 ≤ v < 6.1.1833.18 ≤ v < 6.12.1033.18 ≤ v < 6.18.443.18 ≤ v < 6.6.1513.18 ≤ v < 7.1.83.18 ≤ v < 7.23.18a63d4ac4ab6094c051a5a240260d16117a7a2f86
Vendor states this is fixed in 01504da375f5b19df195cb1cb1cf1dd184318f97 (fixed)
Vendor states this is fixed in 32134cf9211b83bed9076d0739c5906fbea4c763 (fixed)
Vendor states this is fixed in 5c7fc39bf19abb38a996aaad77b3e3a8f48581c3 (fixed)
Vendor states this is fixed in 5f43d2c1bea280dcdfabaf156c25e7402fb8039f (fixed)
Vendor states this is fixed in 6fc7da2a052f2825fff785e860e67183f5acaaba (fixed)
Vendor states this is fixed in 89b1b79c308818a715e75f28744b70d8940a07c9 (fixed)
Vendor states this is fixed in 92c43ac3c2b09eb16162e8144e73c00b7c3e29d6 (fixed)
Vendor states this is fixed in a6940b84c8c035da465b7165fdfcfb005545724e (fixed)
Vendor states this is fixed in 3.18 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card