# CVE-2022-49850: linux: In the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix deadlock in nilfs_count_free_blocks(...

CVE-2022-49850 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-49850, released May 1, 2025. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2022-49850
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0017
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: May 1, 2025

## 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().

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 12.15 (bookworm) | 6.0.10-1 | [DEBIAN-CVE-2022-49850](https://patchblox.com/security/data/fix/linux/debian-cve-2022-49850.md) | May 1, 2025 |
| Linux | linux Debian 13.5 (trixie) | 6.0.10-1 | [DEBIAN-CVE-2022-49850](https://patchblox.com/security/data/fix/linux/debian-cve-2022-49850.md) | May 1, 2025 |
| Linux | linux Debian 14 | 6.0.10-1 | [DEBIAN-CVE-2022-49850](https://patchblox.com/security/data/fix/linux/debian-cve-2022-49850.md) | May 1, 2025 |

---

Data as of 2026-11-09T01:18:40Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.