Does this have a CVE yet ?

[wmealing]

If you're interested in the process, it is documented in kernel and you can see it here:

https://lwn.net/ml/linux-kernel/2024021314-unwelcome-shrill-690e@gregkh/

[fdellwing]

This is CVE-2023-6546 and this repo is sus.

[YuriiCrimson]

This is CVE-2023-6546 and this repo is sus.

this not CVE 2023 6546

[lcfr-eth]

This is CVE-2023-6546 and this repo is sus.

this not CVE 2023 6546

Trigger looks the same calling GSMIOC_SETCONF with a dangling tty reference.

also interesting you happened to find/use the same KASLR leak that the author of CVE-2023-6546 which was unknown publicly previous to his exploit? (XEN_NOTE)

https://github.com/Nassim-Asrir/ZDI-24-020/tree/main

[YuriiCrimson]

This is CVE-2023-6546 and this repo is sus.

this not CVE 2023 6546

Trigger looks the same calling GSMIOC_SETCONF with a dangling tty reference.

also interesting you happened to find/use the same KASLR leak that the author of CVE-2023-6546 which was unknown publicly previous to his exploit? (XEN_NOTE)

https://github.com/Nassim-Asrir/ZDI-24-020/tree/main yes but race condition in gsm dlci config

[YuriiCrimson]

And now i leaked another exploit

[ecki]

Is that line discipline a module and can be blacklisted?

[ecki]

Is that line discipline a module and can be blacklisted?

Yes, you can alias tty-ldisc-21 off

What I also found is that sysctl dev.tty.ldisc_autoload=0 looks like a good general hardening method in this case.

[YuriiCrimson]

i think it is done