CVE-2022-49316: NFSv4: Don't hold the layoutget locks across multiple RPC calls
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.21% (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 08d7a26d115cc7892668baa9750f64bd8baca29b, 0ee5b9644f06b4d3cdcd9544f43f63312e425a4c, 6949493884fe88500de4af182588e071cf1544ee.
Low priority for now. Upgrade to Linux Linux 08d7a26d115cc7892668baa9750f64bd8baca29b, 0ee5b9644f06b4d3cdcd9544f43f63312e425a4c, 6949493884fe88500de4af182588e071cf1544ee 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: Don't hold the layoutget locks across multiple RPC calls When doing layoutget as part of the open() compound, we have to be careful to release the layout locks before we can call any further RPC calls, such as setattr(). The reason is that those calls could trigger a recall, which could deadlock.
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-667
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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
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 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.19.247
- linux linux kernel4.20 and later · before 5.4.198
- linux linux kernel5.5 and later · before 5.10.122
- linux linux kernel5.11 and later · before 5.15.47
- linux linux kernel5.16 and later · before 5.17.15
- linux linux kernel5.18 and later · before 5.18.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
- 4.18affected
- 56f487f8c8fc5d6e582b79a86fc132d050129e15 and later · before 6b3fc1496e7227cd6a39a80bbfb7588ef7c7a010affected · git
- 56f487f8c8fc5d6e582b79a86fc132d050129e15 and later · before a2b3be930e79cc5d9d829f158e31172b2043f0cdaffected · git
- 56f487f8c8fc5d6e582b79a86fc132d050129e15 and later · before 0ee5b9644f06b4d3cdcd9544f43f63312e425a4caffected · git
- 56f487f8c8fc5d6e582b79a86fc132d050129e15 and later · before d4c2a041ed3ba114502d5ed6ace5b1a48d637a8eaffected · git
- 56f487f8c8fc5d6e582b79a86fc132d050129e15 and later · before 08d7a26d115cc7892668baa9750f64bd8baca29baffected · git
- 56f487f8c8fc5d6e582b79a86fc132d050129e15 and later · before ea759ae0a9ae5acee677d722129710ac89cc59c1affected · git
- 56f487f8c8fc5d6e582b79a86fc132d050129e15 and later · before 6949493884fe88500de4af182588e071cf1544eeaffected · git
- before 4.18not affected · semver
- 4.19.247 and later · up to and including 4.19.*not affected · 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 5.18.5-1 | 5.18.5-1 |
| Red Hat:enterprise_linux:9::appstream | bpftool-debuginfo | before 0:7.2.0-362.8.1.el9_3 | 0:7.2.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-debug-devel | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-debuginfo | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-devel | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-devel-matched | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-debug-debuginfo | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-debug-devel | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-debug-devel-matched | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-devel | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-devel-matched | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-doc | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-tools-debuginfo | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-zfcpdump-devel | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | kernel-zfcpdump-devel-matched | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
| Red Hat:enterprise_linux:9::appstream | libperf-debuginfo | before 0:5.14.0-362.8.1.el9_3 | 0:5.14.0-362.8.1.el9_3 |
+55
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-2022-49314Feb 26, 2025 · tty: Fix a possible resource leak in icom_probe22Monitor
- ← EarlierCVE-2022-49315Feb 26, 2025 · drivers: staging: rtl8192e: Fix deadlock in rtllib_beacons_stop()22Monitor
- Later →CVE-2022-49317Feb 26, 2025 · f2fs: avoid infinite loop to flush node pages22Monitor
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 | 08d7a26d115cc7892668baa9750f64bd8baca29b | Vendor (CNA) |
| Linux Linux | 0ee5b9644f06b4d3cdcd9544f43f63312e425a4c | Vendor (CNA) |
| Linux Linux | 6949493884fe88500de4af182588e071cf1544ee | Vendor (CNA) |
| Linux Linux | 6b3fc1496e7227cd6a39a80bbfb7588ef7c7a010 | Vendor (CNA) |
| Linux Linux | a2b3be930e79cc5d9d829f158e31172b2043f0cd | Vendor (CNA) |
| Linux Linux | d4c2a041ed3ba114502d5ed6ace5b1a48d637a8e | Vendor (CNA) |
| Linux Linux | ea759ae0a9ae5acee677d722129710ac89cc59c1 | Vendor (CNA) |
| debian:linux | 5.18.5-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.2.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | 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 researchersFinders, 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
- 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-667 · Improper LockingCVSS 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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/0ee5b9644f06b4d3cdcd9544f43f63312e425a4c
- git.kernel.org/stable/c/6949493884fe88500de4af182588e071cf1544ee
- git.kernel.org/stable/c/6b3fc1496e7227cd6a39a80bbfb7588ef7c7a010
- git.kernel.org/stable/c/a2b3be930e79cc5d9d829f158e31172b2043f0cd
- git.kernel.org/stable/c/d4c2a041ed3ba114502d5ed6ace5b1a48d637a8e
- git.kernel.org/stable/c/ea759ae0a9ae5acee677d722129710ac89cc59c1
Vendor advisories and official records. Exploit/PoC links are deliberately left out.