Linux Kernel up to 5.12.8 NFSv4 pnfs_mark_matching_lsegs_return pnfs_layout_range null pointer dereference

Summaryinfo

A vulnerability described as critical has been identified in Linux Kernel up to 5.12.8. Affected is the function pnfs_mark_matching_lsegs_return of the component NFSv4. The manipulation of the argument pnfs_layout_range results in null pointer dereference. This vulnerability is known as CVE-2021-47179. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel up to 5.12.8. Affected is the function pnfs_mark_matching_lsegs_return of the component NFSv4. The manipulation of the argument pnfs_layout_range with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return() Commit de144ff4234f changes _pnfs_return_layout() to call pnfs_mark_matching_lsegs_return() passing NULL as the struct pnfs_layout_range argument. Unfortunately, pnfs_mark_matching_lsegs_return() doesn't check if we have a value here before dereferencing it, causing an oops. I'm able to hit this crash consistently when running connectathon basic tests on NFS v4.1/v4.2 against Ontap.

The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2021-47179. Technical details are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 276342 (TencentOS Server 2: kernel (TSSA-2024:0557)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.9.271, 4.14.235, 4.19.193, 5.4.124, 5.10.42 or 5.12.9 eliminates this vulnerability. Applying the patch 4e1ba532dbc1/42637ca25c7d/39785761fead/aba3c7795f51/f9890652185b/b090d110e666 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (276342) and CERT Bund (WID-SEC-2024-0699). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• Oracle Linux
• EMC Avamar
• Dell NetWorker
• Open Source Linux Kernel
• IBM Spectrum Protect Plus

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 4.9.270
• 4.14.234
• 4.19.192
• 5.4.123
• 5.10.0
• 5.10.1
• 5.10.2
• 5.10.3
• 5.10.4
• 5.10.5
• 5.10.6
• 5.10.7
• 5.10.8
• 5.10.9
• 5.10.10
• 5.10.11
• 5.10.12
• 5.10.13
• 5.10.14
• 5.10.15
• 5.10.16
• 5.10.17
• 5.10.18
• 5.10.19
• 5.10.20
• 5.10.21
• 5.10.22
• 5.10.23
• 5.10.24
• 5.10.25
• 5.10.26
• 5.10.27
• 5.10.28
• 5.10.29
• 5.10.30
• 5.10.31
• 5.10.32
• 5.10.33
• 5.10.34
• 5.10.35
• 5.10.36
• 5.10.37
• 5.10.38
• 5.10.39
• 5.10.40
• 5.10.41
• 5.12.0
• 5.12.1
• 5.12.2
• 5.12.3
• 5.12.4
• 5.12.5
• 5.12.6
• 5.12.7
• 5.12.8

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion