Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2025-39723— netfs: Fix unbuffered write error handling

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于未正确更新传输值,可能导致数据损坏。

CVSS 7.1 · High EPSS 0.23% · P13

Affected Version Matrix 8

VendorProduct Version RangeStatus
Linux Linux 288ace2f57c9d06dd2e42bd80d03747d879a4068< f08c80af3c9a9849cd178b4843b7c01d103506a1 affected
288ace2f57c9d06dd2e42bd80d03747d879a4068< 387164a2b97e1f5404c6d0049a7409bac7d2bc5b affected
288ace2f57c9d06dd2e42bd80d03747d879a4068< a3de58b12ce074ec05b8741fa28d62ccb1070468 affected
6.10 affected
< 6.10 unaffected
6.12.44≤ 6.12.* unaffected
6.16.4≤ 6.16.* unaffected
6.17≤ * unaffected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2025-39723

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
netfs: Fix unbuffered write error handling
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: netfs: Fix unbuffered write error handling If all the subrequests in an unbuffered write stream fail, the subrequest collector doesn't update the stream->transferred value and it retains its initial LONG_MAX value. Unfortunately, if all active streams fail, then we take the smallest value of { LONG_MAX, LONG_MAX, ... } as the value to set in wreq->transferred - which is then returned from ->write_iter(). LONG_MAX was chosen as the initial value so that all the streams can be quickly assessed by taking the smallest value of all stream->transferred - but this only works if we've set any of them. Fix this by adding a flag to indicate whether the value in stream->transferred is valid and checking that when we integrate the values. stream->transferred can then be initialised to zero. This was found by running the generic/750 xfstest against cifs with cache=none. It splices data to the target file. Once (if) it has used up all the available scratch space, the writes start failing with ENOSPC. This causes ->write_iter() to fail. However, it was returning wreq->transferred, i.e. LONG_MAX, rather than an error (because it thought the amount transferred was non-zero) and iter_file_splice_write() would then try to clean up that amount of pipe bufferage - leading to an oops when it overran. The kernel log showed: CIFS: VFS: Send error in write = -28 followed by: BUG: kernel NULL pointer dereference, address: 0000000000000008 with: RIP: 0010:iter_file_splice_write+0x3a4/0x520 do_splice+0x197/0x4e0 or: RIP: 0010:pipe_buf_release (include/linux/pipe_fs_i.h:282) iter_file_splice_write (fs/splice.c:755) Also put a warning check into splice to announce if ->write_iter() returned that it had written more than it was asked to.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于未正确更新传输值,可能导致数据损坏。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
Linux Linux 288ace2f57c9d06dd2e42bd80d03747d879a4068 ~ f08c80af3c9a9849cd178b4843b7c01d103506a1 -
Linux Linux 6.10 -

II. Public POCs for CVE-2025-39723

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2025-39723

请登录查看更多情报信息。

Same Patch Batch · Linux · 2025-09-05 · 60 CVEs total

CVE-2025-39726 9.8 CRITICAL s390/ism: fix concurrency management in ism_cmd()
CVE-2025-39682 9.8 CRITICAL tls: fix handling of zero-length records on the rx_list
CVE-2025-38734 9.8 CRITICAL net/smc: fix UAF on smcsk after smc_listen_out()
CVE-2025-39702 9.8 CRITICAL ipv6: sr: Fix MAC comparison to be constant-time
CVE-2025-39703 9.8 CRITICAL net, hsr: reject HSR frame if skb can't hold tag
CVE-2025-38737 9.8 CRITICAL cifs: Fix oops due to uninitialised variable
CVE-2025-39673 9.8 CRITICAL ppp: fix race conditions in ppp_fill_forward_path
CVE-2025-39704 8.8 HIGH LoongArch: KVM: Fix stack protector issue in send_ipi_data()
CVE-2025-39718 8.4 HIGH vsock/virtio: Validate length in packet header before skb_put()
CVE-2025-39711 7.8 HIGH media: ivsc: Fix crash at shutdown due to missing mei_cldev_disable() calls
CVE-2025-39710 7.8 HIGH media: venus: Add a check for packet size after reading from shared memory
CVE-2025-39696 7.8 HIGH ALSA: hda: tas2781: Fix wrong reference of tasdevice_priv
CVE-2025-39714 7.8 HIGH media: usbtv: Lock resolution while streaming
CVE-2025-39717 7.8 HIGH open_tree_attr: do not allow id-mapping changes without OPEN_TREE_CLONE
CVE-2025-39698 7.8 HIGH io_uring/futex: ensure io_futex_wait() cleans up properly on failure
CVE-2025-39697 7.8 HIGH NFS: Fix a race when updating an existing write
CVE-2025-38731 7.8 HIGH drm/xe: Fix vm_bind_ioctl double free bug
CVE-2025-39691 7.8 HIGH fs/buffer: fix use-after-free when call bh_read() helper
CVE-2025-39689 7.8 HIGH ftrace: Also allocate and copy hash for reading of filter files
CVE-2025-39677 7.8 HIGH net/sched: Fix backlog accounting in qdisc_dequeue_internal

Showing top 20 of 60 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2025-39723

No comments yet


Leave a comment