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 1610102 - (CVE-2018-14615) CVE-2018-14615 kernel: Buffer overflow in fs/f2fs/inline.c:truncate_inline_inode() when unmounting a crafted f2fs image
CVE-2018-14615 kernel: Buffer overflow in fs/f2fs/inline.c:truncate_inline_in...
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20180705,reported=2...
: Security
Depends On: 1610103 1610104
Blocks: 1610105
  Show dependency treegraph
 
Reported: 2018-07-30 21:47 EDT by Sam Fowler
Modified: 2018-09-11 16:48 EDT (History)
50 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
An issue was discovered in the Linux kernel's F2FS filesystem code. A buffer overflow in truncate_inline_inode() in the fs/f2fs/inline.c function, when umounting a crafted f2fs image, can occur because a length value may be negative.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-08-02 12:42:16 EDT
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-07-30 21:47:52 EDT
An issue was discovered in the Linux kernel in the F2FS filesystem code. There is a buffer overflow in truncate_inline_inode() in fs/f2fs/inline.c when umounting a crafted f2fs image, because a length value may be negative.

Upstream Bug:

https://bugzilla.kernel.org/show_bug.cgi?id=200421
Comment 1 Sam Fowler 2018-07-30 21:49:05 EDT
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1610103]
Comment 5 Vladis Dronov 2018-08-02 12:42:16 EDT
Note:

An F2FS filesystem is not shipped with any of the Red Hat products.
Comment 6 Justin M. Forbes 2018-09-11 16:48:51 EDT
This is fixed for Fedora with the 4.18 rebases.

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