CVE-2021-47454powerpc/smp: do not decrement idle task preempt count in CPU offline
- 5.5MediumCVSS base score
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: powerpc/smp: do not decrement idle task preempt count in CPU offline With PREEMPT_COUNT=y, when a CPU is offlined and then onlined again, we get: BUG: scheduling while atomic: swapper/1/0/0x00000000 no locks held by swapper/1/0. CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.0-rc2+ #100 Call Trace: dump_stack_lvl+0xac/0x108 __schedule_bug+0xac/0xe0 __schedule+0xcf8/0x10d0 schedule_idle+0x3c/0x70 do_idle+0x2d8/0x4a0 cpu_startup_entry+0x38/0x40 start_secondary+0x2ec/0x3a0 start_secondary_prolog+0x10/0x14 This is because powerpc's arch_cpu_idle_dead() decrements the idle task's preempt count, for reasons explained in commit a7c2bb8279d2 ("powerpc: Re-enable preemption before cpu_die()"), specifically "start_secondary() expects a preempt_count() of 0." However, since commit 2c669ef6979c ("powerpc/preempt: Don't touch the idle task's preempt_count during hotplug") and commit f1a0a376ca0c ("sched/core: Initialize the idle task with preemption disabled"), that justification no longer holds. The idle task isn't supposed to re-enable preemption, so remove the vestigial preempt_enable() from the CPU offline path. Tested with pseries and powernv in qemu, and pseries on PowerVM.
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 2 years later
· 2 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected bdf4d33e8342b90386156204e1da0cdfdb4bf146 – < 53770a411559cf7bc0906d1df319cc533d2f4f58
- affected 2c669ef6979c370f98d4b876e54f19613c81e075 – < 3ea0b497a7a2fff6a4b7090310c9f52c91975934
- affected 2c669ef6979c370f98d4b876e54f19613c81e075 – < 787252a10d9422f3058df9a4821f389e5326c440
- affected 2b6148ef2bd6d8ddc76e7873114f7769b6aa25f0
- affected 20a015e948b825afb47855de2efce7cae7c2608f
- affected 5.10.50 – < 5.10.76
- affected 5.12.17 – < 5.13
- affected 5.13.2 – < 5.14
- affected 5.14
- unaffected < 5.14
- unaffected 5.10.76 – ≤ 5.10.*
- unaffected 5.14.15 – ≤ 5.14.*
- unaffected 5.15 – ≤ *
References
References3
- https://git.kernel.org/stable/c/53770a411559cf7bc0906d1df319cc533d2f4f58 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/3ea0b497a7a2fff6a4b7090310c9f52c91975934 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/787252a10d9422f3058df9a4821f389e5326c440 (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2021-34459 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2021-47454)Record last updated .