← Back to CVE intelligence
CVE intelligence

CVE-2025-39691

Vulnerability intelligence

Published Sep 5, 2025Sources checked Nov 19, 2026
7.8HIGHCVSS out of 10
What this means

Review the available evidence

CVE-2025-39691 and is rated High severity with a CVSS score of 7.8. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

What to do next

Remediation and response

Ubuntu Security Notices guidance

Vendor revision: Nov 19, 2026
Vendor remediation details

This update corrects flaws in the following subsystems: - GPU drivers; - IIO ADC drivers; - Multiple devices driver; - Ethernet bonding driver; - Network drivers; - PCI subsystem; - VFIO drivers; - File systems infrastructure; - F2FS file system; - JFS file system; - Network file system (NFS) server daemon; - OCFS2 file system; - Overlay file system; - Tracing infrastructure; - IUCV driver; (CVE-2021-47633, CVE-2022-49058, CVE-2022-49170, CVE-2023-52784, CVE-2024-53194, CVE-2024-53210, CVE-2024-53214, CVE-2024-56570, CVE-2024-56616, CVE-2024-56763, CVE-2024-56779, CVE-2024-57904, CVE-2025-21664, CVE-2025-38604, CVE-2025-39691, CVE-2025-39743, CVE-2026-43456, CVE-2026-74350)

Ubuntu Security Notices guidance

Vendor revision: Nov 19, 2026

This update corrects flaws in the following subsystems: - S/390 drivers; - File systems infrastructure; - Internal shared memory driver; (CVE-2025-39691, CVE-2025-39726)

Ubuntu Security Notices guidance

Vendor revision: Nov 19, 2026

This update corrects flaws in the following subsystems: - S/390 drivers; - File systems infrastructure; - Internal shared memory driver; - Tracing infrastructure; (CVE-2025-39689, CVE-2025-39691, CVE-2025-39726)

CISA KEVNot listedBased on the latest collected catalog
EPSS0.2%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors0Source-linked actor relationships
Overview

What is CVE-2025-39691?

In the Linux kernel, the following vulnerability has been resolved:

fs/buffer: fix use-after-free when call bh_read() helper

There's issue as follows: BUG: KASAN: stack-out-of-bounds in end_buffer_read_sync+0xe3/0x110 Read of size 8 at addr ffffc9000168f7f8 by task swapper/3/0 CPU: 3 UID: 0 PID: 0 Comm: swapper/3 Not tainted 6.16.0-862.14.0.6.x86_64 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Call Trace: <IRQ> dump_stack_lvl+0x55/0x70 print_address_description.constprop.0+0x2c/0x390 print_report+0xb4/0x270 kasan_report+0xb8/0xf0 end_buffer_read_sync+0xe3/0x110 end_bio_bh_io_sync+0x56/0x80 blk_update_request+0x30a/0x720 scsi_end_request+0x51/0x2b0 scsi_io_completion+0xe3/0x480 ? scsi_device_unbusy+0x11e/0x160 blk_complete_reqs+0x7b/0x90 handle_softirqs+0xef/0x370 irq_exit_rcu+0xa5/0xd0 sysvec_apic_timer_interrupt+0x6e/0x90 </IRQ>

Above issue happens when do ntfs3 filesystem mount, issue may happens as follows: mount IRQ ntfs_fill_super read_cache_page do_read_cache_folio filemap_read_folio mpage_read_folio do_mpage_readpage ntfs_get_block_vbo bh_read submit_bh wait_on_buffer(bh); blk_complete_reqs scsi_io_completion scsi_end_request blk_update_request end_bio_bh_io_sync end_buffer_read_sync __end_buffer_read_notouch unlock_buffer

wait_on_buffer(bh);--> return will return to caller

put_bh --> trigger stack-out-of-bounds In the mpage_read_folio() function, the stack variable 'map_bh' is passed to ntfs_get_block_vbo(). Once unlock_buffer() unlocks and wait_on_buffer() returns to continue processing, the stack variable is likely to be reclaimed.

Consequently, during the end_buffer_read_sync() process, calling put_bh() may result in stack overrun.

If the bh is not allocated on the stack, it belongs to a folio. Freeing a buffer head which belongs to a folio is done by drop_buffers() which will fail to free buffers which are still locked.

So it is safe to call put_bh() before __end_buffer_read_notouch().

Source: NVD