padata: Put CPU offline callback in ONLINE section to allow failure
Summary
| CVE | CVE-2026-53314 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-06-26 20:17:24 UTC |
| Updated | 2026-06-26 20:17:24 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: padata: Put CPU offline callback in ONLINE section to allow failure syzbot reported the following warning: DEAD callback error for CPU1 WARNING: kernel/cpu.c:1463 at _cpu_down+0x759/0x1020 kernel/cpu.c:1463, CPU#0: syz.0.1960/14614 at commit 4ae12d8bd9a8 ("Merge tag 'kbuild-fixes-7.0-2' of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux") which tglx traced to padata_cpu_dead() given it's the only sub-CPUHP_TEARDOWN_CPU callback that returns an error. Failure isn't allowed in hotplug states before CPUHP_TEARDOWN_CPU so move the CPU offline callback to the ONLINE section where failure is possible. |
Risk And Classification
EPSS: 0.001610000 probability, percentile 0.056920000 (date 2026-06-27)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 894c9ef9780c5cf2f143415e867ee39a33ecb75d 65dae8b34f0810f3fa9f77c4c63650cd20820693 git | Not specified |
| CNA | Linux | Linux | affected 894c9ef9780c5cf2f143415e867ee39a33ecb75d a6d44f477000c6352de6b05e9e276e62083e5fbf git | Not specified |
| CNA | Linux | Linux | affected 894c9ef9780c5cf2f143415e867ee39a33ecb75d 3e6c08dd97dcd22a00aee469e0adfa819071d80e git | Not specified |
| CNA | Linux | Linux | affected 894c9ef9780c5cf2f143415e867ee39a33ecb75d 5a9f29a3e076b637d2234093e57989cf755ded5b git | Not specified |
| CNA | Linux | Linux | affected 894c9ef9780c5cf2f143415e867ee39a33ecb75d 9afe53f14a2aae8c4beb30e5ea51641a34f1a3d3 git | Not specified |
| CNA | Linux | Linux | affected 894c9ef9780c5cf2f143415e867ee39a33ecb75d c8c4a2972f83c8b68ff03b43cecdb898939ff851 git | Not specified |
| CNA | Linux | Linux | affected 2b1207801c393a5e9af2fbac2dd8b0377d8ae63a git | Not specified |
| CNA | Linux | Linux | affected 0685dfa0a2ff7635c0b64f7b7f0fafbf1c3e0c14 git | Not specified |
| CNA | Linux | Linux | affected 3f4d3d010477365ee1aefedc3ad52563740b777e git | Not specified |
| CNA | Linux | Linux | affected 4.19.202 4.20 semver | Not specified |
| CNA | Linux | Linux | affected 5.4.22 5.5 semver | Not specified |
| CNA | Linux | Linux | affected 5.5.6 5.6 semver | Not specified |
| CNA | Linux | Linux | affected 5.6 | Not specified |
| CNA | Linux | Linux | unaffected 5.6 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.175 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.141 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.91 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.33 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0.10 7.0.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/c8c4a2972f83c8b68ff03b43cecdb898939ff851 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/9afe53f14a2aae8c4beb30e5ea51641a34f1a3d3 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/a6d44f477000c6352de6b05e9e276e62083e5fbf | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/65dae8b34f0810f3fa9f77c4c63650cd20820693 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/5a9f29a3e076b637d2234093e57989cf755ded5b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/3e6c08dd97dcd22a00aee469e0adfa819071d80e | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.