Bug 1582346 (CVE-2018-10840) - CVE-2018-10840 kernel: Heap-based buffer overflow in fs/ext4/xattr.c:ext4_xattr_set_entry() with crafted ext4 image
Summary: CVE-2018-10840 kernel: Heap-based buffer overflow in fs/ext4/xattr.c:ext4_xat...
Status: NEW
Alias: CVE-2018-10840
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: impact=moderate,public=20180411,repor...
Keywords: Security
Depends On: 1582347 1584987 1584988 1582348 1584985 1584986 1584989 1584990
Blocks: 1582351
TreeView+ depends on / blocked
 
Reported: 2018-05-25 00:40 UTC by Sam Fowler
Modified: 2019-05-16 08:21 UTC (History)
43 users (show)

(edit)
The Linux kernel is vulnerable to a heap-based buffer overflow in the fs/ext4/xattr.c:ext4_xattr_set_entry() function. An attacker could exploit this by operating on a mounted crafted ext4 image.
Clone Of:
(edit)
Last Closed:


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:0162 None None None 2019-01-29 18:30 UTC

Description Sam Fowler 2018-05-25 00:40:54 UTC
The Linux kernel is vulnerable to a heap-based buffer overflow in the fs/ext4/xattr.c:ext4_xattr_set_entry() function. An attacker could exploit this by operating on a mounted crafted ext4 image.


Upstream bug:

https://bugzilla.kernel.org/show_bug.cgi?id=199347


Upstream patch:

https://bugzilla.kernel.org/attachment.cgi?id=276147&action=diff

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8a2b307c21d4b290e3cbe33f768f194286d07c23

Comment 1 Sam Fowler 2018-05-25 00:42:16 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1582348]

Comment 6 errata-xmlrpc 2019-01-29 18:30:22 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2019:0162 https://access.redhat.com/errata/RHSA-2019:0162


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