Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1959673 (CVE-2021-32606) - CVE-2021-32606 kernel: isotp_setsockopt in net/can/isotp.c allows privilege escalation via use-after-free
Summary: CVE-2021-32606 kernel: isotp_setsockopt in net/can/isotp.c allows privilege e...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2021-32606
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1959674 1960246
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-12 05:01 UTC by Marian Rehak
Modified: 2022-05-17 08:53 UTC (History)
44 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the Linux kernel. A use-after-free flaw in isotp_setsockopt leads to arbitrary kernel execution by overwriting the sk_error_report() pointer which can be misused in order to execute a user-controlled ROP chain to gain root privileges. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
Clone Of:
Environment:
Last Closed: 2021-05-13 12:05:44 UTC
Embargoed:


Attachments (Terms of Use)

Description Marian Rehak 2021-05-12 05:01:13 UTC
The isotp_setsockopt in net/can/isotp.c allows a use-after-free. This leads to arbitrary kernel execution by overwriting the sk_error_report()
pointer, which can be misused in order to execute a user-controlled ROP chain to gain root privileges.

External Reference:

https://www.openwall.com/lists/oss-security/2021/05/11/16

Comment 1 Marian Rehak 2021-05-12 05:01:45 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1959674]


Note You need to log in before you can comment on or make changes to this bug.