home.social

#fragnesia — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #fragnesia, aggregated by home.social.

fetched live
  1. #Linux got bitten by crypto-related page cache vulnerabilities in recent weeks. They had rather boring names: #CopyFail #DirtyFrag #Fragnesia

    The #FreeBSD community is fixing this by naming their own bug of this class #BUMSRAKETE.

    (Now, if you ran the name through a translator and are questioning its legitimacy: It's as real as the person that inspired the bug report's style, unfortunately.)

    bumsrake.de/

    #PrivilegeEscalation #security #vulnerability

  2. #Linux got bitten by crypto-related page cache vulnerabilities in recent weeks. They had rather boring names: #CopyFail #DirtyFrag #Fragnesia

    The #FreeBSD community is fixing this by naming their own bug of this class #BUMSRAKETE.

    (Now, if you ran the name through a translator and are questioning its legitimacy: It's as real as the person that inspired the bug report's style, unfortunately.)

    bumsrake.de/

    #PrivilegeEscalation #security #vulnerability

  3. #Linux got bitten by crypto-related page cache vulnerabilities in recent weeks. They had rather boring names: #CopyFail #DirtyFrag #Fragnesia

    The #FreeBSD community is fixing this by naming their own bug of this class #BUMSRAKETE.

    (Now, if you ran the name through a translator and are questioning its legitimacy: It's as real as the person that inspired the bug report's style, unfortunately.)

    bumsrake.de/

    #PrivilegeEscalation #security #vulnerability

  4. #Linux got bitten by crypto-related page cache vulnerabilities in recent weeks. They had rather boring names: #CopyFail #DirtyFrag #Fragnesia

    The #FreeBSD community is fixing this by naming their own bug of this class #BUMSRAKETE.

    (Now, if you ran the name through a translator and are questioning its legitimacy: It's as real as the person that inspired the bug report's style, unfortunately.)

    bumsrake.de/

    #PrivilegeEscalation #security #vulnerability

  5. #Linux got bitten by crypto-related page cache vulnerabilities in recent weeks. They had rather boring names: #CopyFail #DirtyFrag #Fragnesia

    The #FreeBSD community is fixing this by naming their own bug of this class #BUMSRAKETE.

    (Now, if you ran the name through a translator and are questioning its legitimacy: It's as real as the person that inspired the bug report's style, unfortunately.)

    bumsrake.de/

    #PrivilegeEscalation #security #vulnerability

  6. Aktuelle Sicherheitslage - CopyFail und Co.

    Aktuelle Sicherheitslücken wie: CopyFail, DirtyFrag, Fragnesia und ssh-keysign-pwn verunsichern Linux-Nutzer:innen. Dieser Artikel ordnet ein und gibt Entwarnung.
    — von @ralfhersel im @gnulinux

    🔐 gnulinux.ch/aktuelle-sicherhei

    #linux #itsicherheit #copyfail #dirtyfrag #fragnesia #sshkeysignpwn #entwarnung #opensource #software #itsec

  7. Aktuelle Sicherheitslage - CopyFail und Co.

    Aktuelle Sicherheitslücken wie: CopyFail, DirtyFrag, Fragnesia und ssh-keysign-pwn verunsichern Linux-Nutzer:innen. Dieser Artikel ordnet ein und gibt Entwarnung.
    — von @ralfhersel im @gnulinux

    🔐 gnulinux.ch/aktuelle-sicherhei

    #linux #itsicherheit #copyfail #dirtyfrag #fragnesia #sshkeysignpwn #entwarnung #opensource #software #itsec

  8. Aktuelle Sicherheitslage - CopyFail und Co.

    Aktuelle Sicherheitslücken wie: CopyFail, DirtyFrag, Fragnesia und ssh-keysign-pwn verunsichern Linux-Nutzer:innen. Dieser Artikel ordnet ein und gibt Entwarnung.
    — von @ralfhersel im @gnulinux

    🔐 gnulinux.ch/aktuelle-sicherhei

    #linux #itsicherheit #copyfail #dirtyfrag #fragnesia #sshkeysignpwn #entwarnung #opensource #software #itsec

  9. Aktuelle Sicherheitslage - CopyFail und Co.

    Aktuelle Sicherheitslücken wie: CopyFail, DirtyFrag, Fragnesia und ssh-keysign-pwn verunsichern Linux-Nutzer:innen. Dieser Artikel ordnet ein und gibt Entwarnung.
    — von @ralfhersel im @gnulinux

    🔐 gnulinux.ch/aktuelle-sicherhei

    #linux #itsicherheit #copyfail #dirtyfrag #fragnesia #sshkeysignpwn #entwarnung #opensource #software #itsec

  10. Aktuelle Sicherheitslage - CopyFail und Co.

    Aktuelle Sicherheitslücken wie: CopyFail, DirtyFrag, Fragnesia und ssh-keysign-pwn verunsichern Linux-Nutzer:innen. Dieser Artikel ordnet ein und gibt Entwarnung.
    — von @ralfhersel im @gnulinux

    🔐 gnulinux.ch/aktuelle-sicherhei

    #linux #itsicherheit #copyfail #dirtyfrag #fragnesia #sshkeysignpwn #entwarnung #opensource #software #itsec

  11. Aktuelle Sicherheitslage - CopyFail und Co.

    Aktuelle Sicherheitslücken wie: CopyFail, DirtyFrag, Fragnesia und ssh-keysign-pwn verunsichern Linux-Nutzer:innen. Dieser Artikel ordnet ein und gibt Entwarnung.

    #CopyFail #DirtyFrag #Fragnesia #Linux

    gnulinux.ch/aktuelle-sicherhei

  12. Aktuelle Sicherheitslage - CopyFail und Co.

    Aktuelle Sicherheitslücken wie: CopyFail, DirtyFrag, Fragnesia und ssh-keysign-pwn verunsichern Linux-Nutzer:innen. Dieser Artikel ordnet ein und gibt Entwarnung.

    #CopyFail #DirtyFrag #Fragnesia #Linux

    gnulinux.ch/aktuelle-sicherhei

  13. Aktuelle Sicherheitslage - CopyFail und Co.

    Aktuelle Sicherheitslücken wie: CopyFail, DirtyFrag, Fragnesia und ssh-keysign-pwn verunsichern Linux-Nutzer:innen. Dieser Artikel ordnet ein und gibt Entwarnung.

    #CopyFail #DirtyFrag #Fragnesia #Linux

    gnulinux.ch/aktuelle-sicherhei

  14. Aktuelle Sicherheitslage - CopyFail und Co.

    Aktuelle Sicherheitslücken wie: CopyFail, DirtyFrag, Fragnesia und ssh-keysign-pwn verunsichern Linux-Nutzer:innen. Dieser Artikel ordnet ein und gibt Entwarnung.

    #CopyFail #DirtyFrag #Fragnesia #Linux

    gnulinux.ch/aktuelle-sicherhei

  15. Aktuelle Sicherheitslage - CopyFail und Co.

    Aktuelle Sicherheitslücken wie: CopyFail, DirtyFrag, Fragnesia und ssh-keysign-pwn verunsichern Linux-Nutzer:innen. Dieser Artikel ordnet ein und gibt Entwarnung.

    #CopyFail #DirtyFrag #Fragnesia #Linux

    gnulinux.ch/aktuelle-sicherhei

  16. How do we know when #Fragnesia is fully patched?

  17. Has anybody an explanation why this time it takes longer to patch the kernel for fragnesia esp. for bookworm and trixie in debian?
    I get that sid is patched first because it's unstable. e: trixie is now fixed, too

    security-tracker.debian.org/tr

    It's NOT a complaint but getting to know the processes.
    Thanks!
    e: and a huge thanks to the people maintaining debian and the other distributions ❤️

    #linux #debian #bookworm #trixie #fragnesia

  18. Has anybody an explanation why this time it takes longer to patch the kernel for fragnesia esp. for bookworm and trixie in debian?
    I get that sid is patched first because it's unstable. e: trixie is now fixed, too

    security-tracker.debian.org/tr

    It's NOT a complaint but getting to know the processes.
    Thanks!
    e: and a huge thanks to the people maintaining debian and the other distributions ❤️

    #linux #debian #bookworm #trixie #fragnesia

  19. Has anybody an explanation why this time it takes longer to patch the kernel for fragnesia esp. for bookworm and trixie in debian?
    I get that sid is patched first because it's unstable. e: trixie is now fixed, too

    security-tracker.debian.org/tr

    It's NOT a complaint but getting to know the processes.
    Thanks!
    e: and a huge thanks to the people maintaining debian and the other distributions ❤️

    #linux #debian #bookworm #trixie #fragnesia

  20. Has anybody an explanation why this time it takes longer to patch the kernel for fragnesia esp. for bookworm and trixie in debian?
    I get that sid is patched first because it's unstable. e: trixie is now fixed, too

    security-tracker.debian.org/tr

    It's NOT a complaint but getting to know the processes.
    Thanks!
    e: and a huge thanks to the people maintaining debian and the other distributions ❤️

    #linux #debian #bookworm #trixie #fragnesia

  21. Has anybody an explanation why this time it takes longer to patch the kernel for fragnesia esp. for bookworm and trixie in debian?
    I get that sid is patched first because it's unstable. e: trixie is now fixed, too

    security-tracker.debian.org/tr

    It's NOT a complaint but getting to know the processes.
    Thanks!
    e: and a huge thanks to the people maintaining debian and the other distributions ❤️

    #linux #debian #bookworm #trixie #fragnesia

  22. #Debian still without a #fragnesia patch. Not funny anmore!
    (I know that there is a mitigation for systems without ipsec)
    security-tracker.debian.org/tr

  23. #Debian still without a #fragnesia patch. Not funny anmore!
    (I know that there is a mitigation for systems without ipsec)
    security-tracker.debian.org/tr

  24. #Debian still without a #fragnesia patch. Not funny anmore!
    (I know that there is a mitigation for systems without ipsec)
    security-tracker.debian.org/tr

  25. #Debian still without a #fragnesia patch. Not funny anmore!
    (I know that there is a mitigation for systems without ipsec)
    security-tracker.debian.org/tr

  26. Once again the cluster has been upgraded to catch the latest fixes for #DirtyFrag and #Fragnesia. I ought to get to work on that Ansible playbook.

  27. Please read this important update from #CheckPoint:

    Check Point Response to CVE-2026-31431 (Copy Fail), CVE-2026-43284, CVE-2026-43500 (Dirty Frag) and CVE-2026-46300 (Fragnesia)

    support.checkpoint.com/results

    #copyfail #dirtyfrag #fragnesia

  28. Please read this important update from #CheckPoint:

    Check Point Response to CVE-2026-31431 (Copy Fail), CVE-2026-43284, CVE-2026-43500 (Dirty Frag) and CVE-2026-46300 (Fragnesia)

    support.checkpoint.com/results

    #copyfail #dirtyfrag #fragnesia

  29. Please read this important update from #CheckPoint:

    Check Point Response to CVE-2026-31431 (Copy Fail), CVE-2026-43284, CVE-2026-43500 (Dirty Frag) and CVE-2026-46300 (Fragnesia)

    support.checkpoint.com/results

    #copyfail #dirtyfrag #fragnesia

  30. Please read this important update from #CheckPoint:

    Check Point Response to CVE-2026-31431 (Copy Fail), CVE-2026-43284, CVE-2026-43500 (Dirty Frag) and CVE-2026-46300 (Fragnesia)

    support.checkpoint.com/results

    #copyfail #dirtyfrag #fragnesia

  31. Please read this important update from #CheckPoint:

    Check Point Response to CVE-2026-31431 (Copy Fail), CVE-2026-43284, CVE-2026-43500 (Dirty Frag) and CVE-2026-46300 (Fragnesia)

    support.checkpoint.com/results

    #copyfail #dirtyfrag #fragnesia

  32. Is it safe to update packages on OpenSUSE Tumbleweed with the LPEs unpatched?
    Running kernel 7.0.6-1-default
    I have two third-party repos enabled: packman (for codecs) and librewolf.
    #Fragnesia #DirtyFrag

  33. I've finally finished pushing the latest update for #Gentoo Distribution Kernels, and requested their stabilization. This includes upstream releases 7.0.9, 6.18.32, 6.12.90 and 6.6.140; and Gentoo patch bumps 6.1.173_p1, 5.15.207_p1 and 5.10.256_p1.

    All of these contain the v5 #Fragnesia patch. And yes, while the exploit is in the wild, upstream still hasn't merged a fix to the mainline kernel, let alone all the LTS branches. Of course, the patch keeps covering more holes, but it would really be preferable to do that as a followup instead of leaving people vulnerable and forcing us to keep rebasing it.

    They also include a few reverts in 6.18 and 6.6 for broken PowerPC backports that upstream didn't apparently test. 🤷

    We're doing our best, but I'd still recommend running the latest 7.0.x kernel, or LTS 6.18.x, because upstream is far from reliable with the backports.

    #Linux

  34. I've finally finished pushing the latest update for #Gentoo Distribution Kernels, and requested their stabilization. This includes upstream releases 7.0.9, 6.18.32, 6.12.90 and 6.6.140; and Gentoo patch bumps 6.1.173_p1, 5.15.207_p1 and 5.10.256_p1.

    All of these contain the v5 #Fragnesia patch. And yes, while the exploit is in the wild, upstream still hasn't merged a fix to the mainline kernel, let alone all the LTS branches. Of course, the patch keeps covering more holes, but it would really be preferable to do that as a followup instead of leaving people vulnerable and forcing us to keep rebasing it.

    They also include a few reverts in 6.18 and 6.6 for broken PowerPC backports that upstream didn't apparently test. 🤷

    We're doing our best, but I'd still recommend running the latest 7.0.x kernel, or LTS 6.18.x, because upstream is far from reliable with the backports.

    #Linux

  35. I've finally finished pushing the latest update for #Gentoo Distribution Kernels, and requested their stabilization. This includes upstream releases 7.0.9, 6.18.32, 6.12.90 and 6.6.140; and Gentoo patch bumps 6.1.173_p1, 5.15.207_p1 and 5.10.256_p1.

    All of these contain the v5 #Fragnesia patch. And yes, while the exploit is in the wild, upstream still hasn't merged a fix to the mainline kernel, let alone all the LTS branches. Of course, the patch keeps covering more holes, but it would really be preferable to do that as a followup instead of leaving people vulnerable and forcing us to keep rebasing it.

    They also include a few reverts in 6.18 and 6.6 for broken PowerPC backports that upstream didn't apparently test. 🤷

    We're doing our best, but I'd still recommend running the latest 7.0.x kernel, or LTS 6.18.x, because upstream is far from reliable with the backports.

    #Linux

  36. I've finally finished pushing the latest update for #Gentoo Distribution Kernels, and requested their stabilization. This includes upstream releases 7.0.9, 6.18.32, 6.12.90 and 6.6.140; and Gentoo patch bumps 6.1.173_p1, 5.15.207_p1 and 5.10.256_p1.

    All of these contain the v5 #Fragnesia patch. And yes, while the exploit is in the wild, upstream still hasn't merged a fix to the mainline kernel, let alone all the LTS branches. Of course, the patch keeps covering more holes, but it would really be preferable to do that as a followup instead of leaving people vulnerable and forcing us to keep rebasing it.

    They also include a few reverts in 6.18 and 6.6 for broken PowerPC backports that upstream didn't apparently test. 🤷

    We're doing our best, but I'd still recommend running the latest 7.0.x kernel, or LTS 6.18.x, because upstream is far from reliable with the backports.

    #Linux

  37. I've finally finished pushing the latest update for #Gentoo Distribution Kernels, and requested their stabilization. This includes upstream releases 7.0.9, 6.18.32, 6.12.90 and 6.6.140; and Gentoo patch bumps 6.1.173_p1, 5.15.207_p1 and 5.10.256_p1.

    All of these contain the v5 #Fragnesia patch. And yes, while the exploit is in the wild, upstream still hasn't merged a fix to the mainline kernel, let alone all the LTS branches. Of course, the patch keeps covering more holes, but it would really be preferable to do that as a followup instead of leaving people vulnerable and forcing us to keep rebasing it.

    They also include a few reverts in 6.18 and 6.6 for broken PowerPC backports that upstream didn't apparently test. 🤷

    We're doing our best, but I'd still recommend running the latest 7.0.x kernel, or LTS 6.18.x, because upstream is far from reliable with the backports.

    #Linux

  38. The Register quoted Wiz putting it plainly: “The Linux networking stack is starting to look less like infrastructure and more like a root exploit vending machine.”

    byteiota.com/fragnesia-cve-202

    #copyfail #dirtyfrag #fragnesia #linux

  39. The Register quoted Wiz putting it plainly: “The Linux networking stack is starting to look less like infrastructure and more like a root exploit vending machine.”

    byteiota.com/fragnesia-cve-202

    #copyfail #dirtyfrag #fragnesia #linux

  40. The Register quoted Wiz putting it plainly: “The Linux networking stack is starting to look less like infrastructure and more like a root exploit vending machine.”

    byteiota.com/fragnesia-cve-202

    #copyfail #dirtyfrag #fragnesia #linux

  41. The Register quoted Wiz putting it plainly: “The Linux networking stack is starting to look less like infrastructure and more like a root exploit vending machine.”

    byteiota.com/fragnesia-cve-202

    #copyfail #dirtyfrag #fragnesia #linux

  42. The Register quoted Wiz putting it plainly: “The Linux networking stack is starting to look less like infrastructure and more like a root exploit vending machine.”

    byteiota.com/fragnesia-cve-202

    #copyfail #dirtyfrag #fragnesia #linux