kernel: CVE-2018-16871 nfs: NULL pointer dereference due to an anomalized NFS message sequence

                							

                <!--X-Body-Begin-->
<!--X-User-Header-->

oss-sec
mailing list archives
<!--X-User-Header-End-->
<!--X-TopPNI-->

By Date

By Thread

</form>

<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
kernel: CVE-2018-16871 nfs: NULL pointer dereference due to an anomalized NFS message sequence

<!--X-Subject-Header-End-->
<!--X-Head-of-Message-->

From: Wade Mealing &lt;wmealing () redhat com&gt;

Date: Mon, 3 Jun 2019 12:51:07 +1000

<!--X-Head-of-Message-End-->
<!--X-Head-Body-Sep-Begin-->

<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->
A flaw was found in NFS in the Linux Kernel. An attacker who is able
to mount an exported NFS file system  is able to trigger a null
pointer dereference by an invalid NFS sequence.

This can panic the machine with a null pointer dereference and
therefore deny to the NFS server. Any outstanding disk writes to the
NFS server will be lost.

Upstream fix:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=01310bb7c9c98752cc763b36532fab028e0f8f81

Red Hat bugzilla:

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16871

Thanks,

Wade Mealing

<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->

<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->

By Date

By Thread

Current thread:

kernel: CVE-2018-16871 nfs: NULL pointer dereference due to an anomalized NFS message sequence Wade Mealing (Jun 02)

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->