Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
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
CVE-2018-10840 kernel: Heap-based buffer overflow in fs/ext4/xattr.c:ext4_xat...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180411,repor...
: Security
Depends On: 1582347 1584985 1584987 1584988 1582348 1584986 1584989 1584990
Blocks: 1582351
  Show dependency treegraph
 
Reported: 2018-05-24 20:40 EDT by Sam Fowler
Modified: 2018-08-28 18:44 EDT (History)
44 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
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.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam Fowler 2018-05-24 20:40:54 EDT
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-24 20:42:16 EDT
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1582348]

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