First published: Thu Jul 08 2010(Updated: )
The gfs-kmod packages contain modules that provide the ability to mount and<br>use GFS file systems.<br>A flaw was found in the gfs_lock() implementation. The GFS locking code<br>could skip the lock operation for files that have the S_ISGID bit<br>(set-group-ID on execution) in their mode set. A local, unprivileged user<br>on a system that has a GFS file system mounted could use this flaw to cause<br>a kernel panic. (CVE-2010-0727)<br>These updated gfs-kmod packages are in sync with the latest kernel<br>(2.6.18-164.19.1.el5). The modules in earlier gfs-kmod packages failed to<br>load because they did not match the running kernel. It was possible to<br>force-load the modules. With this update, however, users no longer need to.<br>Users are advised to upgrade to these latest gfs-kmod packages, updated for<br>use with the 2.6.18-164.19.1.el5 kernel, which contain a backported patch<br>to correct this issue.<br>
Affected Software | Affected Version | How to fix |
---|---|---|
<2.6.18-164.19.1.el5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of RHSA-2010:0521 is classified as moderate.
To fix RHSA-2010:0521, you should update the gfs-kmod package to version that includes the fix.
RHSA-2010:0521 affects the gfs-kmod packages on systems running kernel version 2.6.18-164.19.1.el5.
The vulnerability in RHSA-2010:0521 relates to a flaw in the gfs_lock() implementation, potentially allowing lock operations to be skipped.
There is no documented workaround for RHSA-2010:0521; the recommended action is to update the affected packages.