Bug 2018225 (CVE-2021-0935) - CVE-2021-0935 kernel: out-of-bounds write due to a use-after-free in ip6_xmit() in ip6_output.c
Summary: CVE-2021-0935 kernel: out-of-bounds write due to a use-after-free in ip6_xmit...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2021-0935
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2018226
Blocks: 2018227
TreeView+ depends on / blocked
 
Reported: 2021-10-28 14:45 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-11-02 20:55 UTC (History)
45 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
An out of bounds write flaw in the Linux kernel's IPv6 protocol was found. A local user could use this flaw to crash the system or escalate their privileges on the system.
Clone Of:
Environment:
Last Closed: 2021-11-02 14:08:34 UTC


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2021-10-28 14:45:55 UTC
In ip6_xmit of ip6_output.c, there is a possible out of bounds write due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-168607263References: Upstream kernel.

References:
https://source.android.com/security/bulletin/pixel/2021-10-01
https://android.googlesource.com/kernel/common/+/2f987a76a97773beafbc615b9c4d8fe79129a7f4

Comment 1 Guilherme de Almeida Suckevicz 2021-10-28 14:47:12 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2018226]

Comment 3 Product Security DevOps Team 2021-11-02 14:08:34 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2021-0935

Comment 4 Justin M. Forbes 2021-11-02 20:55:03 UTC
This was fixed for Fedora with the 4.15.15 stable update.


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