CVE-2024-26696: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers()
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.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 228742b2ddfb99dfd71e5a307e6088ab6836272e, 38296afe3c6ee07319e01bb249aa4bb47c07b534, 7e9b622bd0748cc104d66535b76d9b3535f9dc0f.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 228742b2ddfb99dfd71e5a307e6088ab6836272e, 38296afe3c6ee07319e01bb249aa4bb47c07b534, 7e9b622bd0748cc104d66535b76d9b3535f9dc0f 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: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers() Syzbot reported a hang issue in migrate_pages_batch() called by mbind() and nilfs_lookup_dirty_data_buffers() called in the log writer of nilfs2. While migrate_pages_batch() locks a folio and waits for the writeback to complete, the log writer thread that should bring the writeback to completion picks up the folio being written back in nilfs_lookup_dirty_data_buffers() that it calls for subsequent log creation and was trying to lock the folio. Thus causing a deadlock. In the first place, it is unexpected that folios/pages in the middle of writeback will be updated and become dirty. Nilfs2 adds a checksum to verify the validity of the log being written and uses it for recovery at mount, so data changes during writeback are suppressed. Since this is broken, an unclean shutdown could potentially cause recovery to fail. Investigation revealed that the root cause is that the wait for writeback completion in nilfs_page_mkwrite() is conditional, and if the backing device does not require stable writes, data may be modified without waiting. Fix these issues by making nilfs_page_mkwrite() wait for writeback to finish regardless of the stable write requirement of the backing device.
- Published
- Apr 3, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 8th 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.1%
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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- linux linux kernel4.20 and later · before 5.4.269
- linux linux kernel5.5 and later · before 5.10.210
- linux linux kernel5.11 and later · before 5.15.149
- linux linux kernel3.9 and later · before 4.19.307
- linux linux kernel6.2 and later · before 6.6.18
- linux linux kernel6.7 and later · before 6.7.6
- linux linux kernel5.16 and later · before 6.1.79
- linux linux kernel6.8
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
- 3.9affected
- 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 and later · before 228742b2ddfb99dfd71e5a307e6088ab6836272eaffected · git
- 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 and later · before 862ee4422c38be5c249844a684b00d0dbe9d1e46affected · git
- 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 and later · before 98a4026b22ff440c7f47056481bcbbe442f607d6affected · git
- 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 and later · before 7e9b622bd0748cc104d66535b76d9b3535f9dc0faffected · git
- 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 and later · before 8494ba2c9ea00a54d5b50e69b22c55a8958bce32affected · git
- 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 and later · before ea5ddbc11613b55e5128c85f57b08f907abd9b28affected · git
- 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 and later · before e38585401d464578d30f5868ff4ca54475c34f7daffected · git
- 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 and later · before 38296afe3c6ee07319e01bb249aa4bb47c07b534affected · git
- before 3.9not 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 6.1.82-1 | 6.1.82-1 |
| Debian:13 | linux | before 6.7.7-1 | 6.7.7-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-2024-26694Apr 3, 2024 · wifi: iwlwifi: fix double-free bug31Monitor
- ← EarlierCVE-2024-26695Apr 3, 2024 · crypto: ccp - Fix null pointer dereference in __sev_platform_shutdown_locked22Monitor
- Later →CVE-2024-26697Apr 3, 2024 · nilfs2: fix data corruption in dsync block recovery for small block sizes22Monitor
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 | 228742b2ddfb99dfd71e5a307e6088ab6836272e | Vendor (CNA) |
| Linux Linux | 38296afe3c6ee07319e01bb249aa4bb47c07b534 | Vendor (CNA) |
| Linux Linux | 7e9b622bd0748cc104d66535b76d9b3535f9dc0f | Vendor (CNA) |
| Linux Linux | 8494ba2c9ea00a54d5b50e69b22c55a8958bce32 | Vendor (CNA) |
| Linux Linux | 862ee4422c38be5c249844a684b00d0dbe9d1e46 | Vendor (CNA) |
| Linux Linux | 98a4026b22ff440c7f47056481bcbbe442f607d6 | Vendor (CNA) |
| Linux Linux | e38585401d464578d30f5868ff4ca54475c34f7d | Vendor (CNA) |
| Linux Linux | ea5ddbc11613b55e5128c85f57b08f907abd9b28 | Vendor (CNA) |
| debian:linux | 6.1.82-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.
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0494 · May 16, 2024(Linux Kernel Güncellemesi)
- TR-24-0265 · Apr 4, 2024(Linux Kernel Güncellemesi)
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 (9 more)Show less
- git.kernel.org/stable/c/38296afe3c6ee07319e01bb249aa4bb47c07b534
- git.kernel.org/stable/c/7e9b622bd0748cc104d66535b76d9b3535f9dc0f
- git.kernel.org/stable/c/8494ba2c9ea00a54d5b50e69b22c55a8958bce32
- git.kernel.org/stable/c/862ee4422c38be5c249844a684b00d0dbe9d1e46
- git.kernel.org/stable/c/98a4026b22ff440c7f47056481bcbbe442f607d6
- git.kernel.org/stable/c/e38585401d464578d30f5868ff4ca54475c34f7d
- git.kernel.org/stable/c/ea5ddbc11613b55e5128c85f57b08f907abd9b28
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- lists.debian.org/debian-lts-announce/2024/06/msg00020.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.