In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix invalid inode pointer dereferences during log replay
In a few places where we call read_one_inode(), if we get a NULL pointer
we end up jumping into an error path, or fallthrough in case of
__add_inode_ref(), where we then do something like this:
iput(&inode->vfs_inode);
which results in an invalid inode pointer that triggers an invalid memory
access, resulting in a crash.
Fix this by making sure we don't do such dereferences.
Metrics
Affected Vendors & Products
References
History
Tue, 15 Jul 2025 13:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
epss
|
epss
|
Fri, 11 Jul 2025 13:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
epss
|
epss
|
Thu, 10 Jul 2025 14:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
|
Thu, 10 Jul 2025 00:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Wed, 09 Jul 2025 10:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | In the Linux kernel, the following vulnerability has been resolved: btrfs: fix invalid inode pointer dereferences during log replay In a few places where we call read_one_inode(), if we get a NULL pointer we end up jumping into an error path, or fallthrough in case of __add_inode_ref(), where we then do something like this: iput(&inode->vfs_inode); which results in an invalid inode pointer that triggers an invalid memory access, resulting in a crash. Fix this by making sure we don't do such dereferences. | |
Title | btrfs: fix invalid inode pointer dereferences during log replay | |
References |
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-07-09T10:42:26.014Z
Updated: 2025-07-28T04:16:01.184Z
Reserved: 2025-04-16T04:51:23.996Z
Link: CVE-2025-38243

No data.

Status : Awaiting Analysis
Published: 2025-07-09T11:15:26.350
Modified: 2025-07-10T15:15:27.077
Link: CVE-2025-38243
