Answer in brief
CVE-2021-47179 records a High severity (CVSS 7.5) vulnerability in NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2021-47179 records a High severity (CVSS 7.5) vulnerability in NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=80e34f4957ec3010c85f9bb0b568a8d46acdf535 <4e1ba532dbc1a0e19fc2458d74ab8d98680c4e42 || >=7b7b9774643220e53eef58c15bb29bd4182fe053 <42637ca25c7d7b5a92804a679af5192e8c1a9f48 || >=9ffa7967f9379a0a1b924e9ffeda709d72237da7 <39785761feadf261bc5101372b0b0bbaf6a94494 || >=6be0e4b59314e4a836495f6ffdc5d2c5b079deeb <aba3c7795f51717ae316f3566442dee7cc3eeccb || >=2fafe7d5047f98791afd9a1d90d2afb70debc590 <f9890652185b72b8de9ebeb4406037640b6e1b53 || >=7e65ea887d0c0997f3053acd91a027af45e71c5b <b090d110e66636bca473fd8b98d5c97b555a965a || >=de144ff4234f935bd2150108019b5d87a90a8a96 <a421d218603ffa822a0b8045055c03eae394a7eb || 96260bde1ea8ae31a5402fe506abbb8951d5a42c || >=5.11.20 <5.12 | 4e1ba532dbc1a0e19fc2458d74ab8d98680c4e42, 42637ca25c7d7b5a92804a679af5192e8c1a9f48, 39785761feadf261bc5101372b0b0bbaf6a94494, aba3c7795f51717ae316f3566442dee7cc3eeccb, f9890652185b72b8de9ebeb4406037640b6e1b53, b090d110e66636bca473fd8b98d5c97b555a965a, a421d218603ffa822a0b8045055c03eae394a7eb, 5.12 |
| Linux/Linuxgeneric | >=4.9.269 <4.9.271 || >=4.14.233 <4.14.235 || >=4.19.191 <4.19.193 || >=5.4.118 <5.4.124 || >=5.10.36 <5.10.42 || >=5.12.3 <5.12.9 | 4.9.271, 4.14.235, 4.19.193, 5.4.124, 5.10.42, 5.12.9 |
Published upstream
Mar 25, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=80e34f4957ec3010c85f9bb0b568a8d46acdf535 <4e1ba532dbc1a0e19fc2458d74ab8d98680c4e42 || >=7b7b9774643220e53eef58c15bb29bd4182fe053 <42637ca25c7d7b5a92804a679af5192e8c1a9f48 || >=9ffa7967f9379a0a1b924e9ffeda709d72237da7 <39785761feadf261bc5101372b0b0bbaf6a94494 || >=6be0e4b59314e4a836495f6ffdc5d2c5b079deeb <aba3c7795f51717ae316f3566442dee7cc3eeccb || >=2fafe7d5047f98791afd9a1d90d2afb70debc590 <f9890652185b72b8de9ebeb4406037640b6e1b53 || >=7e65ea887d0c0997f3053acd91a027af45e71c5b <b090d110e66636bca473fd8b98d5c97b555a965a || >=de144ff4234f935bd2150108019b5d87a90a8a96 <a421d218603ffa822a0b8045055c03eae394a7eb || 96260bde1ea8ae31a5402fe506abbb8951d5a42c || >=5.11.20 <5.12 | 4e1ba532dbc1a0e19fc2458d74ab8d98680c4e42, 42637ca25c7d7b5a92804a679af5192e8c1a9f48, 39785761feadf261bc5101372b0b0bbaf6a94494, aba3c7795f51717ae316f3566442dee7cc3eeccb, f9890652185b72b8de9ebeb4406037640b6e1b53, b090d110e66636bca473fd8b98d5c97b555a965a, a421d218603ffa822a0b8045055c03eae394a7eb, 5.12 |
| Linux/Linuxgeneric | >=4.9.269 <4.9.271 || >=4.14.233 <4.14.235 || >=4.19.191 <4.19.193 || >=5.4.118 <5.4.124 || >=5.10.36 <5.10.42 || >=5.12.3 <5.12.9 | 4.9.271, 4.14.235, 4.19.193, 5.4.124, 5.10.42, 5.12.9 |
Published upstream
Mar 25, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.