{"api_version":"1","generated_at":"2026-09-17T23:31:46+00:00","cve":"CVE-2026-90432","urls":{"html":"https://cve.report/CVE-2026-90432","api":"https://cve.report/api/cve/CVE-2026-90432.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-90432","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-90432"},"summary":{"title":"sched_ext: Abort directly from the hardlockup handler","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Abort directly from the hardlockup handler\n\nscx_hardlockup() defers the abort to an irq_work because exit claiming used\nto take scx_sched_lock and couldn't run from NMI. The deferral is now\nunnecessary - claiming is NMI-safe and asserting ->aborting is exactly what\nbreaks the live-locks that hard-lock CPUs. Call handle_lockup() directly and\ndrop the irq_work. This also makes the self-detected case recoverable: the\nperf watchdog fires on the hard-locked CPU itself, where a queued irq_work\nnever runs with IRQs off.\n\nAlso fix the return value: %true used to be returned whenever sched_ext was\nloaded, suppressing the kernel's hardlockup report even when the abort was\nrefused. Return %true only when this call initiated the abort.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-17 17:17:48","updated_at":"2026-09-17 17:17:48"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/4d6270bbb4e083a4d2d39f3c36f30f5c939c06ed","name":"https://git.kernel.org/stable/c/4d6270bbb4e083a4d2d39f3c36f30f5c939c06ed","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/3c4b38064937a761ebbf85b1649e812db85eb59e","name":"https://git.kernel.org/stable/c/3c4b38064937a761ebbf85b1649e812db85eb59e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-90432","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90432","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected bd2d76455b65aab77652823919db128a8e585825 4d6270bbb4e083a4d2d39f3c36f30f5c939c06ed git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected bd2d76455b65aab77652823919db128a8e585825 3c4b38064937a761ebbf85b1649e812db85eb59e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.1","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.6 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["kernel/sched/ext/ext.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"4d6270bbb4e083a4d2d39f3c36f30f5c939c06ed","status":"affected","version":"bd2d76455b65aab77652823919db128a8e585825","versionType":"git"},{"lessThan":"3c4b38064937a761ebbf85b1649e812db85eb59e","status":"affected","version":"bd2d76455b65aab77652823919db128a8e585825","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["kernel/sched/ext/ext.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"7.1"},{"lessThan":"7.1","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.6","versionStartIncluding":"7.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"7.1","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Abort directly from the hardlockup handler\n\nscx_hardlockup() defers the abort to an irq_work because exit claiming used\nto take scx_sched_lock and couldn't run from NMI. The deferral is now\nunnecessary - claiming is NMI-safe and asserting ->aborting is exactly what\nbreaks the live-locks that hard-lock CPUs. Call handle_lockup() directly and\ndrop the irq_work. This also makes the self-detected case recoverable: the\nperf watchdog fires on the hard-locked CPU itself, where a queued irq_work\nnever runs with IRQs off.\n\nAlso fix the return value: %true used to be returned whenever sched_ext was\nloaded, suppressing the kernel's hardlockup report even when the abort was\nrefused. Return %true only when this call initiated the abort."}],"providerMetadata":{"dateUpdated":"2026-09-17T16:09:52.429Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/4d6270bbb4e083a4d2d39f3c36f30f5c939c06ed"},{"url":"https://git.kernel.org/stable/c/3c4b38064937a761ebbf85b1649e812db85eb59e"}],"title":"sched_ext: Abort directly from the hardlockup handler","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-90432","datePublished":"2026-09-17T16:09:52.429Z","dateReserved":"2026-09-11T19:38:34.815Z","dateUpdated":"2026-09-17T16:09:52.429Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-17 17:17:48","lastModifiedDate":"2026-09-17 17:17:48","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"90432","Ordinal":"1","Title":"sched_ext: Abort directly from the hardlockup handler","CVE":"CVE-2026-90432","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"90432","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Abort directly from the hardlockup handler\n\nscx_hardlockup() defers the abort to an irq_work because exit claiming used\nto take scx_sched_lock and couldn't run from NMI. The deferral is now\nunnecessary - claiming is NMI-safe and asserting ->aborting is exactly what\nbreaks the live-locks that hard-lock CPUs. Call handle_lockup() directly and\ndrop the irq_work. This also makes the self-detected case recoverable: the\nperf watchdog fires on the hard-locked CPU itself, where a queued irq_work\nnever runs with IRQs off.\n\nAlso fix the return value: %true used to be returned whenever sched_ext was\nloaded, suppressing the kernel's hardlockup report even when the abort was\nrefused. Return %true only when this call initiated the abort.","Type":"Description","Title":"sched_ext: Abort directly from the hardlockup handler"}]}}}