CVE-2021-47179: NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.67% (FIRST EPSS); higher than 52.8% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 39785761feadf261bc5101372b0b0bbaf6a94494, 4.14.235, 4.19.193.
- Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 39785761feadf261bc5101372b0b0bbaf6a94494, 4.14.235, 4.19.193 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 25, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.6% · 52th percentile
- CWE
- CWE-476
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.5
- 2.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 96260bde1ea8ae31a5402fe506abbb8951d5a42caffected
- 80e34f4957ec3010c85f9bb0b568a8d46acdf535 and later · before 4e1ba532dbc1a0e19fc2458d74ab8d98680c4e42affected · git
- 7b7b9774643220e53eef58c15bb29bd4182fe053 and later · before 42637ca25c7d7b5a92804a679af5192e8c1a9f48affected · git
- 9ffa7967f9379a0a1b924e9ffeda709d72237da7 and later · before 39785761feadf261bc5101372b0b0bbaf6a94494affected · git
- 6be0e4b59314e4a836495f6ffdc5d2c5b079deeb and later · before aba3c7795f51717ae316f3566442dee7cc3eeccbaffected · git
- 2fafe7d5047f98791afd9a1d90d2afb70debc590 and later · before f9890652185b72b8de9ebeb4406037640b6e1b53affected · git
- 7e65ea887d0c0997f3053acd91a027af45e71c5b and later · before b090d110e66636bca473fd8b98d5c97b555a965aaffected · git
- de144ff4234f935bd2150108019b5d87a90a8a96 and later · before a421d218603ffa822a0b8045055c03eae394a7ebaffected · git
- 5.11.20 and later · before 5.12affected · semver
- 4.9.269 and later · before 4.9.271affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.9.269 and later · before 4.9.271
- linux linux kernel4.14.233 and later · before 4.14.235
- linux linux kernel4.19.191 and later · before 4.19.193
- linux linux kernel5.4.118 and later · before 5.4.124
- linux linux kernel5.10.36 and later · before 5.10.42
- linux linux kernel5.12.3 and later · before 5.12.9
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.14.6-1 | 5.14.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2021-47177Mar 25, 2024 · iommu/vt-d: Fix sysfs leak in alloc_iommu()22Monitor
- ← EarlierCVE-2021-47178Mar 25, 2024 · scsi: target: core: Avoid smp_processor_id() in preemptible code22Monitor
- Later →CVE-2021-47180Mar 25, 2024 · NFC: nci: fix memory leak in nci_allocate_device22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 39785761feadf261bc5101372b0b0bbaf6a94494 | Vendor (CNA) |
| Linux Linux | 4.14.235 | Vendor (CNA) |
| Linux Linux | 4.19.193 | Vendor (CNA) |
| Linux Linux | 4.9.271 | Vendor (CNA) |
| Linux Linux | 42637ca25c7d7b5a92804a679af5192e8c1a9f48 | Vendor (CNA) |
| Linux Linux | 4e1ba532dbc1a0e19fc2458d74ab8d98680c4e42 | Vendor (CNA) |
| Linux Linux | 5.10.42 | Vendor (CNA) |
| Linux Linux | 5.12 | Vendor (CNA) |
| Linux Linux | 5.12.9 | Vendor (CNA) |
| Linux Linux | 5.4.124 | Vendor (CNA) |
| Linux Linux | a421d218603ffa822a0b8045055c03eae394a7eb | Vendor (CNA) |
| Linux Linux | aba3c7795f51717ae316f3566442dee7cc3eeccb | Vendor (CNA) |
| Linux Linux | b090d110e66636bca473fd8b98d5c97b555a965a | Vendor (CNA) |
| Linux Linux | f9890652185b72b8de9ebeb4406037640b6e1b53 | Vendor (CNA) |
| debian:linux | 5.14.6-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/42637ca25c7d7b5a92804a679af5192e8c1a9f48
- git.kernel.org/stable/c/4e1ba532dbc1a0e19fc2458d74ab8d98680c4e42
- git.kernel.org/stable/c/a421d218603ffa822a0b8045055c03eae394a7eb
- git.kernel.org/stable/c/aba3c7795f51717ae316f3566442dee7cc3eeccb
- git.kernel.org/stable/c/b090d110e66636bca473fd8b98d5c97b555a965a
- git.kernel.org/stable/c/f9890652185b72b8de9ebeb4406037640b6e1b53
Vendor advisories and official records. Exploit/PoC links are deliberately left out.