CVE-2026-46290
In the Linux kernel, the following vulnerability has been resolved:
x86/efi: Fix graceful fault handling after FPU softirq changes
Since commit d02198550423 ("x86/fpu: Improve crypto performance by making kernel-mode FPU reliably usable in softirqs"), kernel_fpu_begin() calls fpregs_lock() which uses local_bh_disable() instead of the previous preempt_disable(). This sets SOFTIRQ_OFFSET in preempt_count during the entire EFI runtime service call, causing in_interrupt() to return true in normal task context.
The graceful page fault handler efi_crash_gracefully_on_page_fault() uses in_interrupt() to bail out for faults in real interrupt context.
Leer descripción completaMostrar menos
With SOFTIRQ_OFFSET now set, the handler always bails out, leaving EFI firmware page faults unhandled. This escalates to die() which also sees in_interrupt() as true and calls panic("Fatal exception in interrupt"), resulting in a hard system freeze. On systems with buggy firmware that triggers page faults during EFI runtime calls (e.g., accessing unmapped memory in GetTime()), this causes an unrecoverable hang instead of the expected graceful EFI_ABORTED recovery.
Fix by replacing in_interrupt() with !in_task(). This preserves the original intent of bailing for interrupts or NMI faults, while no longer falsely triggering from the FPU code path's local_bh_disable().
Detalles técnicos trazas, registros y código del informe original
[ardb: Sashiko spotted that using 'in_hardirq() || in_nmi()' leaves a
window where a softirq may be taken before fpregs_lock() is
called, but after efi_rts_work.efi_rts_id has been assigned,
and any page faults occurring in that window will then be
misidentified as having been caused by the firmware. Instead,
use !in_task(), which incorporates in_serving_softirq(). ]CVSS
- Versión: 3.1
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Puntuación base: 5.5
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.16%
- Percentil entre todas las CVEs puntuadas: 5
- Fecha de la puntuación: 5/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
Tecnologías afectadas (1)
CWE
- NVD-CWE-noinfo
Referencias
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-46290",
"cveTags": [],
"metrics": {
"cvssMetricV31": [
{
"type": "Primary",
"source": "nvd@nist.gov",
"cvssData": {
"scope": "UNCHANGED",
"version": "3.1",
"baseScore": 5.5,
"attackVector": "LOCAL",
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"integrityImpact": "NONE",
"userInteraction": "NONE",
"attackComplexity": "LOW",
"availabilityImpact": "HIGH",
"privilegesRequired": "LOW",
"confidentialityImpact": "NONE"
},
"impactScore": 3.6,
"exploitabilityScore": 1.8
}
]
},
"affected": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"affectedData": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "d02198550423a0b695e7a24ec77153209ad45b09",
"lessThan": "22b365ba1af3d8c6036b8e5112fffe80998b85a0",
"versionType": "git"
},
{
"status": "affected",
"version": "d02198550423a0b695e7a24ec77153209ad45b09",
"lessThan": "db155b86d1523e85941f61efd7d7ffb594cc9a29",
"versionType": "git"
},
{
"status": "affected",
"version": "d02198550423a0b695e7a24ec77153209ad45b09",
"lessThan": "088f65e206087bf903743bd18417261d7a4c9644",
"versionType": "git"
}
],
"programFiles": [
"arch/x86/platform/efi/quirks.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "6.15"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.15",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.18.30",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.0.7",
"versionType": "semver",
"lessThanOrEqual": "7.0.*"
},
{
"status": "unaffected",
"version": "7.1",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"arch/x86/platform/efi/quirks.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-06-08T17:16:47.230",
"references": [
{
"url": "https://git.kernel.org/stable/c/088f65e206087bf903743bd18417261d7a4c9644",
"tags": [
"Patch"
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/22b365ba1af3d8c6036b8e5112fffe80998b85a0",
"tags": [
"Patch"
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/db155b86d1523e85941f61efd7d7ffb594cc9a29",
"tags": [
"Patch"
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Analyzed",
"weaknesses": [
{
"type": "Primary",
"source": "nvd@nist.gov",
"description": [
{
"lang": "en",
"value": "NVD-CWE-noinfo"
}
]
}
],
"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(). ]"
},
{
"lang": "es",
"value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nx86/efi: Corrección del manejo elegante de fallos después de los cambios en softirq de FPU\n\nDesde el commit d02198550423 ('x86/fpu: Mejorar el rendimiento criptográfico haciendo que la FPU en modo kernel sea utilizable de forma fiable en softirqs'), kernel_fpu_begin() llama a fpregs_lock() que usa local_bh_disable() en lugar del preempt_disable() anterior. Esto establece SOFTIRQ_OFFSET en preempt_count durante toda la llamada al servicio de tiempo de ejecución de EFI, haciendo que in_interrupt() devuelva verdadero en un contexto de tarea normal.\n\nEl gestor elegante de fallos de página efi_crash_gracefully_on_page_fault() usa in_interrupt() para salir de los fallos en un contexto de interrupción real. Con SOFTIRQ_OFFSET ahora establecido, el gestor siempre sale, dejando los fallos de página del firmware EFI sin manejar. Esto escala a die() que también ve in_interrupt() como verdadero y llama a panic('Excepción fatal en interrupción'), resultando en una congelación dura del sistema. En sistemas con firmware defectuoso que dispara fallos de página durante las llamadas de tiempo de ejecución de EFI (p. ej., acceder a memoria no mapeada en GetTime()), esto causa un cuelgue irrecuperable en lugar de la recuperación elegante EFI_ABORTED esperada.\n\nSolución reemplazando in_interrupt() con !in_task(). Esto preserva la intención original de salir por interrupciones o fallos NMI, mientras ya no se dispara falsamente desde el local_bh_disable() de la ruta de código de la FPU.\n\n[ardb: Sashiko detectó que usar 'in_hardirq() || in_nmi()' deja una ventana donde un softirq puede ser tomado antes de que se llame a fpregs_lock(), pero después de que efi_rts_work.efi_rts_id haya sido asignado, y cualquier fallo de página que ocurra en esa ventana será entonces mal identificado como causado por el firmware. En su lugar, use !in_task(), que incorpora in_serving_softirq(). ]"
}
],
"lastModified": "2026-07-23T08:10:00.137",
"configurations": [
{
"nodes": [
{
"negate": false,
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"vulnerable": true,
"matchCriteriaId": "7A99D29F-3622-4F26-9E29-80DF70FFF2B1",
"versionEndExcluding": "6.18.30",
"versionStartIncluding": "6.15"
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"vulnerable": true,
"matchCriteriaId": "D0893CA7-9AE6-4DFE-AC75-48967D73AD8E",
"versionEndExcluding": "7.0.7",
"versionStartIncluding": "6.19"
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*",
"vulnerable": true,
"matchCriteriaId": "B1EF7059-E670-45F4-B422-54C40FA86390"
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*",
"vulnerable": true,
"matchCriteriaId": "0D38F0BF-A728-4133-A358-D44A2F7EE6D6"
}
],
"operator": "OR"
}
]
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}