Linux Kernel up to 6.3.1 mark_buffer_dirty buffer overflow

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.6	$0-$5k	0.00

Summaryinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.3.1. The impacted element is the function mark_buffer_dirty. Such manipulation leads to buffer overflow. This vulnerability is documented as CVE-2023-53337. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.3.1 and classified as critical. Affected by this issue is the function mark_buffer_dirty. The manipulation with an unknown input leads to a buffer overflow vulnerability. Using CWE to declare the problem leads to CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. Impacted is confidentiality, integrity, and availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not write dirty data after degenerating to read-only According to syzbot's report, mark_buffer_dirty() called from nilfs_segctor_do_construct() outputs a warning with some patterns after nilfs2 detects metadata corruption and degrades to read-only mode. After such read-only degeneration, page cache data may be cleared through nilfs_clear_dirty_page() which may also clear the uptodate flag for their buffer heads. However, even after the degeneration, log writes are still performed by unmount processing etc., which causes mark_buffer_dirty() to be called for buffer heads without the "uptodate" flag and causes the warning. Since any writes should not be done to a read-only file system in the first place, this fixes the warning in mark_buffer_dirty() by letting nilfs_segctor_do_construct() abort early if in read-only mode. This also changes the retry check of nilfs_segctor_write_out() to avoid unnecessary log write retries if it detects -EROFS that nilfs_segctor_do_construct() returned.

The advisory is shared for download at git.kernel.org. This vulnerability is handled as CVE-2023-53337 since 09/16/2025. The exploitation is known to be easy. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 12/27/2025).

The vulnerability scanner Nessus provides a plugin with the ID 265472 (Linux Distros Unpatched Vulnerability : CVE-2023-53337), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.14.315, 4.19.283, 5.4.243, 5.10.180, 5.15.111, 6.1.28, 6.2.15 or 6.3.2 eliminates this vulnerability. Applying the patch bd89073fc7a5d03b1d06b372addbe405e5a925f4/e9c5412c5972124776c1b873533eb39e287a4dfa/4569a292a84e340e97d178898ad1cfe1a3080a61/7c3e662048053802f6b0db3a78e97f4e1f7edc4f/13f73ef77baa4764dc1ca4fcbae9cade05b83866/a73201c607d8e506358d60aafddda4246bdd9350/4005cec6847c06ee191583270b7cdd7e696543cc/55f7810632f993cff622a0ddbc7c865892294b61/28a65b49eb53e172d23567005465019658bfdb4d is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (265472) and CERT Bund (WID-SEC-2025-2087). Once again VulDB remains the best source for vulnerability data.

Affected

• Amazon Linux 2
• Red Hat Enterprise Linux
• SUSE Linux
• Oracle Linux
• IBM QRadar SIEM
• Open Source Linux Kernel
• RESF Rocky Linux
• Dell Secure Connect Gateway

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 4.14.314
• 4.19.282
• 5.4.242
• 5.10.179
• 5.15.110
• 6.1.0
• 6.1.1
• 6.1.2
• 6.1.3
• 6.1.4
• 6.1.5
• 6.1.6
• 6.1.7
• 6.1.8
• 6.1.9
• 6.1.10
• 6.1.11
• 6.1.12
• 6.1.13
• 6.1.14
• 6.1.15
• 6.1.16
• 6.1.17
• 6.1.18
• 6.1.19
• 6.1.20
• 6.1.21
• 6.1.22
• 6.1.23
• 6.1.24
• 6.1.25
• 6.1.26
• 6.1.27
• 6.2.0
• 6.2.1
• 6.2.2
• 6.2.3
• 6.2.4
• 6.2.5
• 6.2.6
• 6.2.7
• 6.2.8
• 6.2.9
• 6.2.10
• 6.2.11
• 6.2.12
• 6.2.13
• 6.2.14
• 6.3.0
• 6.3.1

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.8
VulDB Meta Temp Score: 6.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Buffer overflow
CWE: CWE-120 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Nessus ID: 265472
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-53337

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.14.315/4.19.283/5.4.243/5.10.180/5.15.111/6.1.28/6.2.15/6.3.2
Patch: bd89073fc7a5d03b1d06b372addbe405e5a925f4/e9c5412c5972124776c1b873533eb39e287a4dfa/4569a292a84e340e97d178898ad1cfe1a3080a61/7c3e662048053802f6b0db3a78e97f4e1f7edc4f/13f73ef77baa4764dc1ca4fcbae9cade05b83866/a73201c607d8e506358d60aafddda4246bdd9350/4005cec6847c06ee191583270b7cdd7e696543cc/55f7810632f993cff622a0ddbc7c865892294b61/28a65b49eb53e172d23567005465019658bfdb4d

Timelineinfo

09/16/2025 CVE reserved
09/17/2025 +1 days Advisory disclosed
09/17/2025 +0 days VulDB entry created
12/27/2025 +101 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2023-53337 (🔒)
GCVE (CVE): GCVE-0-2023-53337
GCVE (VulDB): GCVE-100-324716
CERT Bund: WID-SEC-2025-2087 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 09/17/2025 17:45
Updated: 12/27/2025 03:21
Changes: 09/17/2025 17:45 (58), 09/22/2025 23:45 (2), 12/11/2025 17:06 (11), 12/27/2025 03:21 (7)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

Interested in the pricing of exploits?

See the underground prices here!