Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1590205 - (CVE-2018-12233) CVE-2018-12233 kernel: Memory corruption in JFS setattr
CVE-2018-12233 kernel: Memory corruption in JFS setattr
Status: CLOSED NOTABUG
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=20180601,repor...
: Security
Depends On: 1590206 1590207
Blocks: 1590208
  Show dependency treegraph
 
Reported: 2018-06-12 04:30 EDT by Andrej Nemec
Modified: 2018-06-12 22:26 EDT (History)
44 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A memory corruption issue was found in the Linux kernel with a JFS file system. Two setxattr calls to the same file with different extended attribute names would trigger an overflow and a memory corruption.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-06-12 10:48:43 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 Andrej Nemec 2018-06-12 04:30:00 EDT
A memory corruption issue was found in the Linux kernel with a JFS file system. Two setxattr calls to the same file with different extended attribute names would trigger an overflow and a memory corruption.

References:

https://lkml.org/lkml/2018/6/1/829

https://marc.info/?t=152788652700001&r=1&w=2

A proposed patch:

https://marc.info/?l=linux-kernel&m=152814391530549&w=2
Comment 1 Andrej Nemec 2018-06-12 04:31:05 EDT
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1590207]
Comment 5 Vladis Dronov 2018-06-12 10:48:43 EDT
Note:

Red Hat does not ship the JFS filesystem in any product, so no Red Hat products are vulnerable to this flaw.

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