CVE-2026-31731

{"id": "CVE-2026-31731", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-31731", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-10-16T15:12:52.594804Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.8, "attackVector": "LOCAL", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 1.8}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.8, "attackVector": "LOCAL", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "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": "5a5efdaffda5d23717d9117cf36cda9eafcf2fae", "lessThan": "1a6d2b001eb730d85f00da39ae7db6f3b4edc540", "versionType": "git"}, {"status": "affected", "version": "5a5efdaffda5d23717d9117cf36cda9eafcf2fae", "lessThan": "2dbe93f344f10b432b95a23304006be805c097a1", "versionType": "git"}, {"status": "affected", "version": "5a5efdaffda5d23717d9117cf36cda9eafcf2fae", "lessThan": "c4593f1654f7dea3bcf9bb1851ded86311d4f370", "versionType": "git"}, {"status": "affected", "version": "5a5efdaffda5d23717d9117cf36cda9eafcf2fae", "lessThan": "45b859b0728267a6199ee5002d62e6c6f3e8c89d", "versionType": "git"}], "programFiles": ["drivers/thermal/thermal_core.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.8"}, {"status": "unaffected", "version": "0", "lessThan": "6.8", "versionType": "semver"}, {"status": "unaffected", "version": "6.12.83", "versionType": "semver", "lessThanOrEqual": "6.12.*"}, {"status": "unaffected", "version": "6.18.22", "versionType": "semver", "lessThanOrEqual": "6.18.*"}, {"status": "unaffected", "version": "6.19.12", "versionType": "semver", "lessThanOrEqual": "6.19.*"}, {"status": "unaffected", "version": "7.0", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["drivers/thermal/thermal_core.c"], "defaultStatus": "affected"}]}], "published": "2026-05-01T15:16:35.683", "references": [{"url": "https://git.kernel.org/stable/c/1a6d2b001eb730d85f00da39ae7db6f3b4edc540", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/2dbe93f344f10b432b95a23304006be805c097a1", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/45b859b0728267a6199ee5002d62e6c6f3e8c89d", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/c4593f1654f7dea3bcf9bb1851ded86311d4f370", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-416"}]}, {"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "description": [{"lang": "en", "value": "CWE-362"}]}], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nthermal: core: Address thermal zone removal races with resume\n\nSince thermal_zone_pm_complete() and thermal_zone_device_resume()\nre-initialize the poll_queue delayed work for the given thermal zone,\nthe cancel_delayed_work_sync() in thermal_zone_device_unregister()\nmay miss some already running work items and the thermal zone may\nbe freed prematurely [1].\n\nThere are two failing scenarios that both start with\nrunning thermal_pm_notify_complete() right before invoking\nthermal_zone_device_unregister() for one of the thermal zones.\n\nIn the first scenario, there is a work item already running for\nthe given thermal zone when thermal_pm_notify_complete() calls\nthermal_zone_pm_complete() for that thermal zone and it continues to\nrun when thermal_zone_device_unregister() starts. Since the poll_queue\ndelayed work has been re-initialized by thermal_pm_notify_complete(), the\nrunning work item will be missed by the cancel_delayed_work_sync() in\nthermal_zone_device_unregister() and if it continues to run past the\nfreeing of the thermal zone object, a use-after-free will occur.\n\nIn the second scenario, thermal_zone_device_resume() queued up by\nthermal_pm_notify_complete() runs right after the thermal_zone_exit()\ncalled by thermal_zone_device_unregister() has returned. The poll_queue\ndelayed work is re-initialized by it before cancel_delayed_work_sync() is\ncalled by thermal_zone_device_unregister(), so it may continue to run\nafter the freeing of the thermal zone object, which also leads to a\nuse-after-free.\n\nAddress the first failing scenario by ensuring that no thermal work\nitems will be running when thermal_pm_notify_complete() is called.\nFor this purpose, first move the cancel_delayed_work() call from\nthermal_zone_pm_complete() to thermal_zone_pm_prepare() to prevent\nnew work from entering the workqueue going forward. Next, switch\nover to using a dedicated workqueue for thermal events and update\nthe code in thermal_pm_notify() to flush that workqueue after\nthermal_pm_notify_prepare() has returned which will take care of\nall leftover thermal work already on the workqueue (that leftover\nwork would do nothing useful anyway because all of the thermal zones\nhave been flagged as suspended).\n\nThe second failing scenario is addressed by adding a tz->state check\nto thermal_zone_device_resume() to prevent it from re-initializing\nthe poll_queue delayed work if the thermal zone is going away.\n\nNote that the above changes will also facilitate relocating the suspend\nand resume of thermal zones closer to the suspend and resume of devices,\nrespectively."}, {"lang": "es", "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nthermal: core: Abordar las condiciones de carrera en la eliminaci\u00f3n de zonas t\u00e9rmicas con la reanudaci\u00f3n\n\nDado que thermal_zone_pm_complete() y thermal_zone_device_resume() reinicializan el trabajo retrasado de poll_queue para la zona t\u00e9rmica dada, el cancel_delayed_work_sync() en thermal_zone_device_unregister() puede pasar por alto algunos elementos de trabajo ya en ejecuci\u00f3n y la zona t\u00e9rmica puede ser liberada prematuramente [1].\n\nHay dos escenarios de fallo que ambos comienzan con la ejecuci\u00f3n de thermal_pm_notify_complete() justo antes de invocar thermal_zone_device_unregister() para una de las zonas t\u00e9rmicas.\n\nEn el primer escenario, hay un elemento de trabajo ya en ejecuci\u00f3n para la zona t\u00e9rmica dada cuando thermal_pm_notify_complete() llama a thermal_zone_pm_complete() para esa zona t\u00e9rmica y contin\u00faa ejecut\u00e1ndose cuando thermal_zone_device_unregister() comienza. Dado que el trabajo retrasado de poll_queue ha sido reinicializado por thermal_pm_notify_complete(), el elemento de trabajo en ejecuci\u00f3n ser\u00e1 pasado por alto por el cancel_delayed_work_sync() en thermal_zone_device_unregister() y si contin\u00faa ejecut\u00e1ndose despu\u00e9s de la liberaci\u00f3n del objeto de la zona t\u00e9rmica, ocurrir\u00e1 un uso despu\u00e9s de liberaci\u00f3n.\n\nEn el segundo escenario, thermal_zone_device_resume() encolado por thermal_pm_notify_complete() se ejecuta justo despu\u00e9s de que thermal_zone_exit() llamado por thermal_zone_device_unregister() haya regresado. El trabajo retrasado de poll_queue es reinicializado por este antes de que cancel_delayed_work_sync() sea llamado por thermal_zone_device_unregister(), por lo que puede continuar ejecut\u00e1ndose despu\u00e9s de la liberaci\u00f3n del objeto de la zona t\u00e9rmica, lo que tambi\u00e9n conduce a un uso despu\u00e9s de liberaci\u00f3n.\n\nAbordar el primer escenario de fallo asegurando que ning\u00fan elemento de trabajo t\u00e9rmico estar\u00e1 en ejecuci\u00f3n cuando se llame a thermal_pm_notify_complete(). Para este prop\u00f3sito, primero mover la llamada a cancel_delayed_work() de thermal_zone_pm_complete() a thermal_zone_pm_prepare() para evitar que nuevo trabajo entre en la cola de trabajo en adelante. A continuaci\u00f3n, cambiar a usar una cola de trabajo dedicada para eventos t\u00e9rmicos y actualizar el c\u00f3digo en thermal_pm_notify() para vaciar esa cola de trabajo despu\u00e9s de que thermal_pm_notify_prepare() haya regresado, lo que se encargar\u00e1 de todo el trabajo t\u00e9rmico restante ya en la cola de trabajo (ese trabajo restante no har\u00eda nada \u00fatil de todos modos porque todas las zonas t\u00e9rmicas han sido marcadas como suspendidas).\n\nEl segundo escenario de fallo se aborda a\u00f1adiendo una comprobaci\u00f3n de tz -> state a thermal_zone_device_resume() para evitar que reinicialice el trabajo retrasado de poll_queue si la zona t\u00e9rmica est\u00e1 desapareciendo.\n\nTenga en cuenta que los cambios anteriores tambi\u00e9n facilitar\u00e1n la reubicaci\u00f3n de la suspensi\u00f3n y reanudaci\u00f3n de las zonas t\u00e9rmicas m\u00e1s cerca de la suspensi\u00f3n y reanudaci\u00f3n de los dispositivos, respectivamente."}], "lastModified": "2026-11-11T21:10:00.200", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "4065C9A5-AA06-4747-8C07-BDBC1E8C0051", "versionEndExcluding": "6.12.83", "versionStartIncluding": "6.8"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "C9DF8BCE-36D3-475D-9D21-19E4F02F9029", "versionEndExcluding": "6.18.22", "versionStartIncluding": "6.13"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "0A2B9540-02D5-41B4-B16A-82AF66FD4F36", "versionEndExcluding": "6.19.12", "versionStartIncluding": "6.19"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "F253B622-8837-4245-BCE5-A7BF8FC76A16"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "4AE85AD8-4641-4E7C-A2F4-305E2CD9EE64"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "F666C8D8-6538-46D4-B318-87610DE64C34"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "02259FDA-961B-47BC-AE7F-93D7EC6E90C2"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "58A9FEFF-C040-420D-8F0A-BFDAAA1DF258"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "1D2315C0-D46F-4F85-9754-F9E5E11374A6"}], "operator": "OR"}]}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}