Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-26685: nilfs2: fix potential bug in end_buffer_async_write

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 2c3bdba00283a6c7a5b19481a59a730f46063803, 3.11, 3.12.
  • Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 2c3bdba00283a6c7a5b19481a59a730f46063803, 3.11, 3.12 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 potential bug in end_buffer_async_write According to a syzbot report, end_buffer_async_write(), which handles the completion of block device writes, may detect abnormal condition of the buffer async_write flag and cause a BUG_ON failure when using nilfs2. Nilfs2 itself does not use end_buffer_async_write(). But, the async_write flag is now used as a marker by commit 7f42ec394156 ("nilfs2: fix issue with race condition of competition between segments for dirty blocks") as a means of resolving double list insertion of dirty blocks in nilfs_lookup_dirty_data_buffers() and nilfs_lookup_node_buffers() and the resulting crash. This modification is safe as long as it is used for file data and b-tree node blocks where the page caches are independent. However, it was irrelevant and redundant to also introduce async_write for segment summary and super root blocks that share buffers with the backing device. This led to the possibility that the BUG_ON check in end_buffer_async_write would fail as described above, if independent writebacks of the backing device occurred in parallel. The use of async_write for segment summary buffers has already been removed in a previous change. Fix this issue by removing the manipulation of the async_write flag for the remaining super root block buffer.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Apr 3, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 16th percentile

Report tools

JSON

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.

Follow CVE-2024-26685

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux kernel
debiandebian 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 kernel3.4.83 and later · before 3.5
  • linux linux kernel3.10.16 and later · before 3.11
  • linux linux kernel3.11.5 and later · before 4.19.307
  • linux linux kernel4.20 and later · before 5.4.269
  • linux linux kernel5.5 and later · before 5.10.210
  • linux linux kernel3.2.52 and later · before 3.3
  • linux linux kernel5.16 and later · before 6.1.79
  • linux linux kernel6.2 and later · before 6.6.18
  • linux linux kernel6.7 and later · before 6.7.6
  • linux linux kernel5.11 and later · before 5.15.149
  • 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

    • ccebcc74c81d8399c7b204aea47c1f33b09c2b17, 831c87640d23ccb253a02e4901bd9a325b5e8c2d, d8974c7fe717ee8fb0706e35cc92e0bcdf660ec5, 8f67918af09fc0ffd426a9b6f87697976d3fbc7b, 3.12affected
    • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a and later · before c4a09fdac625e64abe478dcf88bfa20406616928affected · git
    • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a and later · before d31c8721e816eff5ca6573cc487754f357c093cdaffected · git
    • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a and later · before f3e4963566f58726d3265a727116a42b591f6596affected · git
    • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a and later · before 8fa90634ec3e9cc50f42dd605eec60f2d146ced8affected · git
    • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a and later · before 6589f0f72f8edd1fa11adce4eedbd3615f2e78abaffected · git
    • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a and later · before 2c3bdba00283a6c7a5b19481a59a730f46063803affected · git
    • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a and later · before 626daab3811b772086aef1bf8eed3ffe6f523effaffected · git
    • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a and later · before 5bc09b397cbf1221f8a8aacb1152650c9195b02baffected · git
    • 3.2.52 and later · before 3.3affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.82-16.1.82-1
Debian:13linuxbefore 6.7.7-16.7.7-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-52638Apr 3, 2024 · can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock
    22Monitor
  • ← EarlierCVE-2023-52639Apr 3, 2024 · KVM: s390: vsie: fix race during shadow creation
    18Monitor
  • Later →CVE-2024-26686Apr 3, 2024 · fs/proc: do_task_stat: use sig->stats_lock to gather the threads/children stats
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2c3bdba00283a6c7a5b19481a59a730f46063803Vendor (CNA)
Linux Linux3.11Vendor (CNA)
Linux Linux3.12Vendor (CNA)
Linux Linux3.3Vendor (CNA)
Linux Linux3.5Vendor (CNA)
Linux Linux5bc09b397cbf1221f8a8aacb1152650c9195b02bVendor (CNA)
Linux Linux626daab3811b772086aef1bf8eed3ffe6f523effVendor (CNA)
Linux Linux6589f0f72f8edd1fa11adce4eedbd3615f2e78abVendor (CNA)
Linux Linux8fa90634ec3e9cc50f42dd605eec60f2d146ced8Vendor (CNA)
Linux Linuxc4a09fdac625e64abe478dcf88bfa20406616928Vendor (CNA)
Linux Linuxd31c8721e816eff5ca6573cc487754f357c093cdVendor (CNA)
Linux Linuxf3e4963566f58726d3265a727116a42b591f6596Vendor (CNA)
debian:linux6.1.82-1 · Debian:12Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

Finders, 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.

All national notices →

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-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records