CVE-2022-49850nilfs2: fix deadlock in nilfs_count_free_blocks()
- 5.5MediumCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix deadlock in nilfs_count_free_blocks() A semaphore deadlock can occur if nilfs_get_block() detects metadata corruption while locating data blocks and a superblock writeback occurs at the same time: task 1 task 2 ------ ------ * A file operation * nilfs_truncate() nilfs_get_block() down_read(rwsem A) <-- nilfs_bmap_lookup_contig() ... generic_shutdown_super() nilfs_put_super() * Prepare to write superblock * down_write(rwsem B) <-- nilfs_cleanup_super() * Detect b-tree corruption * nilfs_set_log_cursor() nilfs_bmap_convert_error() nilfs_count_free_blocks() __nilfs_error() down_read(rwsem A) <-- nilfs_set_error() down_write(rwsem B) <-- *** DEADLOCK *** Here, nilfs_get_block() readlocks rwsem A (= NILFS_MDT(dat_inode)->mi_sem) and then calls nilfs_bmap_lookup_contig(), but if it fails due to metadata corruption, __nilfs_error() is called from nilfs_bmap_convert_error() inside the lock section. Since __nilfs_error() calls nilfs_set_error() unless the filesystem is read-only and nilfs_set_error() attempts to writelock rwsem B (= nilfs->ns_sem) to write back superblock exclusively, hierarchical lock acquisition occurs in the order rwsem A -> rwsem B. Now, if another task starts updating the superblock, it may writelock rwsem B during the lock sequence above, and can deadlock trying to readlock rwsem A in nilfs_count_free_blocks(). However, there is actually no need to take rwsem A in nilfs_count_free_blocks() because it, within the lock section, only reads a single integer data on a shared struct with nilfs_sufile_get_ncleansegs(). This has been the case after commit aa474a220180 ("nilfs2: add local variable to cache the number of clean segments"), that is, even before this bug was introduced. So, this resolves the deadlock problem by just not taking the semaphore in nilfs_count_free_blocks().
Timeline
ID reserved
By Linux
Published
- 13 months later
· 13 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected e828949e5b42bfd234ee537cdb7c5e3a577958a3 – < 3c89ca6d3dfa6c09c515807a7a97a521f5d5147e
- affected e828949e5b42bfd234ee537cdb7c5e3a577958a3 – < 8b4506cff6630bb474bb46a2a75c31e533a756ba
- affected e828949e5b42bfd234ee537cdb7c5e3a577958a3 – < f0cc93080d4c09510b74ecba87fd778cca390bb1
- affected e828949e5b42bfd234ee537cdb7c5e3a577958a3 – < 36ff974b0310771417c0be64b64aa221bd70d63d
- affected e828949e5b42bfd234ee537cdb7c5e3a577958a3 – < 1d4ff73062096c21b47954d2996b4df259777bda
- affected e828949e5b42bfd234ee537cdb7c5e3a577958a3 – < abc082aac0d9b6b926038fc3adb7008306581be2
- affected e828949e5b42bfd234ee537cdb7c5e3a577958a3 – < cb029b54953420f7a2d65100f1c5107f14411bdc
- affected e828949e5b42bfd234ee537cdb7c5e3a577958a3 – < 8ac932a4921a96ca52f61935dbba64ea87bbd5dc
- affected 2.6.38
- unaffected < 2.6.38
- unaffected 4.9.334 – ≤ 4.9.*
- unaffected 4.14.300 – ≤ 4.14.*
- unaffected 4.19.267 – ≤ 4.19.*
- unaffected 5.4.225 – ≤ 5.4.*
- unaffected 5.10.155 – ≤ 5.10.*
- unaffected 5.15.79 – ≤ 5.15.*
- unaffected 6.0.9 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References
References8
- https://git.kernel.org/stable/c/3c89ca6d3dfa6c09c515807a7a97a521f5d5147e (opens in a new tab)
- https://git.kernel.org/stable/c/8b4506cff6630bb474bb46a2a75c31e533a756ba (opens in a new tab)
- https://git.kernel.org/stable/c/f0cc93080d4c09510b74ecba87fd778cca390bb1 (opens in a new tab)
- https://git.kernel.org/stable/c/36ff974b0310771417c0be64b64aa221bd70d63d (opens in a new tab)
- https://git.kernel.org/stable/c/1d4ff73062096c21b47954d2996b4df259777bda (opens in a new tab)
- https://git.kernel.org/stable/c/abc082aac0d9b6b926038fc3adb7008306581be2 (opens in a new tab)
- https://git.kernel.org/stable/c/cb029b54953420f7a2d65100f1c5107f14411bdc (opens in a new tab)
- https://git.kernel.org/stable/c/8ac932a4921a96ca52f61935dbba64ea87bbd5dc (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-12931 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-49850)Record last updated .