NVD / CVE Program· CNA Linux

CVE-2022-50072: NFSv4/pnfs: Fix a use-after-free bug in open

Noroxi assessment

Priority: Monitor (action score 31/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.19% (FIRST EPSS).
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 0fffb46ff3d5ed4668aca96441ec7a25b793bd6f, 2135e5d56278ffdb1c2e6d325dc6b87f669b9dac, 4.19.256.

Low priority for now. Upgrade to Linux Linux 0fffb46ff3d5ed4668aca96441ec7a25b793bd6f, 2135e5d56278ffdb1c2e6d325dc6b87f669b9dac, 4.19.256 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/pnfs: Fix a use-after-free bug in open If someone cancels the open RPC call, then we must not try to free either the open slot or the layoutget operation arguments, since they are likely still in use by the hung RPC call.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2026-09589

Published: Jun 18, 2025
Updated: Aug 5, 2026
EPSS: 0.1% · 9th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

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.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel4.19.247 and later · before 4.19.256
linux linux kernel5.4.198 and later · before 5.4.211
linux linux kernel5.10.122 and later · before 5.10.138
linux linux kernel5.15.47 and later · before 5.15.63
linux linux kernel5.17.15 and later · before 5.18
linux linux kernel5.18.4 and later · before 5.19.4

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
- 08d7a26d115cc7892668baa9750f64bd8baca29b, ea759ae0a9ae5acee677d722129710ac89cc59c1, 5.19affected
- 6b3fc1496e7227cd6a39a80bbfb7588ef7c7a010 and later · before 0fffb46ff3d5ed4668aca96441ec7a25b793bd6faffected · git
- a2b3be930e79cc5d9d829f158e31172b2043f0cd and later · before f7ee3b772d9de87387a725caa04bc041ac7fe5ecaffected · git
- 0ee5b9644f06b4d3cdcd9544f43f63312e425a4c and later · before 76ffd2042438769298f34b76102b40dea89de616affected · git
- d4c2a041ed3ba114502d5ed6ace5b1a48d637a8e and later · before a4cf3dadd1fa43609f7c6570c9116b0e0a9923d1affected · git
- 6949493884fe88500de4af182588e071cf1544ee and later · before b03d1117e9be7c7da60e466eaf9beed85c5916c8affected · git
- 6949493884fe88500de4af182588e071cf1544ee and later · before 2135e5d56278ffdb1c2e6d325dc6b87f669b9dacaffected · git
- 4.19.247 and later · before 4.19.256affected · semver
- 5.4.198 and later · before 5.4.211affected · semver
- 5.10.122 and later · before 5.10.138affected · semver

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 6.0.2-1	6.0.2-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
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 KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2022-50070Jun 18, 2025 · mptcp: do not queue data on closed subflows
31Monitor
← EarlierCVE-2022-50071Jun 18, 2025 · mptcp: move subflow cleanup in mptcp_destroy_common()
31Monitor
Later →CVE-2022-50073Jun 18, 2025 · net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null
22Monitor

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	0fffb46ff3d5ed4668aca96441ec7a25b793bd6f	Vendor (CNA)
Linux Linux	2135e5d56278ffdb1c2e6d325dc6b87f669b9dac	Vendor (CNA)
Linux Linux	4.19.256	Vendor (CNA)
Linux Linux	5.10.138	Vendor (CNA)
Linux Linux	5.15.63	Vendor (CNA)
Linux Linux	5.18	Vendor (CNA)
Linux Linux	5.19	Vendor (CNA)
Linux Linux	5.4.211	Vendor (CNA)
Linux Linux	76ffd2042438769298f34b76102b40dea89de616	Vendor (CNA)
Linux Linux	a4cf3dadd1fa43609f7c6570c9116b0e0a9923d1	Vendor (CNA)
Linux Linux	b03d1117e9be7c7da60e466eaf9beed85c5916c8	Vendor (CNA)
Linux Linux	f7ee3b772d9de87387a725caa04bc041ac7fe5ec	Vendor (CNA)
debian:linux	6.0.2-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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

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

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/0fffb46ff3d5ed4668aca96441ec7a25b793bd6f

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records