← All Advisories

CVE-2026-46173

Last refreshed2026-10-06

Status: UPDATED  |  Advisory ID: CVE-2026-46173

Key Details

CVECVE-2026-46173
CVSS Score / Version7.8 (High) / CVSS v3.1
Updated2026-09-08
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Proseattack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected productsSiemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, and Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
Classified asCWE-787 (Out-of-bounds Write)

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP
SiemensSIPLUS S7-1500 CPU 1518-4 PN/DP MFP
SubsystemsGeneral OT
SectorsMultiple

What to Know

In the Linux kernel, the following vulnerability has been resolved:

exit: prevent preemption of oopsing TASK_DEAD task

When an already-exiting task oopses, make_task_dead() currently calls

do_task_dead() with preemption enabled. That is forbidden:

do_task_dead() calls __schedule(), which has a comment saying "WARNING:

must be called with preemption disabled!".

If an oopsing task is preempted in do_task_dead(), between becoming

TASK_DEAD and entering the scheduler explicitly, bad things happen:

finish_task_switch() assumes that once the scheduler has switched away

from a TASK_DEAD task, the task can never run again and its stack is no

longer needed; but that assumption apparently doesn't hold if the dead

task was preempted (the SM_PREEMPT case).

This means that the scheduler ends up repeatedly dropping references on

the dead task's stack, which can lead to use-after-free or double-free

of the entire task stack; in other words, two tasks can end up running

on the same stack, resulting in various kinds of memory corruption.

(This does not just affect "recursively oopsing" tasks; it is enough to

oops once during task exit, for example in a file_operations::release

handler) (NVD)

What to Do

Monitor Siemens's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-46173
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-46173