# Status on copy.fail mitigations?
**URL:** https://forum.yunohost.org/t/status-on-copy-fail-mitigations/42161
**Category:** Discuss
**Tags:** english
**Created:** [April 30, 2026, 1:15pm UTC](https://forum.yunohost.org/t/status-on-copy-fail-mitigations/42161 "2026-04-30T13:15:33Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@Thibaultmol](https://forum.yunohost.org/u/Thibaultmol)
#### Post date: [April 30, 2026, 1:15pm UTC](https://forum.yunohost.org/t/status-on-copy-fail-mitigations/42161/1 "2026-04-30T13:15:33Z")
### Discuss
Curious if someone is working on the changes needed to fix [https://copy.fail/](https://copy.fail/) or is it just a case ‘waiting on debian to fix it’ kind of issue? (I assume it’s the latter, but figured it’d open a discussion thread just in case)
---
### Author:  [@gemlog](https://forum.yunohost.org/u/gemlog)
#### Post date: [April 30, 2026, 1:26pm UTC](https://forum.yunohost.org/t/status-on-copy-fail-mitigations/42161/2 "2026-04-30T13:26:59Z")
I wonder too. I suppose it’s prudent to follow the advice in the meantime?
**For immediate mitigation** , block AF\_ALG socket creation via seccomp or blacklist the algif\_aead module:
```auto
echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif-aead.conf
rmmod algif_aead 2>/dev/null
```
> **[Copy Fail: 732 Bytes to Root on Every Major Linux Distribution. - Xint](https://xint.io/blog/copy-fail-linux-distributions)**
>
> Xint Code disclosed CVE-2026-31431, an authencesn scratch-write bug chaining AF\_ALG + splice() into a 4-byte page cache write. A 732-byte PoC gets root on Ubuntu, Amazon Linux, RHEL, SUSE. | AI for Security, Vulnerability Research
---
### Author:  [@orhtej2](https://forum.yunohost.org/u/orhtej2)
#### Post date: [April 30, 2026, 2:04pm UTC](https://forum.yunohost.org/t/status-on-copy-fail-mitigations/42161/3 "2026-04-30T14:04:04Z")
We’re waiting for an upstream fix: [CVE-2026-31431](https://security-tracker.debian.org/tracker/CVE-2026-31431)
---
### Author:  [@KMK](https://forum.yunohost.org/u/KMK)
#### Post date: [May 1, 2026, 8:23pm UTC](https://forum.yunohost.org/t/status-on-copy-fail-mitigations/42161/4 "2026-05-01T20:23:28Z")
The fix is now available, just update your system
---
### Author:  [@steko](https://forum.yunohost.org/u/steko)
#### Post date: [May 2, 2026, 7:45am UTC](https://forum.yunohost.org/t/status-on-copy-fail-mitigations/42161/5 "2026-05-02T07:45:35Z")
Update AND reboot, it seems. Otherwise the affected kernel will keep running.
---
### Author:  [@JfmbLinux](https://forum.yunohost.org/u/JfmbLinux)
#### Post date: [May 19, 2026, 10:34pm UTC](https://forum.yunohost.org/t/status-on-copy-fail-mitigations/42161/6 "2026-05-19T22:34:52Z")
The update of yunohost from 12.1.3.9 to 12.1.40 went well, but the diagnosis indicates an error.
> Le paquet système ‘kernel’ est actuellement dans la version ‘6.1.0-48-amd64’, qui est vulnérable à un problème de sécurité MAJEUR : CVE-2026-31431, 31433, 43284 and 43500 a.k.a ‘Copy Fail’ and ‘Dirty Frag’ / CRITICAL Privilege escalations from any local user account. Il est recommandé de passer dès que possible à la version ‘{‘bookworm’: ‘6.1.170-3’, ‘trixie’: ‘6.12.86-1’}’. Plus d’informations : [https://copy.fail/](https://copy.fail/), [GitHub - V4bel/dirtyfrag · GitHub](https://github.com/V4bel/dirtyfrag), [CVE-2026-31431](https://security-tracker.debian.org/tracker/CVE-2026-31431), [CVE-2026-31433](https://security-tracker.debian.org/tracker/CVE-2026-31433), [CVE-2026-43284](https://security-tracker.debian.org/tracker/CVE-2026-43284), [CVE-2026-43500](https://security-tracker.debian.org/tracker/CVE-2026-43500)
How do I solve this?
---
### Author:  [@antoine.courtois](https://forum.yunohost.org/u/antoine.courtois)
#### Post date: [May 20, 2026, 6:37am UTC](https://forum.yunohost.org/t/status-on-copy-fail-mitigations/42161/7 "2026-05-20T06:37:27Z")
Bonjour, Pareil chez moi MAJ en 12.1.40 et j’ai l’alerte du kernel. Le kernel a été mis à jour le 15 mai en version 6.1.172-1. la version 6.1.170-3 n’est pas disponible à priori ?
---
### Author:  [@JfmbLinux](https://forum.yunohost.org/u/JfmbLinux)
#### Post date: [May 20, 2026, 8:23am UTC](https://forum.yunohost.org/t/status-on-copy-fail-mitigations/42161/8 "2026-05-20T08:23:39Z")
Salut,
Je pense qu’il va y avoir une nouvelle mise à jour pour corriger cette erreur.
---
### Author:  [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [May 20, 2026, 3:16pm UTC](https://forum.yunohost.org/t/status-on-copy-fail-mitigations/42161/9 "2026-05-20T15:16:14Z")
The diagnosis check should be fixed in 12.1.40.1, cf [Kernel version detection matches debian kernel version, not mainline · Issue #2803 · YunoHost/issues · GitHub](https://github.com/YunoHost/issues/issues/2803)
---
### Author:  [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [June 12, 2026, 2:50pm UTC](https://forum.yunohost.org/t/status-on-copy-fail-mitigations/42161/10 "2026-06-12T14:50:27Z")
24 posts were split to a new topic: [Upgrade kernel 4.x vers 6.x pour pallier à copy.fail](https://forum.yunohost.org/t/upgrade-kernel-4-x-vers-6-x-pour-pallier-a-copy-fail/42441)