Live data from Hacker News

Linux kernel use-after-free in Netfilter, local privilege escalation

seclists.org

11–20 of 107 posts

Re: Linux kernel use-after-free in Netfilter, local privilege escalation

#11
post #7
post #4

> delete an existing nft rule that uses an nft anonymous set. And an example of the latter operation is an attempt to delete an element from that nft anonymous set after the set gets deleted I'd be very interested to hear how this can be done by an unprivileged user. Try to race set add/removals, sure, but if it depends on the set itself getting deleted, that seems… harder.

on https://bugzilla.redhat.com/show_bug.cgi?id=2196105 a comment suggests that it might only be possible if you have "unprivileged user namespaces" enabled

>a comment suggests that it might only be possible if you have "unprivileged user namespaces" enabled

Which is the default on Ubuntu.

Re: Linux kernel use-after-free in Netfilter, local privilege escalation

#12
post #8

"We developed an exploit that allows unprivileged local users to start a root shell by abusing the above issue. That exploit was shared privately with to assist with fix development. Somebody from the Linux kernel team then emailed the proposed fix to and that email also included a link to download our description of exploitation techniques and our exploit source code. Therefore, according to the linux-distros list p…

I don't think the bug itself is newsworthy. The existence of the exploit code, and the way that it was accidentally published, I think are.

Re: Linux kernel use-after-free in Netfilter, local privilege escalation

#13
post #8

"We developed an exploit that allows unprivileged local users to start a root shell by abusing the above issue. That exploit was shared privately with to assist with fix development. Somebody from the Linux kernel team then emailed the proposed fix to and that email also included a link to download our description of exploitation techniques and our exploit source code. Therefore, according to the linux-distros list p…

I don't think the bug itself is newsworthy. The existence of the exploit code, and the way that it was accidentally published, I think are.

It's exploitable by an unprivileged user on the most popular distro out there (Ubuntu). I would say it's newsworthy.

Re: Linux kernel use-after-free in Netfilter, local privilege escalation

#14
post #8

"We developed an exploit that allows unprivileged local users to start a root shell by abusing the above issue. That exploit was shared privately with to assist with fix development. Somebody from the Linux kernel team then emailed the proposed fix to and that email also included a link to download our description of exploitation techniques and our exploit source code. Therefore, according to the linux-distros list p…

What’s actually reasonable here. I’m all for exploit code becoming public eventually, but I think it’s silly to drop it immediately after a fix has been released, or before, in almost all scenarios (unless there’s been 90+ days or the issue marked as wontfix)

Re: Linux kernel use-after-free in Netfilter, local privilege escalation

#15
post #8

"We developed an exploit that allows unprivileged local users to start a root shell by abusing the above issue. That exploit was shared privately with to assist with fix development. Somebody from the Linux kernel team then emailed the proposed fix to and that email also included a link to download our description of exploitation techniques and our exploit source code. Therefore, according to the linux-distros list p…

What a dumb policy. Why have the disclosure time be so soon? This thing will be in the wild before folks can upgrade if I'm understanding this correctly.

Re: Linux kernel use-after-free in Netfilter, local privilege escalation

#16
post #8

"We developed an exploit that allows unprivileged local users to start a root shell by abusing the above issue. That exploit was shared privately with to assist with fix development. Somebody from the Linux kernel team then emailed the proposed fix to and that email also included a link to download our description of exploitation techniques and our exploit source code. Therefore, according to the linux-distros list p…

What a dumb policy. Why have the disclosure time be so soon? This thing will be in the wild before folks can upgrade if I'm understanding this correctly.

The thing is already in the wild because someone on the private mailing list already accidentally mailed it to the public mailing list.

Re: Linux kernel use-after-free in Netfilter, local privilege escalation

#18
https://nvd.nist.gov/vuln/detail/CVE-2023-32233

The NIST CVE page points back here. Funny.

Nothing I see so far specifically says how far back this goes, but, https://security-tracker.debian.org/tracker/CVE-2023-32233

Seems to go back really far.

Re: Linux kernel use-after-free in Netfilter, local privilege escalation

#19
post #8

"We developed an exploit that allows unprivileged local users to start a root shell by abusing the above issue. That exploit was shared privately with to assist with fix development. Somebody from the Linux kernel team then emailed the proposed fix to and that email also included a link to download our description of exploitation techniques and our exploit source code. Therefore, according to the linux-distros list p…

> but the specific module in question in the patch, nf_tables, is not loaded on my Ubuntu 20.04LTS 5.40 kernel running iptables/ufw at least This doesn't matter since Linux has autoloading of most network modules, and you can cause the modules to be loaded on Ubuntu since it supports unprivileged user/net namespaces. ubuntu:~% grep DISTRIB_DESCRIPTION /etc/lsb-release DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS" ubuntu:~…

Yikes... are other popular distros shipping with unprivileged user namespaces enabled by default?

Re: Linux kernel use-after-free in Netfilter, local privilege escalation

#20
post #7

Earlier quoted context omitted.

on https://bugzilla.redhat.com/show_bug.cgi?id=2196105 a comment suggests that it might only be possible if you have "unprivileged user namespaces" enabled

>a comment suggests that it might only be possible if you have "unprivileged user namespaces" enabled Which is the default on Ubuntu.

It's the default on pretty much any modern Linux system!
Post reply on HN