Linux Kernel up to 6.2.7 ocfs2 ocfs2_write_end_nolock buffer overflow

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.2.7. It has been declared as critical. This impacts the function ocfs2_write_end_nolock of the component ocfs2. Such manipulation leads to buffer overflow. This vulnerability is referenced as CVE-2023-53081. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.2.7. It has been rated as critical. Affected by this issue is the function ocfs2_write_end_nolock of the component ocfs2. 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: ocfs2: fix data corruption after failed write When buffered write fails to copy data into underlying page cache page, ocfs2_write_end_nolock() just zeroes out and dirties the page. This can leave dirty page beyond EOF and if page writeback tries to write this page before write succeeds and expands i_size, page gets into inconsistent state where page dirty bit is clear but buffer dirty bits stay set resulting in page data never getting written and so data copied to the page is lost. Fix the problem by invalidating page beyond EOF after failed write.

The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2023-53081 since 05/02/2025. The exploitation is known to be easy. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 11/12/2025).

Upgrading to version 4.14.312, 4.19.280, 5.4.240, 5.10.177, 5.15.105, 6.1.21 or 6.2.8 eliminates this vulnerability. Applying the patch 1629f6f522b2d058019710466a84b240683bbee3/c26f3ff4c0be590c1250f945ac2e4fc5fcdc5f45/4c24eb49ab44351424ac8fe8567f91ea48a06089/91d7a4bd5656552d6259e2d0f8859f9e8cc5ef68/a9e53869cb43c96d6d851c491fd4e26430ab6ba6/47eb055ad3588fc96d34e9e1dd87b210ce62906b/205759c6c18f54659b0b5976b14a52d1b3eb9f57/90410bcf873cf05f54a32183afff0161f44f9715 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.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 4.14.311
• 4.19.279
• 5.4.239
• 5.10.176
• 5.15.104
• 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.2.0
• 6.2.1
• 6.2.2
• 6.2.3
• 6.2.4
• 6.2.5
• 6.2.6
• 6.2.7

License

• open-source

Website

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

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion