Kernel: tap: tap_open(): correctly initialize socket uid next fix of i_uid to current_fsuid
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
A flaw was found in the Linux kernel's TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - a096ccca6e50 ("tun: tun_chr_open(): correctly initialize socket uid"), - 66b2c338adce ("tap: tap_open(): correctly initialize socket uid"), pass "inode->i_uid" to sock_init_data_uid() as the last parameter and that turns out to not be accurate.
Timeline
- CVE published
- Record last updated
Affected versions
- kernel
Version range not reported
- kernel
Version range not reported
- kernel
Version range not reported
- kernel
Version range not reported
- kernel-rt
Version range not reported
- kernel
Version range not reported
- kernel-rt
Version range not reported
- kernel-rt
Version range not reported
- redhat-virtualization-host
Version range not reported