{"api_version":"1","generated_at":"2026-06-08T19:17:07+00:00","cve":"CVE-2026-46290","urls":{"html":"https://cve.report/CVE-2026-46290","api":"https://cve.report/api/cve/CVE-2026-46290.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-46290","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-46290"},"summary":{"title":"x86/efi: Fix graceful fault handling after FPU softirq changes","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nx86/efi: Fix graceful fault handling after FPU softirq changes\n\nSince commit d02198550423 (\"x86/fpu: Improve crypto performance by\nmaking kernel-mode FPU reliably usable in softirqs\"), kernel_fpu_begin()\ncalls fpregs_lock() which uses local_bh_disable() instead of the\nprevious preempt_disable(). This sets SOFTIRQ_OFFSET in preempt_count\nduring the entire EFI runtime service call, causing in_interrupt() to\nreturn true in normal task context.\n\nThe graceful page fault handler efi_crash_gracefully_on_page_fault()\nuses in_interrupt() to bail out for faults in real interrupt context.\nWith SOFTIRQ_OFFSET now set, the handler always bails out, leaving EFI\nfirmware page faults unhandled. This escalates to die() which also sees\nin_interrupt() as true and calls panic(\"Fatal exception in interrupt\"),\nresulting in a hard system freeze. On systems with buggy firmware that\ntriggers page faults during EFI runtime calls (e.g., accessing unmapped\nmemory in GetTime()), this causes an unrecoverable hang instead of the\nexpected graceful EFI_ABORTED recovery.\n\nFix by replacing in_interrupt() with !in_task(). This preserves the\noriginal intent of bailing for interrupts or NMI faults, while no longer\nfalsely triggering from the FPU code path's local_bh_disable().\n\n[ardb: Sashiko spotted that using 'in_hardirq() || in_nmi()' leaves a\n       window where a softirq may be taken before fpregs_lock() is\n       called, but after efi_rts_work.efi_rts_id has been assigned,\n       and any page faults occurring in that window will then be\n       misidentified as having been caused by the firmware. Instead,\n       use !in_task(), which incorporates in_serving_softirq(). ]","state":"PUBLISHED","assigner":"Linux","published_at":"2026-06-08 17:16:47","updated_at":"2026-06-08 17:16:47"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/088f65e206087bf903743bd18417261d7a4c9644","name":"https://git.kernel.org/stable/c/088f65e206087bf903743bd18417261d7a4c9644","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/db155b86d1523e85941f61efd7d7ffb594cc9a29","name":"https://git.kernel.org/stable/c/db155b86d1523e85941f61efd7d7ffb594cc9a29","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/22b365ba1af3d8c6036b8e5112fffe80998b85a0","name":"https://git.kernel.org/stable/c/22b365ba1af3d8c6036b8e5112fffe80998b85a0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-46290","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46290","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d02198550423a0b695e7a24ec77153209ad45b09 22b365ba1af3d8c6036b8e5112fffe80998b85a0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d02198550423a0b695e7a24ec77153209ad45b09 db155b86d1523e85941f61efd7d7ffb594cc9a29 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d02198550423a0b695e7a24ec77153209ad45b09 088f65e206087bf903743bd18417261d7a4c9644 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.15","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.15 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.30 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.7 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1-rc3 * 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":["arch/x86/platform/efi/quirks.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"22b365ba1af3d8c6036b8e5112fffe80998b85a0","status":"affected","version":"d02198550423a0b695e7a24ec77153209ad45b09","versionType":"git"},{"lessThan":"db155b86d1523e85941f61efd7d7ffb594cc9a29","status":"affected","version":"d02198550423a0b695e7a24ec77153209ad45b09","versionType":"git"},{"lessThan":"088f65e206087bf903743bd18417261d7a4c9644","status":"affected","version":"d02198550423a0b695e7a24ec77153209ad45b09","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["arch/x86/platform/efi/quirks.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.15"},{"lessThan":"6.15","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.30","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1-rc3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.30","versionStartIncluding":"6.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.7","versionStartIncluding":"6.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1-rc3","versionStartIncluding":"6.15","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nx86/efi: Fix graceful fault handling after FPU softirq changes\n\nSince commit d02198550423 (\"x86/fpu: Improve crypto performance by\nmaking kernel-mode FPU reliably usable in softirqs\"), kernel_fpu_begin()\ncalls fpregs_lock() which uses local_bh_disable() instead of the\nprevious preempt_disable(). This sets SOFTIRQ_OFFSET in preempt_count\nduring the entire EFI runtime service call, causing in_interrupt() to\nreturn true in normal task context.\n\nThe graceful page fault handler efi_crash_gracefully_on_page_fault()\nuses in_interrupt() to bail out for faults in real interrupt context.\nWith SOFTIRQ_OFFSET now set, the handler always bails out, leaving EFI\nfirmware page faults unhandled. This escalates to die() which also sees\nin_interrupt() as true and calls panic(\"Fatal exception in interrupt\"),\nresulting in a hard system freeze. On systems with buggy firmware that\ntriggers page faults during EFI runtime calls (e.g., accessing unmapped\nmemory in GetTime()), this causes an unrecoverable hang instead of the\nexpected graceful EFI_ABORTED recovery.\n\nFix by replacing in_interrupt() with !in_task(). This preserves the\noriginal intent of bailing for interrupts or NMI faults, while no longer\nfalsely triggering from the FPU code path's local_bh_disable().\n\n[ardb: Sashiko spotted that using 'in_hardirq() || in_nmi()' leaves a\n       window where a softirq may be taken before fpregs_lock() is\n       called, but after efi_rts_work.efi_rts_id has been assigned,\n       and any page faults occurring in that window will then be\n       misidentified as having been caused by the firmware. Instead,\n       use !in_task(), which incorporates in_serving_softirq(). ]"}],"providerMetadata":{"dateUpdated":"2026-06-08T15:46:17.224Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/22b365ba1af3d8c6036b8e5112fffe80998b85a0"},{"url":"https://git.kernel.org/stable/c/db155b86d1523e85941f61efd7d7ffb594cc9a29"},{"url":"https://git.kernel.org/stable/c/088f65e206087bf903743bd18417261d7a4c9644"}],"title":"x86/efi: Fix graceful fault handling after FPU softirq changes","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-46290","datePublished":"2026-06-08T15:46:17.224Z","dateReserved":"2026-05-13T15:03:33.110Z","dateUpdated":"2026-06-08T15:46:17.224Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-08 17:16:47","lastModifiedDate":"2026-06-08 17:16:47","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"46290","Ordinal":"1","Title":"x86/efi: Fix graceful fault handling after FPU softirq changes","CVE":"CVE-2026-46290","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"46290","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nx86/efi: Fix graceful fault handling after FPU softirq changes\n\nSince commit d02198550423 (\"x86/fpu: Improve crypto performance by\nmaking kernel-mode FPU reliably usable in softirqs\"), kernel_fpu_begin()\ncalls fpregs_lock() which uses local_bh_disable() instead of the\nprevious preempt_disable(). This sets SOFTIRQ_OFFSET in preempt_count\nduring the entire EFI runtime service call, causing in_interrupt() to\nreturn true in normal task context.\n\nThe graceful page fault handler efi_crash_gracefully_on_page_fault()\nuses in_interrupt() to bail out for faults in real interrupt context.\nWith SOFTIRQ_OFFSET now set, the handler always bails out, leaving EFI\nfirmware page faults unhandled. This escalates to die() which also sees\nin_interrupt() as true and calls panic(\"Fatal exception in interrupt\"),\nresulting in a hard system freeze. On systems with buggy firmware that\ntriggers page faults during EFI runtime calls (e.g., accessing unmapped\nmemory in GetTime()), this causes an unrecoverable hang instead of the\nexpected graceful EFI_ABORTED recovery.\n\nFix by replacing in_interrupt() with !in_task(). This preserves the\noriginal intent of bailing for interrupts or NMI faults, while no longer\nfalsely triggering from the FPU code path's local_bh_disable().\n\n[ardb: Sashiko spotted that using 'in_hardirq() || in_nmi()' leaves a\n       window where a softirq may be taken before fpregs_lock() is\n       called, but after efi_rts_work.efi_rts_id has been assigned,\n       and any page faults occurring in that window will then be\n       misidentified as having been caused by the firmware. Instead,\n       use !in_task(), which incorporates in_serving_softirq(). ]","Type":"Description","Title":"x86/efi: Fix graceful fault handling after FPU softirq changes"}]}}}