Generative Model Unlearning: A Survey through Target Events, Unlearning Operators, and Evaluation Protocols

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2507.19894v2 Announce Type: replace Abstract: With the rapid advancement of generative models, privacy, copyright, safety, and reliability risks have attracted growing attention. To mitigate these risks, machine unlearning has been increasingly adapted from traditional classification models to generative settings. Despite notable progress, existing studies remain fragmented in their target definitions, unlearning mechanisms, and evaluation protocols, making objective comparison difficult across models, modalities, and applications. Moreover, modality-specific surveys often overlook the shared structure of Generative Model Unlearning (GenMU). To address this gap, we provide a comprehensive review of GenMU and formulate it as target-constrained distributional projection: given a target event, an unlearning operator transforms the generative distribution to suppress target-related outputs while preserving useful behavior and controlling operator cost. Under this framework, an unlearning request is specified by a target event, implemented through an unlearning operator, and assessed by empirical evidence over target suppression, distribution preservation, and operator cost. We further reorganize existing GenMU studies under this view. From this perspective, we provide the first explicit and unified account of how GenMU connects to mainstream applications, including privacy protection, copyright and style protection, safety alignment, hallucination mitigation, and deployment defense. Finally, we identify key open problems and future directions toward reliable, scalable, …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2507.19894
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.