CVE-2022-49097: NFS: Avoid writeback threads getting stuck in mempool_alloc()
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.25% (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 0bae835b63c53f86cdc524f5962e39409585b22c, 1b3fa9a3c420c31e77b406ddc28f3a627100516c, a6caeddd68977a1aaaf62fbd1955b41dd5c3c5d3.
Low priority for now. Upgrade to Linux Linux 0bae835b63c53f86cdc524f5962e39409585b22c, 1b3fa9a3c420c31e77b406ddc28f3a627100516c, a6caeddd68977a1aaaf62fbd1955b41dd5c3c5d3 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: NFS: Avoid writeback threads getting stuck in mempool_alloc() In a low memory situation, allow the NFS writeback code to fail without getting stuck in infinite loops in mempool_alloc().
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-835
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%
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 5.10.111
- linux linux kernel5.11 and later · before 5.15.34
- linux linux kernel5.16 and later · before 5.16.20
- linux linux kernel5.17 and later · before 5.17.3
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
- 5.3affected
- 2b17d725f9be59a1bfa0583af690c463fca1f385 and later · before c74e2f6ecc51bd08bb5b0335477dba954a50592eaffected · git
- 2b17d725f9be59a1bfa0583af690c463fca1f385 and later · before ea029e4ce760f786919d06ef52efa2e50ea92a5faffected · git
- 2b17d725f9be59a1bfa0583af690c463fca1f385 and later · before 1b3fa9a3c420c31e77b406ddc28f3a627100516caffected · git
- 2b17d725f9be59a1bfa0583af690c463fca1f385 and later · before a6caeddd68977a1aaaf62fbd1955b41dd5c3c5d3affected · git
- 2b17d725f9be59a1bfa0583af690c463fca1f385 and later · before 0bae835b63c53f86cdc524f5962e39409585b22caffected · git
- before 5.3not affected · semver
- 5.10.111 and later · up to and including 5.10.*not affected · semver
- 5.15.34 and later · up to and including 5.15.*not affected · semver
- 5.16.20 and later · up to and including 5.16.*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.17.3-1 | 5.17.3-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-2022-49095Feb 26, 2025 · scsi: zorro7xx: Fix a resource leak in zorro7xx_remove_one()22Monitor
- ← EarlierCVE-2022-49096Feb 26, 2025 · net: sfc: add missing xdp queue reinitialization22Monitor
- Later →CVE-2022-49098Feb 26, 2025 · Drivers: hv: vmbus: Fix potential crash on module unload22Monitor
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 | 0bae835b63c53f86cdc524f5962e39409585b22c | Vendor (CNA) |
| Linux Linux | 1b3fa9a3c420c31e77b406ddc28f3a627100516c | Vendor (CNA) |
| Linux Linux | a6caeddd68977a1aaaf62fbd1955b41dd5c3c5d3 | Vendor (CNA) |
| Linux Linux | c74e2f6ecc51bd08bb5b0335477dba954a50592e | Vendor (CNA) |
| Linux Linux | ea029e4ce760f786919d06ef52efa2e50ea92a5f | Vendor (CNA) |
| debian:linux | 5.17.3-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 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.
- CVE-2026-31448420 days apartext4: avoid infinite loops caused by residual data37Monitor
- CVE-2026-63889508 days apartscsi: scsi_transport_fc: Widen FPIN pname walker counter to u3232Monitor
- CVE-2026-52933483 days apartio_uring/poll: fix signed comparison in io_poll_get_ownership()31Monitor
- CVE-2026-23451401 days apartbonding: prevent potential infinite loop in bond_header_parse()30Monitor
- CVE-2026-31552422 days apartwifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom30Monitor
- CVE-2026-46052455 days apartceph: only d_add() negative dentries when they are unhashed30Monitor
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-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.