Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-39866: fs: writeback: fix use-after-free in __mark_inode_dirty()

Noroxi assessment

Priority: Monitor (action score 31/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.31% (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 1edc2feb9c759a9883dfe81cb5ed231412d8b2e4, b187c976111960e6e54a6b1fff724f6e3d39406c, bf89b1f87c72df79cf76203f71fbf8349cd5c9de; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1.

Low priority for now. Upgrade to Linux Linux 1edc2feb9c759a9883dfe81cb5ed231412d8b2e4, b187c976111960e6e54a6b1fff724f6e3d39406c, bf89b1f87c72df79cf76203f71fbf8349cd5c9de; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1 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: fs: writeback: fix use-after-free in __mark_inode_dirty() An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching. CPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1 ...... pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mark_inode_dirty+0x124/0x418 lr : __mark_inode_dirty+0x118/0x418 sp : ffffffc08c9dbbc0 ........ Call trace: __mark_inode_dirty+0x124/0x418 generic_update_time+0x4c/0x60 file_modified+0xcc/0xd0 ext4_buffered_write_iter+0x58/0x124 ext4_file_write_iter+0x54/0x704 vfs_write+0x1c0/0x308 ksys_write+0x74/0x10c __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x40/0xe4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x194/0x198 Root cause is: systemd-random-seed kworker ---------------------------------------------------------------------- ___mark_inode_dirty inode_switch_wbs_work_fn spin_lock(&inode->i_lock); inode_attach_wb locked_inode_to_wb_and_lock_list get inode->i_wb spin_unlock(&inode->i_lock); spin_lock(&wb->list_lock) spin_lock(&inode->i_lock) inode_io_list_move_locked spin_unlock(&wb->list_lock) spin_unlock(&inode->i_lock) spin_lock(&old_wb->list_lock) inode_do_switch_wbs spin_lock(&inode->i_lock) inode->i_wb = new_wb spin_unlock(&inode->i_lock) spin_unlock(&old_wb->list_lock) wb_put_many(old_wb, nr_switched) cgwb_release old wb released wb_wakeup_delayed() accesses wb, then trigger the use-after-free issue Fix this race condition by holding inode spinlock until wb_wakeup_delayed() finished.

HighCVSS 7.8 · v3.1—Proof of concept Fix available
Published
Sep 19, 2025
Updated
Oct 19, 2026
EPSS
0.3% · 24th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-39866

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 linux11.0
  • linux linux kernel5.11 and later · before 5.15.192
  • linux linux kernel5.16 and later · before 6.1.151
  • linux linux kernel6.2 and later · before 6.6.105
  • linux linux kernel4.2 and later · before 5.10.247
  • linux linux kernel6.13 and later · before 6.16.6
  • linux linux kernel6.7 and later · before 6.12.46
  • linux linux kernel6.17

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

    • 4.2affected
    • 0747259d13febfcc838980a63c414c9b920cea6f and later · before e2a14bbae5d8bacaa301362744a110e2be40a3a3affected · git
    • 0747259d13febfcc838980a63c414c9b920cea6f and later · before b187c976111960e6e54a6b1fff724f6e3d39406caffected · git
    • 0747259d13febfcc838980a63c414c9b920cea6f and later · before 1edc2feb9c759a9883dfe81cb5ed231412d8b2e4affected · git
    • 0747259d13febfcc838980a63c414c9b920cea6f and later · before bf89b1f87c72df79cf76203f71fbf8349cd5c9deaffected · git
    • 0747259d13febfcc838980a63c414c9b920cea6f and later · before e63052921f1b25a836feb1500b841bff7a4a0456affected · git
    • 0747259d13febfcc838980a63c414c9b920cea6f and later · before c8c14adf80bd1a6e4a1d7ee9c2a816881c26d17aaffected · git
    • 0747259d13febfcc838980a63c414c9b920cea6f and later · before d02d2c98d25793902f65803ab853b592c7a96b29affected · git
    • before 4.2not affected · semver
    • 5.10.247 and later · up to and including 5.10.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2

+96

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-2025-39864Sep 19, 2025 · wifi: cfg80211: fix use-after-free in cmp_bss()
    31Monitor
  • ← EarlierCVE-2025-39865Sep 19, 2025 · tee: fix NULL pointer dereference in tee_shm_put
    22Monitor
  • Later →CVE-2025-39868Sep 23, 2025 · erofs: fix runtime warning on truncate_folio_batch_exceptionals()
    31Monitor

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 Linux1edc2feb9c759a9883dfe81cb5ed231412d8b2e4Vendor (CNA)
Linux Linuxb187c976111960e6e54a6b1fff724f6e3d39406cVendor (CNA)
Linux Linuxbf89b1f87c72df79cf76203f71fbf8349cd5c9deVendor (CNA)
Linux Linuxc8c14adf80bd1a6e4a1d7ee9c2a816881c26d17aVendor (CNA)
Linux Linuxd02d2c98d25793902f65803ab853b592c7a96b29Vendor (CNA)
Linux Linuxe2a14bbae5d8bacaa301362744a110e2be40a3a3Vendor (CNA)
Linux Linuxe63052921f1b25a836feb1500b841bff7a4a0456Vendor (CNA)
azl3 kernel 6.6.104.2-4 on Azure Linux 3.06.6.112.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.153-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.12.0-160000.7.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-64kb6.12.0-160000.7.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default6.12.0-160000.7.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default-base6.12.0-160000.6.1.160000.2.4 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-docs6.12.0-160000.7.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-kvmsmall6.12.0-160000.7.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-build6.12.0-160000.7.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-qa6.12.0-160000.7.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-rt6.12.0-160000.7.1 · openSUSE:Leap 16.0Package registry (OSV)

+26

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:42025-09-26

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.

  1. Published
  2. First PoC+6 d
  3. TodayNov 10, 2026+417 d

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.

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

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

All records