This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

No CVSS v4.0

Attack Vector Local

Attack Complexity Low

Privileges Required Low

Scope Unchanged

Confidentiality Impact None

Integrity Impact None

Availability Impact High

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

No EPSS score available.

Key SSVC decision points have not yet been added.

No data.

No data.

No data.

Subscriptions

No data.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.

Workaround

No workaround given by the vendor.

References
Link Providers
https://lore.kernel.org/linux-cve-announce/2024082652-CVE-2024-43885-3500@gregkh/T cve-icon
https://nvd.nist.gov/vuln/detail/CVE-2024-43885 cve-icon
https://www.cve.org/CVERecord?id=CVE-2024-43885 cve-icon
History

Tue, 29 Oct 2024 02:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-667
CPEs cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Tue, 29 Oct 2024 02:15:00 +0000

Type Values Removed Values Added
Title btrfs: fix double inode unlock for direct IO sync writes kernel: btrfs: fix double inode unlock for direct IO sync writes
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Tue, 29 Oct 2024 01:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: btrfs: fix double inode unlock for direct IO sync writes If we do a direct IO sync write, at btrfs_sync_file(), and we need to skip inode logging or we get an error starting a transaction or an error when flushing delalloc, we end up unlocking the inode when we shouldn't under the 'out_release_extents' label, and then unlock it again at btrfs_direct_write(). Fix that by checking if we have to skip inode unlocking under that label. This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

Wed, 11 Sep 2024 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Tue, 27 Aug 2024 15:00:00 +0000

Type Values Removed Values Added
First Time appeared Linux
Linux linux Kernel
Weaknesses CWE-667
CPEs cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel

Tue, 27 Aug 2024 13:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

 cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Mon, 26 Aug 2024 10:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: btrfs: fix double inode unlock for direct IO sync writes If we do a direct IO sync write, at btrfs_sync_file(), and we need to skip inode logging or we get an error starting a transaction or an error when flushing delalloc, we end up unlocking the inode when we shouldn't under the 'out_release_extents' label, and then unlock it again at btrfs_direct_write(). Fix that by checking if we have to skip inode unlocking under that label.
Title btrfs: fix double inode unlock for direct IO sync writes
References
cve-icon MITRE

Status: REJECTED

Assigner: Linux

Published:

Updated: 2024-10-29T01:17:53.150Z

Reserved: 2024-08-17T09:11:59.288Z

Link: CVE-2024-43885

cve-icon Vulnrichment

Updated:

cve-icon NVD

Status : Rejected

Published: 2024-08-26T11:15:03.720

Modified: 2024-10-29T02:15:07.143

Link: CVE-2024-43885

cve-icon Redhat

Severity : Moderate

Publid Date: 2024-08-26T00:00:00Z

Links: CVE-2024-43885 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses

No weakness.